Skip to main content
Logic & Flow Control

Execute Workflow Node

Call a published indie.money sub-workflow from within your workflow. The sub-workflow runs on its own owner's budget (owner-pays).

Written By Philippe

Last updated 3 days ago

Execute Workflow Node

⚠️ Limitations — Works with known restrictions, see details below

What It Does

Calls another published indie.money workflow (sub-workflow) from within your workflow. The sub-workflow must be published and deployed on the platform.

How It Works

  1. Your workflow reaches the Execute Workflow node
  2. The node sends the current items to the sub-workflow
  3. The sub-workflow processes them and returns results
  4. Your workflow continues with the sub-workflow's output

Execution Modes

ModeDescription
Once for All ItemsSends all items in a single call to the sub-workflow
Once for Each ItemCalls the sub-workflow separately for each item. Supports Continue on Fail — if one item fails, the rest still process

Billing

When you call a sub-workflow, owner-pays applies:

  • The caller pays only for its own execution costs
  • The sub-workflow runs as its own webhook execution, billed to the sub-workflow owner's budget — not yours

Your budget is never charged for the callee; the callee's owner funds its runs.

Compatibility

FeatureStatus
Call published sub-workflowsSupported
Once for All Items / Once for Each ItemSupported
Continue on FailSupported
Sub-execution trackingSupported — sub-workflow execution IDs are tracked for auditing
Load from file / URL / parameterNot supported — only published workflows can be called. Set "Source" to "Database" in your n8n workflow
Sub-workflow without an Execute Workflow TriggerNot supported — turning on a workflow that calls one is refused. Add an Execute Workflow Trigger to the sub-workflow and publish it again
Shared state with sub-workflowNot available — the sub-workflow runs independently with its own execution context

Timeout

Sub-workflow calls have a 5-minute timeout. If the sub-workflow takes longer, the call will fail. Design sub-workflows to complete within this limit.

Tips

  • The sub-workflow must have an Execute Workflow Trigger as its entry point
  • Make sure the sub-workflow is published and deployed before calling it
  • Use Once for Each Item mode with Continue on Fail for batch processing that shouldn't stop on individual errors

Status

This integration works on indie.money with known limitations. See the details above for specifics.

Was this helpful?

Still need help? Ask the team