Slack Approval Workflows: How to Build Them for IT, HR and Finance

Tara Wickramasinghe

|

9 min read

|

Last updated:

|

Last updated:

Share this article

TL;DR

  • A Slack approval workflow turns "can I get access to X?" into a structured request with a named approver, a recorded decision and a timestamp.

  • Slack Workflow Builder can do this on paid plans: a button pauses the workflow until someone clicks it, and branches (Business+ and Enterprise) route the request based on that click.

  • What makes an approval workflow hold up is routing to roles instead of names, a plan for approvers who never answer, and a record you can find later.

  • Invoice and bill-pay approvals usually belong in your AP or expense tool's own Slack integration. IT, HR and ops approvals are where a Slack or Teams workflow pays off.

An emoji reaction is not an approval. It feels like one when a manager thumbs-up a request for Figma access, but it carries no fields, no approver of record and nothing an auditor can pull six months later.

Most teams know this and still run half their approvals that way, because the alternative used to be a portal nobody opens. This guide covers what Slack's own tooling can do for approvals today, where it stops, how to design approvals for IT, HR and Finance, and where Ravenna fits.

What is a Slack approval workflow?

A Slack approval workflow is a repeatable process where someone submits a request in Slack, it goes to the right approver, and the decision gets recorded. The pieces are always the same: a form, routing rules, a decision step with clear buttons, and a log.

It's worth separating this from the other thing "Slack approvals" means. When app approval is turned on, members can request apps and workflow connector steps, and those requests go to Workspace Owners and app managers. That's an admin control over installs. This post is about business approvals: access, spend, exceptions and HR changes.

What can Slack Workflow Builder do for approvals?

Workflow Builder is the native option, and it does more than it used to. Everything in this section comes from Slack's own help center, so check the linked pages if you're reading this much later.

How do branches turn a button into an approval?

Branches send a workflow down different paths depending on what people do, like clicking a button or picking a form answer. You get up to 15 branches, up to 5 more nested beneath a primary branch, and a fallback for when no condition matches. Slack says branches "can help build workflows to automate approval requests based on criteria you specify."

So a basic approval looks like this: a form collects the request, the approver gets a message with Approve and Decline buttons, and each button maps to its own branch. Slack's conditional branching announcement walks through a two-tier expense example, manager first and then a Finance Director.

One catch: branches are only on Business+ and Enterprise, and your workspace must be on "the new version of Business+" to see them. On Pro you get buttons without branching.

Where does Workflow Builder run out?

Workflow Builder is a general automation tool, and its help docs read that way. They don't describe a dedicated approval step, approval reminders, approval timeouts, or looking up the requester's manager from your HR system or identity provider. You pick the people who can click a button when you build the workflow, which is fine until one of them changes roles.

It also only runs in Slack. If part of your company lives in Microsoft Teams, you're building approvals twice or asking someone in Slack to click on their behalf.

None of that makes Workflow Builder the wrong choice. For one team approving a low-risk request, like a new channel or a PTO heads-up, it's quick and comes with a plan you already pay for.

How do you design an approval workflow that holds up?

The tool matters less than the design. Approval workflows break in production for the same handful of reasons, and you can plan for every one of them up front.

Start with one request type and the fields the approver needs

Pick the request that interrupts managers most often. Then ask the approver what they need to say yes without a follow-up question. For software access that's usually the app, the access level, the business reason and how long it's needed; every extra field is one more reason for the requester to go back to DMs.

Route to roles, not names

Hard-coded approvers are the most common failure, and they fail quietly. The person you named leaves or changes teams, and requests sit there with nobody noticing. Route to a role instead: the requester's manager, the app owner, the budget owner, the security group. That only works if your tool can resolve the role from data you already keep, like your HRIS or identity provider.

Decide what happens when nobody answers

Approvers ignore requests. Plan for it with a reminder before the deadline and a defined path after it: escalate to a backup, move it to a team channel, or close it and tell the requester why. Letting it sit is also a decision, just a bad one, because the requester starts pinging the approver directly and you're back to unrecorded DMs.

Keep the record somewhere you can find it

An approval isn't finished until there's a record: the request fields, every approver's decision, timestamps and any decline reason, all tied to one request ID. A Slack thread is good context but a poor system of record once retention policies kick in. Store the decision somewhere you can search when someone asks who approved admin access to production, and when.

Approval workflow examples for IT, HR and Finance

Here's how the most common requests usually break down. Treat the chains as starting points; your risk tolerance and org chart decide the real ones.

RequestWhat the approver needsTypical approval chain
Standard software accessApp, access level, business reasonManager, then app owner
Admin or privileged accessSystem, scope, duration, ticket or incident linkManager and security in parallel, time-limited
New hardwareItem, cost, cost center, replacement or newManager, then IT, Finance above a set amount
Role change or transferNew team, new manager, effective dateOld and new manager, then IT for access changes
HR exceptionDates, reason, policy referenceManager, then HR partner
Software purchase or renewalVendor, cost, term, data handledBudget owner, then security, then Finance

Two patterns stand out. Access requests are where parallel approval earns its keep, because security shouldn't wait on the manager when they're checking different things. Purchases are where conditional routing matters: a $40 plugin and a $40,000 contract shouldn't take the same path.

Should invoice and expense approvals run in Slack?

A lot of people search for Slack approvals with invoices in mind, so here's a straight answer. Invoice, bill-pay and expense approvals should usually live in the AP or expense tool that already holds the bill. That tool posts the decision back to the ledger and keeps the audit trail Finance actually needs. If it has a Slack or Teams integration with approval buttons, use that.

A general Slack approval workflow fits Finance for the requests that never reach the AP system: buying something before there's an invoice, a budget exception, a discount sign-off. Those start as a conversation, so catching them as a structured request in Slack or Teams is the right move.

Where Ravenna fits

Ravenna is an AI-native service desk that runs in Slack and Microsoft Teams, and approvals are built into its tickets and workflows. Here's how it covers the design points above:

  • Approvals in chat: approvers get a Slack DM with Approve and Decline buttons, and in Teams the request arrives as an Adaptive Card, per the approvals docs.

  • Multi-round and parallel approvals: approval rounds run one after another or side by side, with any, all, majority or threshold policies.

  • Roles, not names: approvers can be people, groups, or dynamic roles like the requester's manager, resolved from your HR system or identity provider.

  • Timeouts and reminders: the Wait for Approval step branches into On Approved, On Declined and On Timeout. Reminders go to pending approvers as a private Slack DM with an email fallback.

  • Conditional rounds: an approval flow can skip a round that isn't needed, like the Finance round when the amount is $5,000 or less.

Ravenna's job is to gate, route and log the decision. It doesn't create accounts in Okta or Google Workspace; once an access request is approved, it triggers the action in your identity provider and records what happened. If access is your first approval workflow, this guide to automating software access requests covers the full flow, and the ITSM automation overview covers what to automate next.

I believe the right first move is boring: pick the request your managers approve most often, build it properly with role-based routing and a timeout, and leave everything else alone for a month. If you want to see that in Ravenna, we're happy to show you, or you can look around the workflows page first.

Frequently Asked Questions

How do I create an approval workflow in Slack?

Open Workflow Builder on a paid Slack plan, add a form to collect the request, then add a message to the approver with Approve and Decline buttons. A button pauses the workflow until someone clicks it, and you can restrict who's allowed to click. On Business+ and Enterprise plans, add a branch so each button leads to its own path, like notifying the requester on a decline.

Can Slack Workflow Builder handle multi-level approvals?

Yes, with branches. You can add up to 15 branches and nest up to 5 more beneath a primary branch, which is enough to route a request to a manager first and then to Finance or security. Branches need Business+ or Enterprise, and Slack's help docs don't describe looking up approvers from your HR system, so approvers are set when you build the workflow.

How does the Slack app approval process work?

When app approval is turned on for a workspace, members can request apps and workflow connector steps they'd like to use. Those requests go to Workspace Owners and app managers, and by default only Workspace Owners can review them. Slack lists app requests as available on all plans.

Can managers approve expenses inline in Slack or Teams?

It depends on where the expense lives. If your expense platform has a Slack or Teams integration with approval buttons, managers can decide without opening another app, and the decision syncs back to the ledger. For requests that start as a conversation, a service desk like Ravenna can run the approval in Slack or Teams and log it on a ticket.

How do you get invoice approvals into Slack?

Start with the AP or bill-pay tool that already holds the invoice and check whether its Slack integration sends approval requests to approvers. That keeps the decision tied to the vendor record and the ledger. A general workflow tool can notify people in Slack, but the approval itself should be recorded in the system that pays the bill.

Do Slack approval workflows work in Microsoft Teams?

No. Slack Workflow Builder runs inside Slack only, and Teams has its own Approvals app. If your company uses both, you either build each approval twice or use a platform that runs in both. Ravenna, for example, sends the same approval to Slack as a DM with buttons and to Teams as an Adaptive Card.

Modernize and automate your
service desk with Ravenna

Modernize and automate your
service desk with Ravenna