How do we automate approvals across email, Slack and the CRM?
Write an approval matrix, keep the decision on the CRM or ERP record, send requests to Slack or email, escalate when nobody answers, and keep an audit trail.
- Time needed
- 45 min
- Steps
- 5
- Level
- Intermediate
In short: Make the CRM or ERP record the single source of truth for an approval, and use Slack buttons and email links only as ways to answer it. Write an approval matrix that says who approves what and at which amount, send the request to the right person with all the details, record the decision and the approver on the record, and escalate when nobody answers. Build it in the tool you already use: n8n, Make, Zapier or Power Automate can all do this.
Step 1: Write the approval matrix
| Request | Condition | Approver | Escalate after | Escalate to |
|---|---|---|---|---|
| Discount | Up to 10% | Sales manager | 4 working hours | Head of sales |
| Discount | Over 10% | Head of sales | 1 working day | CEO |
| Purchase order | Under your first limit | Department head | 1 working day | Finance |
| Purchase order | Over your first limit | Finance and department head | 1 working day | CEO |
| Change order | Any change to price or date | Project owner | 4 working hours | Operations lead |
Use your own limits. The point is to write them down before you automate. Our guide to building a PO and change order approval matrix goes deeper.
Step 2: Keep the decision on the record
Add three fields to the deal, order or ticket: Approval status (Pending, Approved, Rejected), Approved by and Approved at. Every channel writes to these fields. That way the CRM shows the truth, reports work, and later steps (create the invoice, send the contract) trigger only on Approved. This is the core of an ERP approval workflow.
Step 3: Send the request where the approver already is
| Channel | How it works | Watch for |
|---|---|---|
| Slack | A message with the key details and Approve / Reject buttons | Only the named approver's click counts |
| A message with signed, single-use approve and reject links | Links should expire and not work twice | |
| CRM task | A task on the record with the details | Easy to miss without a notification |
| Teams | An adaptive card with buttons (Power Automate approvals) | Same rules as Slack |
Include what is being approved, the amount, who asked, why, and a link to the record. Approvers should not have to open three tools to decide.
Step 4: Escalate and remind
- If no decision arrives in the time from the matrix, remind the approver once.
- If there is still no answer, send to the escalation approver and note it on the record.
- If someone rejects, ask for a reason and send it back to the requester.
Step 5: Keep an audit trail
Log each request, reminder, escalation and decision with time and person. For money decisions, store the values that were approved, so a later edit to the amount sends it back for approval.
Tool options
| Tool | Approval feature |
|---|---|
| n8n | Send-and-wait steps for Slack, email and other channels, plus Wait nodes |
| Make | Slack or email modules with webhooks for the response |
| Zapier | Human in the Loop approval steps and Slack actions, with Paths for approve or reject |
| Power Automate | Built-in approvals in Teams and Outlook |
Choose the one your team already uses. The design above matters more than the tool.
FAQ
Should approvals live in Slack or the CRM?
Both, with different jobs. Slack or email is where people answer; the CRM or ERP record is where the decision is stored and what other steps rely on.
How do we stop the wrong person approving?
Check the clicker's identity against the approver in the matrix before writing the decision, and ignore anyone else's click.
What if the amount changes after approval?
Reset the status to Pending and send it for approval again.
Do we need an approval tool?
Usually not. Most teams can do this with their CRM and an automation tool they already pay for.
How Octacer helps
Octacer builds approval workflows across email, Slack, Teams and the CRM or ERP. If approvals are stuck in threads today, read why approvals should not live in Slack and email chains and our PO and change order approvals use case.
Next step
Write your approval matrix on one page, including who approves and when to escalate. Then book a call and we will help you automate it.
Sources
- n8n Docs, Wait node: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.wait/
- Microsoft Learn, Get started with Power Automate approvals: https://learn.microsoft.com/en-us/power-automate/get-started-approvals
Keep going
More guides
Want it running on your stack?
We implement this guide for clients, tailored to your stack, your data, and your team's workflow, and handed over documented.