How to set up a multi-level approval chain in GoHighLevel

By Jake Marsh · Updated

To build a multi-level approval chain in GoHighLevel, use one Okaygate Request approval step with Steps set to 2 or 3. Each level has its own approvers and its own rule (any one, all, or a number of them), and a level starts only after the one before it approves. The contact waits on the single workflow step until the whole chain is decided, then continues down Approved, Rejected or Expired.

Example: refunds over $500

LevelApproversWho must approve
1. ManagerTeam members: the two support leadsAny one approver
2. FinanceEmail addresses: the bookkeeperAny one approver
3. OwnerTeam members: the ownerAny one approver

A support lead approves from a text, which sends the request to the bookkeeper by email; the owner sees it last. If anyone rejects, the chain stops and the contact goes down Rejected with that person's comment.

Steps

  1. Trigger on the refund request: a form, a tag such as refund-requested, or an opportunity stage.
  2. Add Request approval. Title: Refund {{contact.name}}. Details: amount, order and reason.
  3. Set Steps to 3 and fill in each level's approvers and rule as in the table.
  4. Choose Send by per your team: SMS for people away from a desk, email for finance.
  5. When a step is rejected: keep "on the first rejection" for a chain like this.
  6. Expires after (hours): long enough for all three levels, for example 120.
  7. Approved path: issue the refund or create a task to do it. Rejected path: tell the customer, using comment for the reason in an internal note first.

Voting levels: 2 of 3

For a committee, put three people on one level and set Who must approve to a number, 2. Then pick what a rejection means:

  • On the first rejection: one no ends the request.
  • Only when approval can no longer be reached: one no doesn't end it while 2 yeses are still possible; it ends when a second person rejects.

See where a request is

The decisions page lists Pending requests with every level, who has decided and who hasn't. steps_total and steps_approved come back to the workflow when it's decided. Send a reminder now nudges everyone who hasn't answered on the current level, and an admin can decide for the current level when someone is away.

When the workflow shouldn't wait

If other steps should run while the chain is out, use Start approval with the same fields. It returns request_id right away. A second workflow starting with the Approval decided trigger, filtered on outcome or approval_name, picks up the result.

What it costs

Okaygate is $29 a month or $290 a year per sub-account after a 14-day trial of up to 100 requests, with up to 2,000 requests a month. A three-level request counts as one request. Install it from the Okaygate page.

Okaygate: Workflow Approvals

Pause any workflow until the right people approve, by email or text, with a full history. $29 a month or $290 a year per business account.


Questions

Can I have more than three levels?

A request has up to 3 steps. For more, put a second Request approval after the first one's Approved path.

Can different requests go to different approvers?

Yes. Use If/Else before the step, or set approvers from a contact field, such as an account manager email stored on the contact.

Does each level get its own deadline?

The deadline covers the whole request. Reminders go out on the current level until it's decided.

Who sees the requests on the decisions page?

Everyone on the sub-account sees the list. Waiting on me shows only requests on the current level where you are an approver.


More Okaygate guides


More HighLevel guides