Execute Workflow Trigger

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

Written By pvdyck

Last updated 16 days ago

Execute Workflow Trigger

Limitation - Only the Execute Subflow node works.

n8n docs

Execute Workflow Trigger node documentation

What It Does

The entry point for sub-workflows. When another agent calls your workflow using the Execute Workflow node, this trigger receives the input data and starts the workflow.

Input Modes

ModeDescription

Passthrough

Forwards all incoming data to the workflow unchanged

Using Workflow Inputs

Defines a schema — only specified fields are passed through, others are filtered out. Missing fields default to null

Using JSON Example

Defines accepted fields from a JSON example — same filtering behavior as Workflow Inputs

How It Works

  1. A parent workflow calls your agent using the Execute Workflow node

  2. This trigger receives the parent's items

  3. Items are filtered according to the selected input mode

  4. Your workflow processes the filtered data

  5. The final output is returned to the parent workflow

Compatibility

FeatureStatus

Passthrough mode

Supported

Workflow Inputs mode (field schema)

Supported

JSON Example mode

Supported

One trigger per workflow

Required — only one Execute Workflow Trigger is allowed per workflow

Tips

  • Use Passthrough when you want to accept any input structure

  • Use Workflow Inputs when you want to enforce a strict data contract between parent and child workflows

  • Only one Execute Workflow Trigger is allowed per workflow — if you need multiple entry points, split into separate workflows

Status

This integration is fully tested and verified on indie.money.