Skip to main content

Automations and approvals

An automation is a workflow agent's run. Runs start on a schedule, from a connected app, from a continuous-integration job, or when you start one by hand. Some pause partway and wait for a person to decide before they continue.

Who can use it: the Member role. Deciding an approval needs to be one of the run's reviewers; some approvals are reserved for administrators.

VideoAutomations and approvals2:50

Recorded on .

Follow your runs​

The Automations page: status chips (All, Running, Needs approval, Failed, Scheduled, Successful), a trigger filter, a time range, and a table with Automation, Status, Time, Duration and Output.The Automations page: status chips (All, Running, Needs approval, Failed, Scheduled, Successful), a trigger filter, a time range, and a table with Automation, Status, Time, Duration and Output.
Automations lists every run in the chosen time range. The chips filter by status; Needs approval is where runs wait for a person.

The header counts the runs in the selected range and how many are running or failed.

  • The chips filter by status: All, Running, Needs approval, Failed, Scheduled and Successful.
  • The source filter narrows by trigger: Any source, Schedule, Manual, From a connected app or CI.
  • The range menu offers the Last 24 hours, 7 days, 30 days or 90 days.
  • The table shows Automation, Status, Time, Duration and Output. View output opens the run's artifacts. Re-run starts it again. Copy link copies a link to the run.
StatusWhat it means
waitingQueued, not yet started
scheduledWill start on its schedule
runningIn progress
needs approvalPaused for a person
successFinished
failedEnded with an error
stoppedA person stopped it. Deliberately not the same as failed

From a connected app in the source filter is what the platform calls a webhook trigger.

Start an automation​

Start an automation takes you to the Agents page filtered to workflow agents, where Run workflow on an agent starts a run by hand. The dialog, its inputs and following the run are covered in Start an automation.

Read a run​

  1. Open the run

    Select a row. The run page shows the agent, the run's title, its status and how many of its steps are complete. While it runs you see Step X of Y and a Stop control.

  2. Read the result
    A finished run: the agent and its status, the run title, the Result panel with Copy, Download, Copy link and Re-run, and the collapsed How it ran row.A finished run: the agent and its status, the run title, the Result panel with Copy, Download, Copy link and Re-run, and the collapsed How it ran row.
    A finished run shows its result first. Copy, Download, Copy link and Re-run sit above it; How it ran opens the step-by-step record.

    Result holds what the automation produced, with Copy, Download, Copy link and Re-run above it. If the automation produced a document, Open document takes you to it.

  3. See how it ran
    The How it ran section expanded: the first five of the run's six steps, each with a status tick, a summary line, Show output and a duration.The How it ran section expanded: the first five of the run's six steps, each with a status tick, a summary line, Show output and a duration.
    How it ran lists each step the run took, with its status, a summary and its duration. Show output opens a step's full output.

    How it ran lists each step, its status and its duration, so you can see what happened before you rely on the result.

Approve or reject a paused run​

A workflow can include an approval step. When the run reaches it, the run's status becomes paused, the step line reads Paused for approval, and the page shows the output of the step under review.

  1. Find runs waiting for you

    The Automations entry in the sidebar shows a count of runs waiting for a decision, and Notifications in the top bar lists them under Waiting for your approval. On the Automations page, the Needs approval chip lists them. Runs shared with you for review also appear under Shared with me.

  2. Review
    A run paused for approval: the agent and its paused status, the run title, Step 4 of 5, Paused for approval, the line saying what happens if no one decides in time, Stop, the output under review, and Approve and continue and Reject and stop.A run paused for approval: the agent and its paused status, the run title, Step 4 of 5, Paused for approval, the line saying what happens if no one decides in time, Stop, the output under review, and Approve and continue and Reject and stop.
    A paused run shows the output under review, how long is left before the automatic decision, and the two choices: Approve and continue or Reject and stop.

    Open the run and read the output of the step under review, shown under Reviewing output of and the step's name. If the approval has a deadline, a line above it says how long is left and what happens when time runs out: approved, declined or escalated automatically. How it ran shows what led to it.

  3. Decide

    Approve and continue lets the run carry on. Reject and stop ends it; you can add a rejection reason first. The decision and who made it are recorded on the run.

    If you started the run yourself you cannot decide it. The page says so: a different authorised approver must, as a separation of duties, and the buttons are disabled for you. If two people decide at once, the second sees who won rather than an error.

An approval can also arrive as a link, for example from a notification or a teammate. The approval page shows What needs your decision, who requested it, when, the Respond by deadline and the Reviewers, with the same two decisions. Once decided, the page shows Approved or Rejected, who decided and any note.

The approval request page: the Approval request kicker, the run title, What needs your decision, Requested by, Requested, Respond by, Reviewers, and the Approve and continue and Reject and stop buttons.The approval request page: the Approval request kicker, the run title, What needs your decision, Requested by, Requested, Respond by, Reviewers, and the Approve and continue and Reject and stop buttons.
An approval that arrives as a link opens this page. It states what needs your decision, who asked, and when it must be answered by.

Limits and behaviour​

  • Approvals have a deadline. If time runs out before anyone decides, the run is resolved automatically and the page says so. The deadline is shown as a time, not a ticking countdown, on purpose: the platform holds the real clock.
  • Stop is offered only to the person who started the run, and only when the platform has a live execution to stop. An older run with no execution behind it never offers it.
  • If you are not one of the reviewers, the page says the approval needs an administrator and points you to the Approvals page in the Control Room.
  • A failed run shows the failing step and the error under How it ran. Re-run starts a fresh run; it does not resume the failed one.
  • Stopping a run marks it stopped. Steps that already completed are not undone.

Describes the platform as of .

Was this page helpful?