How to Add Approval Steps to Workflows
Approvals happen in inboxes the workflow cannot see
Large purchases, discounts and refunds need a manager’s yes, but the request goes by email and the follow-up is done by hand.
When nobody answers, the request sits for days because nothing reminds anyone or decides what happens next.
Approvers need full system access just to say yes or no, which widens permissions for the wrong reason.
Why this happens
- Connecting only the Approved port, so a rejection ends the run with nobody told.
- Leaving the time limit at 0 hours (no limit) on requests that must be decided.
- Choosing a role nobody holds, so no one sees the request.
- Forgetting that the first person with the role to answer decides.
Biznsbook addresses this through Request approval step, Approvals inbox, Approved and Rejected branches, approval time limit when Business Automation is licensed — start delays, schedule triggers and approval steps run in the background and every run is logged.
Teams lose hours each week to follow-ups, reminders and approvals that live in inboxes and spreadsheets. Making Biznsbook Automation the one place where these rules run — with roles deciding who can switch them on and run history showing what happened — stops silent gaps and duplicate messages.
Step-by-step: Add Approval Steps to Workflows
Built for operations leads timing Biznsbook Automation workflows — start delays with cancel-on-event, recurring schedules, and approval steps with time limits.
- Open the workflow. Go to Automation → Visual Builder and open or create the workflow — for example one triggered when a purchase order is created.
- Add Request approval. On the Steps tab, under Flow Control, drag Request approval onto the canvas and connect it after the trigger or condition.
- Choose who approves. Under Who approves? pick A specific person, Anyone with a role (the first to answer decides), or A user from the event and enter the merge field, such as {{OwnerId}}.
- Write the request. Enter a Request title, such as Approve {{DocumentNumber}}, and a Message to the approver with the details they need. Keep Also email the approver ticked to send an email.
- Set the time limit. Enter a Time limit (hours) from 0 to 720 — 0 means no limit — and choose under If nobody answers whether the request is treated as approved or rejected.
- Connect both answers. Drag from the Approved port (left) to the steps that follow a yes, and from the Rejected port (right) to the steps that follow a no, such as notifying the requester.
- Test, save and activate. Click Test to see both paths, then save. An Automation Manager activates the workflow. Approvers answer in Automation → Approvals and need no Automation role.
Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.
Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.
Common mistakes to avoid
- Mistake 1: Connecting only the Approved port, so a rejection ends the run with nobody told. Repeating this each month usually shows up first in missed runs, late escalations or unanswered approvals.
- Mistake 2: Leaving the time limit at 0 hours (no limit) on requests that must be decided. Repeating this each month usually shows up first in missed runs, late escalations or unanswered approvals.
- Mistake 3: Choosing a role nobody holds, so no one sees the request. Repeating this each month usually shows up first in missed runs, late escalations or unanswered approvals.
- Mistake 4: Forgetting that the first person with the role to answer decides. Repeating this each month usually shows up first in missed runs, late escalations or unanswered approvals.
Note each recurring failure on the Runs page in your weekly review; each should map to a step in this guide.
Best practices that hold up as you scale
- Open the workflow — Go to Automation → Visual Builder and open or create the workflow — for example one triggered when a purchase order is created.
- Add Request approval — On the Steps tab, under Flow Control, drag Request approval onto the canvas and connect it after the trigger or condition.
- Choose who approves — Under Who approves? pick A specific person, Anyone with a role (the first to answer decides), or A user from the event and enter the merge field, such as {{OwnerId}}.
- Write the request — Enter a Request title, such as Approve {{DocumentNumber}}, and a Message to the approver with the details they need.
- Set the time limit — Enter a Time limit (hours) from 0 to 720 — 0 means no limit — and choose under If nobody answers whether the request is treated as approved or rejected.
Teams that pair every start delay with a cancel event, preview the next runs of every schedule, and give every approval a time limit avoid orphan escalations.
How Biznsbook supports this workflow
Request approval step is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.
Approvals inbox is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.
Approved and Rejected branches is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.
approval time limit is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.
Only an Automation Manager activates a workflow; Builders use Save & request activation, Operators can run, pause, resume and retry, and approvers need no Automation role.
Suggested implementation timeline
- Week 1: List the follow-ups and approvals you repeat by hand and build a first draft with Request approval step.
- Week 2: Test the draft with sample data, check the highlighted path, and have an Automation Manager activate it.
- Week 3: Review the Runs page daily, retry failed runs, and tighten conditions that fire too often.
- Week 4: Add branches, approvals or schedules where the first workflow proved its value.
- Ongoing: Weekly review using approval design tip and the Runs page.
Choosing the approver
A specific person suits fixed sign-offs, such as the owner approving large refunds. Anyone with a role suits shared queues: the request goes to everyone with the role and the first person to answer decides.
A user from the event uses a merge field such as {{OwnerId}}, so the record’s own manager or owner gets the request. Check the field is filled on the records the workflow runs on.
Time limits and default answers
The Time limit runs from 0 to 720 hours (30 days); 0 means the run waits until someone answers. Under If nobody answers, choose Treat as rejected for spending and risk decisions, and Treat as approved only where silence really means consent.
Time limits are checked about every five minutes, so a request that passes its limit is closed within a few minutes and the matching branch runs.
Building both branches
The Approved port is on the left of the step and the Rejected port is on the right. Connect each to the steps that should follow — for example send the purchase order to the supplier on Approved, and notify the buyer on Rejected.
Click Test to see both paths before you save. On a real run, Show path on canvas on the Runs page highlights which branch was taken.
Approvers and Automation roles
Approvers need no Automation role. Anyone a request names can open Automation → Approvals, read the message and approve or reject. Their email follows their own email preferences.
Building and activating the workflow is still controlled: Builders draft it and request activation, and only an Automation Manager switches it on.
Metrics to track monthly
- Delayed workflows that also set a cancel event
- Failed runs retried within one working day
- Scheduled workflows whose next runs match the plan
- Approval requests answered before the time limit
- Documented cancel, schedule and timeout tests in the go-live checklist
Start with three metrics; trend direction matters more than a single point-in-time snapshot.
Manual follow-ups vs Biznsbook Automation
Compare running this by hand with Biznsbook Request approval step and related capabilities.
| Capability | Manual / Spreadsheet | Biznsbook |
|---|---|---|
| Where the request lives | ❌ Personal inbox | ✅ Approvals inbox |
| Who approves | ❌ Whoever is copied | ✅ Person, role or user from the event |
| No answer | ❌ Request sits for days | ✅ Time limit with a set outcome |
| After the answer | ❌ Manual follow-up | ✅ Approved and Rejected branches |
| Approver access | ❌ Full system rights | ✅ No Automation role needed |
| Audit | ❌ Email thread | ✅ Run history with the answer |
Approval design tip
Always connect both ports and give every request a time limit. A rejected or unanswered request should still tell someone what happened, so nothing waits silently. Name the step after the decision, such as Approve PO over 5,000, so the Approvals inbox and run history read clearly.
Write this into your automation runbook and revisit it when you add workflows, roles or modules.
Frequently asked questions
Can a workflow wait for a manager’s approval?
Yes. The run pauses at the Request approval step until the approver answers or the time limit passes, then follows the Approved or Rejected branch.
Where do approvers answer?
In Automation → Approvals. They also get an email if Also email the approver is ticked and their email preferences allow it.
What happens if nobody answers?
When the time limit passes, the request is treated as approved or rejected — whichever you chose under If nobody answers. A time limit of 0 hours waits without limit.
Do approvers need an Automation role?
No. Anyone a request names can open Approvals and answer it, without Automation Manager, Builder, Operator or Viewer rights.
Can one workflow have more than one approval?
Yes. Add another Request approval step on the Approved branch for a second sign-off, such as a manager and then finance.
Can I see who approved?
Yes. The run history records the outcome, and Show path on canvas shows which branch the run followed.
How this differs by industry
Retail
Retail chains ask the store manager to approve return requests above a set amount before the refund goes ahead.
Wholesale & distribution
Distributors route purchase orders over 5,000 to anyone with the Finance Manager role and email the buyer if they are rejected.
Manufacturing
Plants ask the quality lead to approve releasing a batch after a failed inspection is reworked, with a 24-hour time limit.