Call workflow

Node catalog Actions

On this page

Runs a published workflow in the same execution (shared context and outputs)

Usage and specifics

The target workflow must be published. The call shares context and outputs within the same execution. Supply an explicit payload or forward incoming data.

Technical type : call_workflow. Runtime : nodulz.

Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the credentials guide if a remote source or execution target requires access.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`targetTriggerId`	`string`	`""`	-
`targetInputMode`	`enum`	`"select"`	`id`, `select`
`payload`	`string`	`"{}"`	-
`waitForCompletion`	`boolean`	`true`	-

Configuration help

waitForCompletion Wait: When enabled, target workflow nodes run in the same execution (unified log and context). When disabled, starts a background run without merging outputs.

Examples

When enabled, target workflow nodes run in the same execution (unified log and context). When disabled, starts a background run without merging outputs.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "targetTriggerId": "",
  "targetInputMode": "select",
  "payload": "{}",
  "waitForCompletion": true
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.