Execute Workflow Trigger

Entry point for sub-workflows called by an Execute Workflow node in another agent.

Written By pvdyck

Last updated 16 minutes ago

Execute Workflow Trigger

The Execute Workflow Trigger is the entry point for a sub-workflow. It receives data from a parent workflow that calls it via the Execute Workflow node.

What It Does

This node must be the first node in any sub-workflow. When a parent workflow calls this sub-workflow, the trigger receives the incoming data and passes it to the next node. The sub-workflow runs and returns its output to the parent.

Use Cases

  • Workflow reusability — Multiple parent workflows can call the same sub-workflow (e.g., a shared report generator or data formatter).
  • Modular architecture — Break large, complex workflows into smaller, maintainable components.

Input Modes

ModeDescription
PassthroughForwards all incoming data as-is to the next node (default)
Using Workflow InputsFilters incoming data to match a declared field schema. Only the declared fields are passed through.
Using JSON ExampleFilters incoming data to match keys from a sample JSON object you provide.

Parameters

ParameterDescription
Input SourceChoose the input mode: Passthrough, Using Workflow Inputs, or Using JSON Example
Workflow Inputs(Workflow Inputs mode) Define the expected field names and types
JSON Example(JSON Example mode) Paste a sample JSON object to define the expected schema

How Data Flows

  1. The parent workflow's Execute Workflow node sends data to the sub-workflow.
  2. This trigger node receives the data and applies the selected input mode.
  3. The sub-workflow processes the data through its nodes.
  4. The final output is returned to the parent workflow.

Setup

  1. Create the sub-workflow with Execute Workflow Trigger as its entry point.
  2. Publish it as a separate agent on indie.money.
  3. In the parent workflow, use the Execute Workflow node and map the sub-agent's contract address.

Tips

  • Use Workflow Inputs mode to enforce a strict schema and prevent unexpected data from reaching downstream nodes.
  • Use Passthrough mode during development, then switch to a stricter mode before publishing.
  • The JSON Example mode is convenient for quickly defining a schema by pasting a sample payload.

Limitations

  • Sub-workflow billing — Calling a sub-workflow agent costs the Producer the sub-agent's execution price in addition to the parent agent's price. Set sub-agent pricing appropriately.
  • The sub-workflow must be a published, live indie.money agent. You cannot call arbitrary n8n-compatible workflows.
  • This trigger can only be activated by the Execute Workflow node or the Call n8n Workflow Tool node — it cannot be triggered manually or by external events.

Related