Call function workflow
Calls another workflow as a sub-routine, passes inputs, receives outputs back.
Why use it
Reusable logic. If three workflows all need to "score a lead based on its fields and return a label", extract that scoring into a dedicated "function workflow" and call it from each. Maintain in one place.
Function workflows have:
- A Manual run trigger marked as "callable from other workflows".
- A Return value node at the end (see below) that defines what they hand back to the caller.
Inputs
| Field | Type | Description |
|---|---|---|
function_workflow | reference | Pick the callable workflow from a dropdown |
arguments | object | Key/value pairs that become the callable's trigger payload |
Outputs
- return — the payload the callee's Return value node produced.
Errors
If the function workflow fails (and doesn't have its own internal try/catch), the calling workflow's Call function node fails too, propagating up the stack. Wrap the call in a try/catch if you want to handle failures locally.