Skip to main content

Wait for Approval Action

Pause an automation pipeline until a technician manually approves or rejects the run.

Updated this week

Introduction

Pause the automation pipeline at a specific point and wait for a technician to manually approve before execution continues. Use this action when a step carries enough risk that you want a human checkpoint before it runs.


Wait for Approval Action

From the automation pipeline in edit mode, click + and select Wait for approval from the Flow category.

Action Picker - Wait for Approval

This action has no configuration fields. Add it to the pipeline and position it where you want the approval gate to occur.

Wait for Approval Action

πŸ’‘ TIP: Place Wait for Approval immediately before high-impact actions β€” destructive changes, mass uninstalls, or anything you wouldn't want running unattended. It's a low-overhead way to add a human review step without building a separate approval workflow.


Conditions

The Conditions section lets you restrict when this action runs based on device attributes or the outcome of a previous action.

See Action Conditions for the full reference on condition types, operators, and values.


Additional Options

Expand Additional options for action name, failure behavior, output variable assignment, retries, and the enabled toggle.

See Actions Overview for the full reference on additional options available on every action.


FAQ

  • Where do I approve or reject a pending run? Two places: from the automation itself, or from the Automations tab in device details for the specific device that's waiting.

  • What happens to the run while it's waiting? The pipeline is paused for that device. Other devices in the same run continue through their pipelines independently.

  • Does the run expire if nobody approves it? No β€” pending approvals don't expire. The run waits indefinitely until a technician approves or rejects it.

  • Do technicians get notified when a run is waiting for approval? No β€” there's no automatic notification. Technicians need to check the automation run history or device automations view to see pending approvals.

  • Who can approve or reject a pending run? Technicians with permission to manage automations in the relevant group. See Workspace β†’ Permissions for access control configuration.

Did this answer your question?