Execute Workflow Trigger
The Execute Workflow Trigger node is the foundational entry point for building modular sub-workflows. Unlike Webhooks or Schedules that rely on external events, this trigger listens for internal execution calls from the 'Execute Workflow' node or an autonomous AI Agent tool invocation.
What can you do with Execute Workflow Trigger?
Modular Orchestration
Transform your workflow into a reusable function block. Stop duplicating steps manually across 10 canvases; instead, build standard operations once and call them internally.
Flawless Data Passthrough
Automatically receives the raw payload sent from the calling workflow or AI Agent. Variables are instantly mapped to the output port, ready for downstream processing immediately.
AI Agent Compatibility
Required fundamentally when turning a workflow into a "Tool" for the AI Agent. This is the exact gate that safely receives the AI's autonomous JSON tool arguments.
Detailed Usage & Configuration
The Execute Workflow Trigger is the engine powering nested architectures. Whenever you want a workflow to be triggered programmatically by another workflow (or AI Agent) rather than relying on an external HTTP event, this is the trigger you place at the very beginning of your Canvas.
1. Understanding Sub-Workflows
Building massive architectures on a single canvas is unmaintainable. Sub-workflows solve this by encapsulating logic.
- Place the Execute Workflow Trigger at the start of a new workflow.
- Whenever a Parent workflow utilizes an "Execute Workflow" action node and selects this canvas, the execution jumps to this trigger instantly.
2. Receiving Injection Payloads
When an AI Agent uses this workflow as a tool, it generates JSON parameters dynamically (e.g. {"searchQuery": "Support Ticket 42"}). The Execute Workflow Trigger silently accepts this object and passes it straight to its main output line. You can immediately access these properties in the next node using standard expressions like {{ $json.searchQuery }}.
3. Architectural Requirements
For a Sub-Workflow loop to be thoroughly completed, you generally must place an Execute Workflow Output (or standard Virtual Output) at the very end of the sequence to ensure data is handed gracefully back to the original caller. The Trigger acts as the Input door, while the Output acts as the Exit door.