Composable Workflows

You can now build larger automations in our workflows product by connecting multiple workflows. A workflow can now call another workflow, wait for its result, and continue with its output.

We also added more ways to trigger workflows, made workflow runs faster, and improved how you monitor your workflows and recover failed runs.

Calling other workflows

Select another workflow in the editor, map its inputs, and use its result in the steps that follow. This lets you reuse shared logic across automations instead of rebuilding the same steps.

Nested runs are visible in the run history with Called by and Open Child Run indicators. Workflows can be nested up to five levels deep, and cycle detection prevents recursive calls.

Multiple triggers

You can now add multiple triggers to a single workflow, so the same automation can run from different sources. All existing trigger types can be combined without creating and maintaining separate workflows.

Monitor and rerun workflows

The Workflow Monitor now surfaces invalid connections before a run fails and lets you reconnect them directly. You can also approve or reject pending reviews and agent inputs from the monitor.

Published workflow failures and spend limit alerts can notify recipients through their inbox. Failed runs show when a retry has succeeded, and you can rerun up to 20 failed runs at once, either from the point of failure or from the beginning.

Over the last few weeks, we also shipped a set of smaller improvements across workflows, which you can see below.

  • Environment variables: Define shared values once and reuse them across workflows, keeping configuration and secrets consistent without hard-coding them in every node.
  • Export workflow runs: Export run data to analyze executions outside Langdock or keep an offline record.
  • Import from Zapier and Make: Import existing automations from a clearer entry point, with more useful schema details when an import fails.
  • Code node file access: Let code nodes read files produced by earlier nodes, including attachments and generated files.
  • Transcribe audio node: Turn audio into text as part of an automation without leaving the workflow builder.
  • Webhook triggers: Accept GET webhook requests, optionally require authentication, and preserve raw payloads and request headers when you need the unparsed request.
  • Test run context: Test runs retain context from nodes that have already run, so iterative testing does not lose earlier results.
  • Output values redesign: We now display outputs in a more friendly way, making it easier to work with node outputs.