Execute Workflow as Node

Executes a workflow that contains a "Workflow as Node Trigger"
Join our community

Overview

This node allows you to execute another workflow within your current workflow by invoking a workflow that contains a "Workflow as Node Trigger." It is useful when you want to modularize complex automation processes by splitting them into smaller workflows and then calling those workflows dynamically with specific input configurations.

Practical examples include:

  • Running a reusable sub-workflow for data transformation or enrichment.
  • Triggering a specialized workflow based on dynamic configuration passed at runtime.
  • Executing workflows that handle specific tasks like sending notifications, processing files, or interacting with external APIs, all from within a parent workflow.

Properties

Name Meaning
Workflow Select the target workflow to execute. This must be a workflow that includes a "Workflow as Node Trigger".
Configuration Paste the JSON configuration copied from the trigger node of the target workflow. This JSON defines the available methods and input fields for the execution.

Additionally, based on the pasted configuration JSON, dynamic properties are generated representing the input parameters required by the target workflow's trigger node. These dynamic properties correspond to the input fields defined in the configuration JSON and may have conditional display logic.

Output

The node outputs the data returned by the executed workflow. The output is an array of JSON objects representing the results of the invoked workflow execution. Each item corresponds to one output item from the called workflow.

If the executed workflow returns binary data, it will be included accordingly in the output items, but this node primarily focuses on forwarding the JSON data output.

Dependencies

  • Requires access to the selected workflow within the same n8n instance.
  • No external API keys or services are directly required by this node itself.
  • The user must provide the configuration JSON from the target workflow’s trigger node to enable dynamic input property generation.

Troubleshooting

  • Error: "No workflow selected or workflow ID is invalid."
    This occurs if no workflow is selected or the workflow ID is missing/incorrect. Ensure you select a valid workflow containing a "Workflow as Node Trigger."

  • Invalid Configuration JSON
    If the pasted configuration JSON is malformed or does not match the expected structure, dynamic input properties may not load correctly. Verify that the JSON is copied exactly from the trigger node configuration of the target workflow.

  • Empty or Null Output
    If the executed workflow returns no data or null values, the output array will filter out nulls, possibly resulting in empty output. Check the target workflow’s logic and ensure it produces output.

Links and References

Discussion