Sub-automation Node

The Sub-automation node invokes another saved automation and waits for it to complete before passing records downstream. It lets you compose modular, reusable automation pipelines.

When to Use

Use Sub-automation when you have a reusable processing pipeline — an enrichment sequence, a compliance check, a scoring routine — that you want to call from multiple parent automations without duplicating the logic.

Configuration

Input Mapping

passthrough — All fields from the current record are passed to the child automation as-is.

mapped — Only the fields listed in fieldMappings are passed, renamed to their child field names.

Output Mapping

replace — The output of the child automation replaces the current record entirely.

merge — The child automation's output fields are merged into the current record, with child fields taking precedence on name collisions.

On Child Failure

fail — The parent automation run fails if the child fails or times out.

skip — The record is passed through unchanged; the child failure is logged but does not stop the run.

use-input — The original input record (before the sub-automation) is used as the output, as if the sub-automation returned it unchanged.

Example

Run a compliance-check sub-automation on each lead:

workflowId: wf_compliance_check_v2
inputMapping: passthrough
outputMapping: merge
timeout: 10m
onChildFailure: skip

Notes

• The parent automation run pauses at this node until the child completes.
• The child automation must belong to the same owner as the parent, or the node fails.
• The child must be in active or draft status to be callable.
• Circular references (automation A calling automation B calling automation A) are detected at run time and fail immediately.
• Sub-automations can nest up to 3 levels deep; exceeding that depth fails the run.