Skip to content

Multiple approvers

One Approval node takes one decision. You can list several approvers, and the first person to decide settles the request. When you need more than one sign-off, chain Approval nodes.

A canvas with two Approval nodes in a row, Manager Approval then Finance Approval, the first one's Approved output wired to the second, and both Rejected outputs wired to a Notify requester email node.A canvas with two Approval nodes in a row, Manager Approval then Finance Approval, the first one's Approved output wired to the second, and both Rejected outputs wired to a Notify requester email node.

Several approvers on one node

Add each person under Approvers with Add approver +. With Approval Type Email, each of them gets the request email with the same link.

The first decision wins. As soon as one person approves or rejects, the run continues and the link stops working for everyone else. Later attempts see "This approval request has already been completed".

The Approval Strategy setting does not change this. Whatever you pick, one decision settles the request. Use several approvers for cover ("any manager can sign off"), not for joint sign-off.

Joint sign-off: chain Approval nodes

To need two or more people, put one Approval node per sign-off in a row:

Workflow: Invoice received to Manager approval, Manager approval to Finance approval, Finance approval to Pay invoice, Manager approval to Notify requester, Finance approval to Notify requester Invoice receivedAPI/Webhook TriggerManager approvalApprovalFinance approvalApproval Pay invoiceHTTP RequestNotify requesterEmail
  • Each node asks its own approvers, in order. Finance sees the request only after the manager approves.
  • A rejection at any step ends the chain. Wire every Rejected output to the same handler.
  • Each node's output records its own decision, so you have who approved each step and when.

Approve only what needs it

Put an If node in front of the Approval node and send only the risky branch through it:

Workflow: New purchase order to Over 5,000?, Over 5,000? to Finance approval, Finance approval to Create PO, Over 5,000? to Create PO New purchase orderForm Trigger Over 5,000?IfFinance approvalApproval Create POHTTP Request Create POHTTP Request

Small orders go straight through. Large ones wait for finance.

Recording who decided

Each Approval node adds approved, comment, approvedBy / approvedAt or rejectedBy / rejectedAt, and timeToApproval to its output. See The node's output.

To keep a record beyond your execution history, write these fields to a Database node or another system after each approval.

Tips & gotchas

  • Chains add up. If each approver takes a day, a chain of three takes three days.
  • Anyone in the workspace can decide in the app. The Approvers list sets who gets the email. It does not restrict who can approve from Approvals. If only certain people may sign off, use Slack Wait for response with Who can respond set.
  • Need a deadline? The Approval node waits until someone decides. Use the Slack connector's Wait for response, which has a working timeout. See Approvals in Slack.

Found something out of date? This page lives in the Flero docs content set.