Run Integration

The Run Integration step runs another integration from inside this one. It is how a common
sequence is written once and reused, rather than duplicated across workflows.

Configuration

Field	Notes
Integration	The integration to run
Run integration asynchronously	Start it and continue without waiting. Leave off when this integration needs its result
Trigger data	What to pass in. Supply it from an earlier Step, shape it with a Mapping, or provide Request Body Text directly

Output

When run synchronously, the called integration's result is available to later steps. When run
asynchronously there is no result to wait for — the called integration's own execution log is
where its outcome lives.

Notes

Asynchronous is the right choice for fire-and-forget work such as notifications. Synchronous
is required whenever the outcome affects what happens next.
A called integration records its own execution separately, so a failure appears in its history
rather than only in the caller's.
Avoid a chain that leads back to itself; there is no protection against an integration that
eventually calls itself.