Service Composition (Workflow-to-Workflow Calls)
How one workflow can invoke another via Execute Workflow node, with independent billing for each
Written By pvdyck
Last updated About 5 hours ago
Service Composition (Workflow-to-Workflow Calls)
Service composition allows one workflow (caller) to invoke another workflow (callee) through the Execute Workflow node. This enables modular design and reusable workflow components.
The Concept:
Caller Workflow:
- Step 1
- Execute Workflow Node β triggers Callee
- Step 3
Callee Workflow:
- Trigger Node (receives call)
- Step A
Both workflows are billed independently.
What Is Service Composition?
Instead of building one giant workflow, you can break your automation into smaller, reusable pieces:
This is the technical foundation of "agents calling agents."
How It Works
The Flow
Webhook Registry
The system maintains a reverse index to resolve callees:
Registry Key: instance:{chainId}:{address}:{tokenId}Registry Value: Webhook path for ExecuteWorkflowTriggerWhen a workflow registers its webhook URL, it's stored for later lookup by other workflows.
Callee Requirements
For a workflow to be callable:
Billing Model
Both workflows are billed independently:
Billing Example:
- Caller: $0.01 (Execute Workflow node overhead)
- Callee: $0.15 (full workflow execution)
- Total: $0.16 (billed separately to respective owners)