Execute Workflow as Node

Executes a workflow that contains a "Workflow as Node Trigger"

Overview

The "Execute Workflow as Node" custom node allows you to run another workflow within your current workflow execution. It is designed specifically to execute workflows that contain a "Workflow as Node Trigger." This node is useful when you want to modularize complex automation by splitting logic into multiple workflows and then invoking them dynamically from a parent workflow.

Typical use cases include:

  • Reusing common workflow logic across different automation scenarios.
  • Dynamically triggering workflows based on runtime parameters.
  • Passing configuration data to the triggered workflow for customized execution.

For example, you might have a workflow that processes incoming data and, depending on certain conditions, calls another workflow to handle notifications or data enrichment.

Properties

Name Meaning
Workflow Select the target workflow to execute.
Configuration Paste the JSON configuration copied from the trigger node of the target workflow here.

Additionally, after pasting the configuration JSON, dynamic properties are generated based on the methods and input fields defined in that configuration. These dynamic properties allow you to pass specific parameters to the executed workflow.

Output

The node outputs an array of JSON objects representing the results returned by the executed workflow. Each item corresponds to one output item from the called workflow. The output does not include binary data; it only returns JSON-formatted data.

Dependencies

  • Requires access to the n8n instance's workflows to execute the selected workflow by its ID.
  • The user must provide a valid workflow ID and the corresponding configuration JSON from the target workflow's trigger node.
  • No external API keys or services are required beyond what the executed workflow itself may need.

Troubleshooting

  • No workflow ID selected error: This occurs if the "Workflow" property is left empty. Ensure you select a valid workflow to execute.
  • Invalid configuration JSON: If the pasted configuration JSON is malformed or does not match the expected structure, dynamic properties may not load correctly, or execution may fail. Verify the JSON is correctly copied from the target workflow's trigger node.
  • Empty output: If the executed workflow returns no data or null items, the output will be an empty array. Check the target workflow's logic and ensure it produces output.
  • Execution failures in the called workflow: Errors inside the executed workflow will propagate back. Review the target workflow's execution logs for details.

Links and References

Discussion