Automation by function

Internal approvals automation: requests and sign-offs on n8n

How purchase, leave and expense requests move from the person who raises them to the person who approves them without chasing: form, routing, reminders, record.

By the RinooSol team Published ⁨4⁩ min read

An approval is a small decision that a lot of work waits on. A purchase cannot be made, a leave cannot be planned, an expense cannot be reimbursed until someone says yes, and in most companies that someone is reached by a WhatsApp message in a group, an email that scrolls away, or a question in the corridor. The request itself lives nowhere, so nobody knows what is waiting or how long. An approvals system gives every request a number, a route, a reminder and a record, and lets the approver say yes from a phone. This is how it is built on n8n and what you decide.

What counts as an approval

Anything with a requester, an approver and a yes-or-no:

  • Purchase requests and purchase orders
  • Leave and work-from-home requests
  • Expense claims and petty cash
  • Discounts and credit notes above a threshold
  • New supplier or new customer onboarding
  • Content or design sign-off before publishing

They share one shape, which is why one workflow template serves all of them with different forms and routes.

Piece 1: the request has one door

A short form replaces the group message: Google Forms, a form on your intranet, or an n8n form trigger. It asks only what the approver needs to decide: for a purchase, the item, quantity, supplier, amount and reason; for leave, the dates and the cover. The submission lands in a sheet or a small database with a number, a timestamp and a status of waiting.

A request that arrives by WhatsApp anyway, because people will, can be caught by the WhatsApp API and turned into the same row, with a reply that gives the requester the number.

Piece 2: routing by rule

An if or switch node picks the approver from rules you write once:

  • By amount: under a threshold, the department lead; above it, the owner; above a second threshold, both in sequence.
  • By type: leave goes to the line manager, expenses to finance, content to the editor.
  • By branch or team: the requester's record says which.

The approver receives a WhatsApp message or an email with the request summary and two links: approve and reject. Tapping either records the decision with who and when; a rejection asks for one line of reason. The approver never opens a system.

Piece 3: reminders instead of chasing

If the request is still waiting after a period you set, the approver is reminded and the requester is told the request is still open. After a second period, a manager is copied, or the request escalates to a backup approver. Nothing is ever lost in a chat; it is either decided or visibly overdue.

For a two-stage approval, the second stage starts only when the first is approved, and the requester sees which stage the request is at.

Piece 4: what happens after yes

The yes is where the system pays for itself: the workflow does the next step without anyone being told.

  • A purchase approval notifies purchasing with the details, or creates the purchase order in the accounting system.
  • A leave approval writes the dates to the team calendar and tells the cover person.
  • An expense approval creates the reimbursement entry and tells finance.
  • A content approval publishes, or moves the file to the approved folder.

The requester is told the outcome in the channel they used, and the row moves to approved or rejected with the decision attached.

Piece 5: the record and the weekly list

Every request is a row with its history: who asked, when, who decided, when, and the outcome. A scheduled workflow sends each approver their open items every morning, and the owner a weekly summary: requests by type, average time to decision, and the ones that waited longest. The afternoon that used to go into building a report from a chat history is gone.

What to decide before building

  • The thresholds and the approvers, kept in a settings sheet you edit, not in the workflow.
  • Who can be a backup, and after how long.
  • Which approvals have a second stage.
  • What the "after yes" step is for each type, because that is where the value is.

Where this fits

The operations automation page shows this system for a trading company's purchase requests, and the finance page the invoice approval that uses the same shape. A free consultation is where we list your approval types and write the first rule with you.

Read next

Tell us what you do by hand today

Book a free consultation and we will design the automation with you.

We reply in Arabic or English

Last updated: