Add Approvals and Ask People
Workflows can wait for a person. Approvers answer in Automation → Approvals and do not need an Automation role.
Add an approval step
- In the visual builder's Steps tab, drag Request approval (under Flow Control) onto the canvas and connect it.
- Choose Who approves: a person, anyone with a role, or a user id from
the event (for example
{{OwnerId}}). - Write a title and message (merge fields allowed), set a time limit in hours (0 = none) and what happens if nobody answers.
- Connect the Approved port and the Rejected port to what happens next.
- Test with approvals treated as Approved, then Rejected.
The run waits. Approvers get an email (unless they switched approval emails off) and approve or reject with an optional comment. The first answer counts. In the simple builder there are no branches: a rejection ends the run.
Pass an unanswered approval on
- Open the Request approval step and choose Add escalation under If nobody answers, pass it on.
- Enter the hours (counted from when the request was sent) and who it goes to: Their manager, A specific person, or Anyone with a role. Add up to three.
- Keep each escalation earlier than the time limit, or set the time limit to 0.
Each new approver is emailed once and sees the request marked Escalated. Earlier approvers can still answer, and the first answer wins. If an approver has no manager on their employee record, that escalation is skipped.
Approve the expense or order itself
- After the Request approval step, add Approve the Document on the Approved path. In the visual builder you can add Reject the Document on the Rejected path.
- Choose the document (expense claim, purchase order, purchase requisition
or leave request) and its id, usually a merge field such as
{{ExpenseId}}.
The document is approved or rejected as the person who answered, with their comment. It only happens if that person may approve that document on its own screen; otherwise it is left as it is and the run shows why. A time limit that runs out never approves a document.
Ask a person for information
- Add Request approval and choose Fill in a form (Ask a person).
- Choose who fills it in, the title and the message.
- Add the form fields and keep the name for later steps, for example
ask. - Connect Submitted and Timed out.
The person fills the form in Approvals, on a phone too. Later steps use
{{steps.ask.Fields.CountedQty}}, {{steps.ask.SubmittedBy}}. A time limit
that passes never counts as an answer.
Ask a supplier or customer to confirm
- Add Ask Someone Outside. Choose email or SMS and the address or number.
- Write the message and the answers, for example Confirm and Decline. The first answer is the "yes" one. Tick Ask for a date and Allow a comment as needed.
- Set the time limit and a name, for example
reply. - Connect Confirmed and Other or no answer.
The person gets a private one-click link, no login. Later steps use
{{steps.reply.Answer}}, {{steps.reply.ProposedDate}} and
{{steps.reply.Comment}}. With no answer in time the run takes the other path
with the answer no-answer. Links work once.
Escalate a CRM record
- Add the Escalate step to a workflow about a CRM lead, deal, contact or account (for example after a Wait for event that timed out).
- Choose The owner's manager or a specific person, and write a note.
The record gets a new owner and they receive an email with your note.
:::info Automation never replaces module approvals Expense stages and purchase approvals stay in their modules. These steps add an approval inside a workflow. :::
Related articles
Learn more about Biznsbook Automation on biznsbook.com.