Skip to main content
Use approval steps to stop a workflow until the right people approve a request, then continue down a different path for approved, declined, and timed-out requests. An approval in a workflow has two parts: a step that puts approvers on the ticket, and a step that waits for their decision.

Add approvers

Add Approval Round

Use Add Approval Round to ask specific people or groups to approve, such as the requester’s manager or an application owner.
  • Approvers: people or user groups. Groups are expanded to their members.
  • Approval Policy: how many approvers must approve. Any can approve (the default), All must approve, or Majority must approve.
  • Assignment Strategy: who from the list becomes an approver.
Each Add Approval Round adds a new round and sets the ticket’s approval back to in progress, so a Wait for Approval after it waits for the new round. The step’s output lists the Approvers it added.
Approvers who are deactivated, bots, or no longer members of your organization are left out. If nobody is left, the step is skipped, a private note on the ticket says that an admin needs to update the workflow, and nothing after the step runs.
Auto Approve only approves when the ticket has no approval in progress. If it already has an active round, the step adds everyone in the list instead, as if you’d chosen All.

Apply Approval Template

Use Apply Approval Template to reuse a multi-round approval chain you’ve saved as a template, such as manager approval followed by security review.Choose the Template. The step removes the ticket’s existing approval rounds, adds the template’s rounds, and starts the first one. The template’s own settings, such as skip conditions and dynamic approvers, apply as usual. The workflow moves on as soon as the rounds start, so add Wait for Approval after it to gate later steps.
Learn more about approval templates and approval rounds

Add Approvers

Older workflows may use Add Approvers. It still runs, but Add Approval Round replaces it and adds a choice of approval policy. Use Add Approval Round in new workflows.

Wait for the decision

Wait for Approval pauses the workflow until the ticket’s approval finishes across all of its rounds, or until the timeout passes.
  • Duration: the longest to wait. The default is 3 days.
If the ticket’s approval has already finished when the step runs, it continues right away.The step has three paths:On Declined only covers an actual decline. Put anything that should happen to a stalled request, such as adding a backup approver or notifying the requester, on On Timeout.

Use who decided

Wait for Approval outputs:
  • Is Approved: whether the ticket was approved.
  • Approved By and Declined By: the people who approved or declined, across all rounds.
  • Force Approved By: the admin who force approved the ticket, when that happened.
Example: On On Declined, send a message that mentions Declined By, so the requester knows who to follow up with.The approver’s decline reason is posted on the ticket automatically, so you don’t need to send it yourself. See decline reasons.

Start a workflow when an approval finishes

The Ticket Approval trigger starts a workflow when a ticket’s approval is approved or declined, wherever the approval came from: a workflow, a form, or someone adding approvers on the ticket. It splits into Approved and Declined paths, and outputs Is Approved, Approved By, and Declined By.Use it to keep follow-up work in its own workflow, such as provisioning access whenever a ticket in an access channel is approved.

Tips

  • Set a timeout you can act on. Decide what should happen after the timeout and build that on On Timeout, rather than leaving the run waiting.
  • Use templates for multi-step chains. If several workflows ask the same people in the same order, save the chain as an approval template and apply it.
  • Keep approver lists current. A round whose approvers have all left is skipped, so prefer user groups over named individuals.
Last modified on November 18, 2026