Skip to main content

Automation Completed

Starts the automation when a different automation finishes. Reach for it to chain work together—cleanup after a long-running job, a notification when a nightly sync fails—without wiring the second automation into the first.

Fields

FieldDescription
Target AutomationThe automation to watch. It cannot be the automation that owns this trigger.
OutcomesWhich terminal outcomes to react to: Succeeded, Failed, or both.

What later steps see

The output is a completion snapshot of the finished run: which run it was, the payload that originally started it, its timing, and—when it failed—a summary of the error. Later steps branch on the snapshot's status rather than on the target's own output, so one trigger can serve both outcomes.

Only the top-level run counts. A run that fans out into child runs fires this trigger once, when the parent reaches its terminal state.

Was this page helpful?

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.