Execute Workflow Trigger

Helpers for calling other n8n workflows. Used for designing modular, microservice-like workflows.

Overview

This node, named "Execute Workflow Trigger," is designed to facilitate modular and microservice-like workflow designs in n8n by enabling workflows to be called from other workflows. It acts as a trigger that can receive input data when manually triggered or when invoked by another workflow using the Execute Workflow Trigger mechanism.

Common scenarios where this node is beneficial include:

  • Breaking down complex workflows into smaller, reusable components.
  • Creating workflows that act as services or modules callable by other workflows.
  • Passing custom input data to a workflow when testing it manually.

For example, you might have a workflow that processes customer data and want to call it from multiple other workflows with different inputs. This node allows you to trigger that processing workflow and pass the required input data dynamically.

Properties

Name Meaning
Input The JSON input data sent when the node is manually triggered.
Events Hidden property with a single option "Workflow Call" indicating the node triggers when called by another workflow using Execute Workflow Trigger.

Output

The node outputs an array of items where each item contains a json field holding the parsed JSON input data.

  • When run in manual mode, the output is a single item containing the JSON parsed from the "Input" property.
  • When triggered by another workflow, it simply passes through the input data it receives.

No binary data output is produced by this node.

Dependencies

  • No external services or API keys are required.
  • The node relies on n8n's internal workflow execution environment and helpers for parsing input and emitting data.

Troubleshooting

  • Invalid JSON in Input: If the "Input" property contains invalid JSON, the node will throw a parsing error. Ensure the JSON syntax is correct before running manually.
  • No Data Emitted: If triggered externally but no input data is passed, the node will output whatever input it receives, which may be empty. Verify the calling workflow sends the expected data.
  • Manual vs External Trigger Behavior: Remember that the node behaves differently depending on whether it is run manually or triggered by another workflow. Confusion here may lead to unexpected results.

Links and References

Discussion