invoke_workflow
Chain workflows together by invoking another workflow from within your current workflow.
Overview
Chain workflows together by invoking another workflow from within your current workflow. This step enables workflow composition and reusability by allowing you to call another deployed workflow as if it were a function. The target workflow receives the event data (or a subset of it) via its webhook endpoint, processes it through its own steps, and this step captures the result. This is useful for breaking complex processing into modular, reusable workflows, creating multi-stage pipelines, or delegating specialized processing to dedicated workflows. The invocation happens synchronously within the Kubernetes cluster.
Quick Start
steps:
- type: invoke_workflow
workflow_id: 3f9c1b28-9e5e-4c7a-9012-8a7f7d9f03c9Configuration
| Parameter | Type | Required | Description |
|---|---|---|---|
workflow_id | string | Yes | Target workflow UUID used to resolve the in-cluster webhook service. |
input_from | string | No | Dot-separated path selecting a nested value from the event to send to the downstream workflow. When omitted, the entire event is sent. |
payload_path | string | No | DEPRECATED: Use 'input_from' instead. Dot-separated path selecting a value from the event. |
Examples
Chain workflows together
Forward the entire event to a downstream workflow for further processing
type: invoke_workflow
workflow_id: enrichment-pipeline
Pass specific data to another workflow
Send only relevant data to a specialized processor workflow
type: invoke_workflow
workflow_id: user-validation
input_from: user_data
Advanced Options
These options are available on all steps for error handling and retry logic:
| Parameter | Type | Default | Description |
|---|---|---|---|
retries | integer | 0 | Number of retry attempts (0-10) |
backoff_seconds | number | 0 | Backoff (seconds) applied between retry attempts |
retry_propagate | boolean | false | If True, raise last exception after exhausting retries; otherwise swallow. |