How to Automate Business Processes Without Coding

Build one full purchase-request approval process without coding: map it, branch by amount, add approvals in Zapier, test, document, monitor and cost it.

10/12/202626 min read

Most small businesses don't need another list of tools.

They need one messy, real process fixed from start to finish.

A purchase request arrives in Slack. Someone pastes it into a spreadsheet. A manager says "looks fine" in a thread nobody can find later. Finance hears about it after the card has already been charged. Three weeks on, nobody can say who approved what.

That is a business process. It isn't glamorous. It is exactly the kind of work you can automate without writing code — if you treat it as one connected flow instead of a pile of one-off shortcuts.

This guide is a hands-on build, not an introduction to no-code. We'll take one realistic process for an imagined 12-person digital marketing agency, Brightline Creative, and automate it end to end: map the current steps, define the trigger, inputs, decisions and outputs, pick the tools and explain why, build every step in Zapier with menu-level actions that match Zapier's current help docs, add branching and approvals, handle errors, test with sample data, document the handoff, monitor it, and cost it with prices checked live on the vendors' official US pages.

If you want the basics of triggers and actions first, start with our beginner's guide to no-code automation. If you want a library of short blueprints rather than one deep build, see 20 real-world AI automation workflows. Here we stay on one process until it runs.

The process we'll build: a purchase-request approval flow — the path from "I need to buy this" to "approved, logged, and the requester notified," with amount-based branching and human approvals. That is different from expense reimbursement (money already spent) and from invoice intake (a vendor bill arriving), which appear only as short blueprints elsewhere on the site.

What "Automate a Business Process Without Coding" Means Here

A business process is a repeatable set of steps that moves work from a clear start to a clear finish. Think of it as a relay race, not a single sprint. The baton is information: a request, a decision, a record, a notification.

Automating that process without coding means connecting the apps you already use so the baton moves on its own, using a visual builder instead of a programming language. Zapier calls each automated workflow a Zap. A Zap starts with a trigger (the event that fires it) and continues with one or more actions (the things it does) (Zapier key concepts).

What we are not doing in this article:

Explaining every no-code platform (covered in our tools roundup).
Teaching an 8-step method for picking tasks (see how to automate repetitive business tasks with AI).
Building an AI chatbot or a support desk (separate guides).
Writing custom code, scripts or APIs (application programming interfaces — the "waiters" that let software take each other's orders).

We are building one process the way a careful operations lead would: map first, automate second, leave a paper trail, and tell the next person how it works.

The four pieces every automated process needs

Almost every solid build uses the same four pieces. Miss one and the workflow feels clever for a week, then falls apart.

Trigger: the event that starts the run. A form is submitted. A row is added. A status changes.
Inputs: the data the process needs. Amount, vendor, reason, requester email.
Decisions: the forks in the road. Under $200 auto-log. Over $2,000 needs finance.
Outputs: what the business needs at the end. An updated log, a Slack ping, an email to the requester, a clear Approved or Declined status.

There's a fifth piece beginners forget: the record. A timestamp, a decision field, a note from the approver. Without it, you're back to hunting through chat threads when someone asks "who signed off on that ad spend?"

Meet Brightline Creative (Our Imagined Business)

Brightline Creative is a made-up 12-person digital marketing agency. They run ads, design landing pages and manage content for about 25 clients. They are not a tech company. Most of the team lives in Google Workspace, Slack and a project tool.

Their purchase-request problem looks familiar:

Designers need stock photo credits and plugin licences.
Media buyers need to top up ad accounts.
Account managers want to hire a freelance copywriter for a two-week burst.
The office lead needs a new monitor.

Today, those requests arrive as Slack messages, email forwards and hallway conversations. The founder approves some. A manager approves others. Nobody can find the trail.

We'll automate that without pretending Brightline has an IT department.

Step 1: Map the Current Process (As-Is)

Before you open Zapier, draw the process as it actually happens — not as the handbook pretends it happens.

Brightline's as-is purchase request flow looks like this:

Someone needs a purchase → messages their manager in Slack → manager replies "ok" or "ask Maya" → requester buys it on a personal card or asks finance for the company card → receipt lands in email → someone maybe adds a row to a spreadsheet → month-end, finance chases missing receipts.

Write it as an arrow chain so gaps become obvious:

Need arises → Slack ping → informal yes/no → buy → receipt somewhere → optional spreadsheet row → month-end scramble.

Where time and trust leak

In our made-up illustration, Brightline handles about 40 purchase requests a month. Each one burns roughly 15 minutes of back-and-forth across requester, manager and finance — about 10 hours a month, or 120 hours a year. At a blended internal cost of $35/hour (a made-up figure for illustration), that is about $4,200 a year of coordination, before you count the late fees, duplicate tools and "wait, we already pay for that" surprises.

Mapping isn't bureaucracy. It's like photographing the kitchen before you redesign it. You need to see where the crumbs actually fall.

Capture the people and the systems

List every human role and every tool that touches the process today:

Requester (any employee)
Manager (approves routine spend)
Finance / ops lead (approves large spend, owns the budget)
Tools in play: Slack, Gmail, Google Sheets (a messy "Purchases" tab), company cards

Anything that only lives in someone's head is a risk. Those invisible steps are the first ones an automation will trip over.

Step 2: Define Trigger, Inputs, Decisions and Outputs (To-Be)

Now design the to-be process — the version you want the automation to enforce.

Trigger

A team member submits the Purchase Request Google Form.

That single front door replaces Slack DMs, email and hallway asks. If it isn't in the form, it isn't a request.

Inputs (form fields)

Keep fields short and exact. Automations are literal. "done", "Done" and "DONE " are three different values to a computer.

Brightline's form fields:

Requester name (short text)
Requester email (email)
Manager email (email) — who should approve routine amounts
Item or service (short text)
Category (dropdown: Software, Ads, Freelance, Equipment, Other)
Vendor (short text)
Amount USD (number)
One-time or recurring? (dropdown)
Needed by (date)
Business reason (paragraph)
Link or quote (URL, optional)
Urgency (dropdown: Normal, Urgent)

Dropdowns beat free text for Category and Urgency. Google Forms can require answers and validate email format so garbage data never starts the Zap (Google Forms help).

Decisions (amount tiers)

Brightline picks three clear tiers. Write them down where everyone can see them:

Tier A — $0 to $200: auto-approve for logging. Slack posts to #purchases for visibility. Requester gets a confirmation email. No human pause.
Tier B — $201 to $2,000: manager must approve via Zapier's Human in the Loop (a built-in pause that waits for a person to approve or decline before the Zap continues) (Zapier Human in the Loop).
Tier C — over $2,000: manager approves first, then finance approves. Two human checkpoints.

These numbers are Brightline's policy, not a universal rule. Your tiers should match your real risk. A $200 plugin is different from a $2,500 annual SaaS contract (SaaS means software as a service — tools you rent online by subscription).

Outputs

Every finished run should leave:

A row in the Purchase Requests Google Sheet with status Approved, Declined or Auto-approved
A Decision and optional Reviewer note
A Slack message in #purchases
An email to the requester
Timestamps for submitted and decided

If an auditor — or your future self — can't reconstruct the story from the sheet alone, the process isn't done.

Success criteria before you build

Agree these out loud:

1. No purchase request is "approved" only in a Slack thread.

2. Amount tiers are enforced by the Zap, not by memory.

3. Declines still notify the requester with a reason.

4. Errors alert a named owner within an hour.

5. A new hire can run a test request on day one using the handoff doc.

Step 3: Pick the Tool Stack (and Why)

You could build this in Make, n8n, Power Automate or a dozen other platforms. Our no-code tools roundup compares them. For Brightline's build we deliberately pick a small, familiar stack:

Front door — Google Forms: free, everyone already knows it, and responses can land in Sheets (Google Forms help).
System of record — Google Sheets: a simple audit log; prepare it the way we describe in how to automate Google Sheets workflows.
Automation engine — Zapier: multi-step Zaps, Paths for branching, Human in the Loop for approvals, and wide app coverage (Zapier pricing).
Team visibility — Slack: where Brightline already lives; HITL can notify via Slack (Zapier HITL).
Requester updates — Gmail: reliable confirmation and decline emails.

Why Zapier for this build

Three features matter more than brand preference here:

1. Paths — branching logic so Tier A, B and C can live in one Zap ("If A, then X. If B, then Y.") (Zapier Paths).

2. Human in the Loop → Request Approval — pauses the Zap until a reviewer approves or declines (Zapier HITL).

3. Error handling and Autoreplay — so a flaky connection doesn't silently drop a $1,800 request (Zapier custom error handling) (Zapier replay).

Plan reality check (read this before you subscribe)

Zapier's own docs and pricing page set clear gates:

Paths and multi-step Zaps need a paid plan with those features — Zapier's feature comparison lists Filters & Paths on Professional and above, not on Free (Zapier pricing).
Human in the Loop needs a paid Zapier account (it is a premium app). On a Professional account you can only send approval requests to yourself. On Team or Enterprise, you can route reviews to other members — which Brightline needs for manager + finance (Zapier HITL).
Custom error handlers are available on Team and Enterprise (Zapier custom error handling).
You must share the Zap with designated reviewers so they can open the approval link (Zapier HITL).

Brightline's choice: Zapier Team, so managers and finance can both review. Slack Free is enough for channel notifications. Google Forms and Sheets stay on Google accounts they already have.

Step 4: Build the Google Form (the Front Door)

Open a browser and go to forms.google.com.

1. Click Blank form.

2. Name the form Brightline Purchase Request.

3. Add the fields listed in Step 2. For Category, One-time or recurring, and Urgency, click the field type dropdown and choose Multiple choice or Dropdown, then enter the exact options you'll reference later in Paths.

4. Click the Settings gear. Under Responses, turn on Collect email addresses if you want Google to capture the signed-in email automatically — Brightline still keeps a Requester email field so freelancers without a company login can be covered later.

5. Click the Responses tab, then click the Sheets icon to Link to Sheets. Create a new spreadsheet named Brightline Purchase Requests. Google will add a form-responses tab; we'll also use a cleaner Log tab that Zapier writes to, so the audit trail isn't only raw form output (Google Forms help).

Publish the form when you're ready to share it. Brightline pins the link in the #purchases Slack channel and adds it to the company wiki. From now on, "message me an approval" is not a valid request.

Tip: put a one-line policy at the top of the form description: "Software and ads under $200 are auto-logged. $201–$2,000 need your manager. Over $2,000 need manager + finance." People behave better when the machine shows the rules.

Step 5: Prepare the Google Sheet Log

Automations are picky about spreadsheets. People forgive messy headers. Zaps don't.

In Brightline Purchase Requests, create a tab named Log with this header row starting at A1 (one header per column, no merges, no blank header cells):

A: Request ID
B: Submitted At
C: Requester Name
D: Requester Email
E: Manager Email
F: Item
G: Category
H: Vendor
I: Amount USD
J: Recurring
K: Needed By
L: Reason
M: Link
N: Urgency
O: Status
P: Decision Notes
Q: Decided At
R: Approver

Freeze the header row. Turn column O into a dropdown with Pending, Auto-approved, Approved, Declined, Error. That matches the advice in our Google Sheets workflows guide: one clean header row, one row per record, no blank rows in the middle, dropdowns for values the Zap will filter on.

Leave the sheet empty below the header. Zapier will add rows at the bottom.

Step 6: Create the Zap and Set the Trigger

In your Zapier account:

1. In the left sidebar, click + Create.

2. Select Zap workflows. Zapier opens the Zap editor in a new tab (Zapier: set up your Zap trigger).

3. Click the Trigger step. Search for Google Forms.

4. Set Trigger event to New Form Response.

5. Connect the Google account that owns the form.

6. In Configure, choose the Brightline Purchase Request form.

7. Click Test trigger and pull in a sample response. If you don't have one yet, submit a dummy request on the form first (for example, $49 stock photos).

Rename the Zap at the top to Purchase Request Approval — Brightline.

You can also start from a blank Zap via Create a Zap in the sidebar, which Zapier's quick start guide describes as the from-scratch path (Zapier Zap workflows quick start).

Step 7: Normalize the Amount (Formatter)

Form amounts sometimes arrive as text with a dollar sign or a comma. Paths need a clean number.

1. Click the + under the trigger to add an action.

2. Search for Formatter by Zapier.

3. Set Action event to Numbers.

4. Choose a transform such as Format Number (or Spreadsheet-Style Formula if you prefer) and map the form's Amount USD field.

5. Test the step and confirm you get a plain number like `1500` instead of `$1,500`.

Formatter steps are Zapier built-ins and do not count toward task usage on Zapier's pricing model (Zapier pricing — task usage).

Step 8: Create the Pending Log Row

Add a Google Sheets action before any branching so every request is recorded even if an approver never responds.

1. Click + → Google Sheets.

2. Action event: Create Spreadsheet Row.

3. Connect the same Google account.

4. Choose spreadsheet Brightline Purchase Requests, worksheet Log.

5. Map fields:

- Submitted At ← form timestamp

- Requester Name / Email / Manager Email / Item / Category / Vendor / Amount / Recurring / Needed By / Reason / Link / Urgency ← matching form answers

- Status ← type the literal text `Pending`

- Request ID ← you can map the form response ID, or combine timestamp + requester email with Formatter → Text → Default Value / Combine for a human-readable ID

6. Test the step. Confirm a new row appears in Log.

If this step ever fails (permissions, renamed sheet, wrong tab), you want to know immediately — we'll add an error handler on it in Step 12.

Step 9: Branch With Paths (Three Amount Tiers)

Paths let one Zap handle Tier A, B and C without three separate Zaps.

Important rule from Zapier's docs: once you add a Paths step, it must be the final step group in the Zap. You put all remaining actions inside the path branches. You cannot hang shared actions after every branch finishes — duplicate those actions in each branch, or use a Sub-Zap (Zapier Paths).

Add the Paths step

1. Click + after the Sheets row step.

2. Search for Paths and select it. Zapier creates Path A and Path B.

3. Click the + above the branches to add Path C (up to 10 branches per group) (Zapier Paths).

4. Rename the branches (menu icon → Rename):

- Path A → Tier A Auto ≤200

- Path B → Tier B Manager 201–2000

- Path C → Tier C Manager+Finance >2000

Set path rules

For each branch, open Path rules and choose Custom rules:

Tier A: Amount (Formatter output) (Number) Less than or equal to `200`
Tier B: Amount (Number) Greater than `200` AND Amount (Number) Less than or equal to `2000`
Tier C: Amount (Number) Greater than `2000`

Use AND logic inside Tier B so both conditions must match (Zapier Paths).

Click Continue on each branch so Zapier tells you whether the sample data would enter that path. Adjust until only one branch lights up for a given sample.

Paths and Filters do not consume tasks; only the action steps inside a running branch do (Zapier Paths).

Step 10: Build Tier A (Auto-Approve Path)

Inside Tier A Auto ≤200, add these actions in order:

10a. Update the Log row to Auto-approved

1. Google Sheets → Update Spreadsheet Row (or Lookup Spreadsheet Row then update, if you prefer to search by Request ID).

2. Set Status to `Auto-approved`.

3. Set Decided At to a timestamp (Formatter → Date/Time → Now, or map Zapier's run time).

4. Set Approver to `Policy auto-approve ≤200`.

5. Set Decision Notes to `Auto-approved by amount policy`.

10b. Notify Slack

1. Slack → Send Channel Message.

2. Choose #purchases (create the channel first if needed).

3. Message text example:

`✅ Auto-approved purchase request

Item: [Item]

Amount: $[Amount] USD

Requester: [Requester Name]

Vendor: [Vendor]

Reason: [Reason]`

Map the bracketed fields from the trigger or Sheets step.

10c. Email the requester

1. Gmail → Send Email.

2. To: Requester Email.

3. Subject: `Your purchase request was auto-approved: [Item]`

4. Body: short confirmation, amount, and a reminder to keep the receipt for finance.

Test each step with your $49 sample. Confirm the sheet, Slack and inbox all update.

Tier A is the "train on rails" path — no judgment, just policy. Keep AI out of it. Amount comparison is a rule, not a guessing game.

Step 11: Build Tier B (Manager Approval With Human in the Loop)

Inside Tier B Manager 201–2000:

11a. Request Approval

1. Click + → search Human in the Loop.

2. Action event: Request Approval.

3. Click Continue to open Configure (Zapier HITL).

Configure the approval content:

Approval request message: `Please approve or decline this Brightline purchase request.`
Content to review: add rows such as Item, Amount USD, Vendor, Category, Requester, Reason, Link, Urgency — name in the first column, map values in the second. Use + Add value set for each field.
Approve button label: `Approve purchase` (max 75 characters).
Decline button label: `Decline`.
Action if reviewer declines: choose Continue run so we can still update the sheet and email the requester. (If you choose Stop run, decline handling must live elsewhere.)
Let Reviewer edit content?: No for money fields (Brightline doesn't want approvers quietly changing the amount). Managers can still use Additional notes.

Notification section:

Send to: Slack (or Email if a manager lives in inbox).
For Slack: connect the workspace, set Message Type to User, pick the manager — or use Channel for a shared #approvals channel if two managers share the load.
Optionally click Send a preview when using Email so you see the notification yourself first (Zapier HITL).

Reviewer section:

Type of reviewer: Specific members of my account (Team plan).
Reviewers: select the manager's Zapier user. Only one person needs to complete a given review.
On timeout: End run (Brightline prefers a stuck request over a silent auto-approve on mid-size spend).
Timeout value / unit: e.g. `3` Days.
Send reminder: Yes, reminder after `1` Day.

Share the Zap with those reviewers — Zapier's docs require it (Zapier HITL).

Click Continue, then Test step. Testing does not email real reviewers; it creates sample output fields you can map. Use the preview feature if you want a real notification sample (Zapier HITL).

11b. Nested Paths for Approved vs Declined

After the HITL step, still inside Tier B, add a nested Paths step (Zapier allows up to three nesting levels) (Zapier Paths):

Approved branch: rule → HITL Decision (Text) Exactly matches `approved` (Zapier documents that an approval sets `Decision` to `approved`) (Zapier HITL).
Declined branch: Fallback, or Decision does not match `approved`.

Approved branch actions:

1. Google Sheets → update Status `Approved`, map Reviewer Note into Decision Notes, set Decided At and Approver.

2. Slack → `#purchases` success message.

3. Gmail → requester confirmation.

Declined branch actions:

1. Google Sheets → Status `Declined`, map Reviewer Note.

2. Slack → `#purchases` decline notice (so finance isn't waiting on a phantom order).

3. Gmail → requester email that includes the reviewer note and a link to submit a revised request.

This is the human checkpoint. The Zap is the clipboard. The manager is still the decision-maker.

Step 12: Build Tier C (Manager, Then Finance)

Tier C copies Tier B, then adds a second Human in the Loop step for finance after the manager approves.

Inside Tier C Manager+Finance >2000:

1. HITL Request Approval → reviewers = managers (same content as Tier B). Action if declined: Continue run. Timeout: 3 days with a 1-day reminder.

2. Nested Paths on manager Decision:

- Manager declined: update sheet, Slack, email requester. Stop there.

- Manager approved: continue to finance HITL.

3. On the manager-approved branch, add a second Human in the Loop → Request Approval:

- Content to review: same fields plus `Manager note` mapped from the first HITL Reviewer Note.

- Reviewers: finance lead's Zapier user.

- Timeout: 5 days (contracts take longer). Reminder at 2 days.

4. Nested Paths again on finance Decision → Approved / Declined updates, Slack, Gmail.

Two pauses feel slow the first week. They are still faster than a purchase that was never logged. For Brightline, anything over $2,000 is a budget conversation, not a rubber stamp.

Step 13: Error Handling and Alerts

A purchase Zap that fails quietly is worse than no Zap. The requester thinks they're waiting on their manager. The manager never saw a request. Finance discovers it at month-end.

Brightline uses three layers.

Layer 1: Autoreplay for temporary blips

On Professional plans and higher, Zapier can autoreplay errored steps — up to five attempts — and holds error-notification emails until the final attempt fails (Zapier: what is replay) (Zapier: replay Zap runs).

To enable autoreplay for this Zap:

1. Open the Zap in the editor.

2. In the left sidebar, open advanced settings.

3. Set Autoreplay override? to Always replay (or Use account setting if autoreplay is already on for the account) (Zapier: replay Zap runs).

Account-wide autoreplay (owner/super admin): Zap History → Zap Runs tab → toggle Autoreplay on (Zapier: replay Zap runs).

Layer 2: Custom error handler on the Sheets create step

Custom error handlers are available on Team and Enterprise. They run an alternative path when a step errors and mark the run Stopped/Handled. Publishing a Zap with an error handler turns off autoreplay for that Zap (Zapier custom error handling).

Brightline puts an error handler on Create Spreadsheet Row (the step that must never fail silently):

1. On that step, click the three dots icon.

2. Select Add error handler.

3. Zapier splits into Success (left) and Error (right) (Zapier custom error handling).

4. On the Error path, add:

- Slack → Send Channel Message to #ops-alerts with the mapped Error Message field from the failed step.

- Gmail → Send Email to the ops lead: subject `Purchase Zap failed to log a request`.

Because error handlers disable autoreplay on that Zap, Brightline accepts that trade: they'd rather get a loud alert on log failures than a quiet five-retry loop. Temporary Slack hiccups inside a path can still be retried manually from Zap History.

Layer 3: Per-Zap error notification cadence

On Pro, Team and Company-style plans, you can set whether a Zap emails errors immediately, as an hourly summary, or never (Zapier: customize action error notifications). Set this Zap to immediate. A delayed purchase approval is not a "check it tomorrow" problem.

Optional: Zapier Manager watchdog

You can build a second Zap that triggers when this Zap errors (Zapier Manager) and pages whoever is on duty. Even with custom error handling enabled, Manager-based error triggers can still fire (Zapier custom error handling). Useful if #ops-alerts and email both somehow miss.

Step 14: Test With Sample Data (Don't Skip This)

Publish only after a written test plan passes. Brightline's checklist:

Sample set

Prepare five form submissions:

1. $49 stock photos — must take Tier A, Status Auto-approved, Slack + email.

2. $200 exact boundary — must take Tier A (≤200).

3. $201 exact boundary — must take Tier B, pause for manager.

4. $1,500 freelance copywriter — Tier B, manager declines with a note; requester gets the note.

5. $2,500 annual SEO tool — Tier C, manager approves, finance approves; sheet shows both notes in Decision Notes (append finance note after manager note).

How to test without annoying the company

Create a #purchases-test Slack channel and temporarily point Slack steps there.
Use your own email as requester for the first pass.
For HITL, Zapier's step test does not notify real reviewers — do one end-to-end live test per tier after the dry mapping tests (Zapier HITL).
After each run, open Zap History, click the run, and confirm which path branch executed.

Pass/fail rules

A test fails if:

Two path branches both fire for one amount (fix exclusive rules).
Status stays `Pending` after an approval.
Decline stops the Zap before the requester is emailed (if you chose Stop run by mistake).
The Log row is missing entirely.

Only when all five samples pass do you switch Slack back to #purchases and tell the team the form is live.

Step 15: Document and Hand Off

Automations without documentation become "Maya's Zap." When Maya is on holiday, the process dies.

Brightline's one-page handoff lives in the company wiki and in a Zapier note on the Zap itself (editor Notes panel).

Include:

1. Purpose: purchase requests from form to logged decision.

2. Owner: ops lead name + backup.

3. Tier rules: the $200 / $2,000 thresholds and who reviews.

4. Apps connected: which Google account, which Slack workspace, which Zapier Team users must remain shared on the Zap.

5. How to approve: reviewers get a Slack/email link → log into Zapier → Approve or Decline → optional note.

6. How to pause: turn the Zap off from Zapier; pin a Slack message that requests go to a manual spreadsheet until further notice.

7. How to change tiers: edit Path rules, retest samples 2–5, update the form description and this doc on the same day.

8. Where logs live: link to the Google Sheet Log tab and Zap History.

Screenshot the Zap outline (Zapier can export a PNG of a Zap from the editor menu on supported plans) and drop it under the wiki page (Zapier editor controls).

Handoff is like leaving baking instructions on the fridge. Ingredients (apps), temperature (tiers), and what "done" looks like (Statuses).

Step 16: Monitor for the First 30 Days

Week 1 checklist (15 minutes/day):

Open Zap History. Any Stopped/Errored or Stopped/Handled runs?
Spot-check five Log rows against Slack messages.
Ask one requester and one manager: "Did this feel clearer than Slack DMs?"

Week 2–4:

Count requests by tier. If 80% are Tier A, your $200 threshold may be too high or too low — adjust with data, not vibes.
Watch timeout rates. If managers miss the 3-day window often, shorten the reminder or change On timeout behavior with eyes open.
Review Decision Notes on declines. Repeated declines for the same vendor usually mean a policy conversation, not a Zap bug.

Monthly:

Export or filter the Log for finance. This sheet should replace the month-end receipt scavenger hunt for requests; receipts for the actual purchases still matter for bookkeeping (pair with your accounting process, and see our notes on data entry if receipts are the bottleneck: how to automate data entry with AI).

What It Costs (Prices Checked Live)

All figures below were read on 13 October 2026 (EAT) from the vendors' official US pages. Amounts are USD. Full source notes live in the companion price audit.

Zapier

On Zapier's pricing page with Pay yearly (Save 33%) selected (Zapier pricing):

Free: $0 / month, 100 tasks per month, two-step Zaps.
Professional: starting from $19.99 / month (yearly billing).
Team: starting from $69 / month (yearly billing), includes 25 users.

Zapier's published task-tier table (annual vs monthly) lists Professional at $19.99 / month billed yearly for the 750-task tier ($29.99 billed monthly), and Team at $69 / month billed yearly for the 2,000-task tier ($103.50 billed monthly) (Zapier pricing). Higher task tiers cost more. Enterprise is sales-quoted.

Brightline needs Team because Human in the Loop must reach managers and finance, not only the Zap owner (Zapier HITL).

Slack

From Slack's pricing page (Slack pricing):

Free: $0 USD, free forever.
Pro: $7.25 per user per month when paying annually; $8.75 per user per month when paying monthly.
Business+: $15 per user per month annually; $18 per user per month monthly.

Brightline can run HITL Slack notifications on Free if they stay within Free's limits (including the 10 apps cap on Free) (Slack pricing). Upgrade only if they need longer message history or more apps.

Promotional prices ($4.38 and $9) appeared on Slack's page during our check; we do not quote them here because promotion terms change. Use the standard annual/monthly figures above.

Google Forms and Sheets

Creating forms and spreadsheets does not carry a separate Google price on the Forms help pages; they work with a Google account (Google Forms help). If Brightline already pays for Google Workspace, that bill doesn't increase because of this Zap. We are not attaching Workspace list prices to this build's required cost.

Worked example (labeled illustration)

Assume 40 requests/month:

Rough tasks per Tier B request: create row + HITL approval + update row + Slack + Gmail ≈ 5 successful action tasks (Paths/Formatter don't count; Forms/Tables free-task rules don't apply to Google Forms/Sheets the same way — Google Forms trigger is free as a trigger; Sheets and Gmail and Slack and HITL actions count when they succeed) (Zapier pricing) (Zapier HITL).
40 × 5 = 200 tasks/month, well inside Team's entry 2,000-task tier.

Monthly software cost (Brightline illustration):

Zapier Team, 2,000 tasks, billed yearly: $69 / month
Slack Free: $0
Google Forms/Sheets: $0 incremental

Total: $69 / month (billed yearly to Zapier), or $69 × 12 = $828 / year.

Against the made-up $4,200 / year coordination cost from Step 1, the subscription is smaller than the time waste — but your hours and wages will differ. Re-run the math with your numbers. For a staged view of what to automate first across a whole business, see our small business automation roadmap.

What to Do Next

Once purchase requests run cleanly for a month, Brightline's natural sequels are:

1. Vendor onboarding — when Status becomes Approved for Category = Freelance, create a folder and a kickoff checklist (still no code).

2. Ads top-up variant — prefill Category = Ads and route Tier B to the media lead instead of the default manager (duplicate the Zap or add a Path rule on Category).

3. Accounting sync — on Approved, create a draft bill in QuickBooks or Xero. Keep a human before money moves. Invoice intake is a different process; don't collapse them.

4. Browser extension or pinned Slack shortcut — reduce friction so people stop bypassing the form.

For a wider menu of single tasks (not this full process), see 15 tasks you can automate today. Resist the urge to rebuild the Zap with AI decision-making on day one. Amount thresholds are rules. Rules belong on rails. Save judgment-heavy AI steps for later workflows, and read our explainer on how AI workflow automation works before you add them.

Common Mistakes (and How Brightline Avoids Them)

Building before mapping. A Zap that mirrors a broken process is a faster broken process. Map first.

Free-text status fields. If humans type "approved" into Sheets while Paths look for `approved` from HITL, you get chaos. Let the Zap write Status.

Using Professional when two people must approve. Pro HITL only sends requests to yourself (Zapier HITL). Budget for Team if reviews leave your hands.

Putting Paths in the middle, then adding "shared" steps after. Zapier moves later steps into Path A. Duplicate end notifications inside each branch (Zapier Paths).

No decline path. Stopping the Zap on decline without an email leaves requesters in the dark. Prefer Continue run and handle declines explicitly.

Skipping the record. If it isn't in the Log, it didn't happen.

Changing Path rules without retesting boundaries. Always retest $200 and $201 after an edit.

Rollout: How Brightline Turns the Zap On Without Chaos

A finished Zap is not a finished change. People bypass forms when the old Slack habit is easier.

Brightline's rollout plan:

Day 0 (soft launch)

Ops lead and one manager run the five sample tests again on production channels.
Pin the form link in #purchases with the policy one-liner.
Announce in #general: "From Monday, purchase requests only count if they're in the form. Slack approvals aren't official."

Week 1 (parallel run)

Keep the Zap on.
Ops still glances at Slack for people who forget, and replies with the form link only — no more typing "ok buy it."
Track bypass attempts. If the same person bypasses twice, their manager gets a private note.

Week 2 (hard cutover)

Managers agree to ignore approval DMs that aren't from the Zap.
Finance refuses to reimburse or issue a card for anything Approved-missing in the Log after the cutover date (with a short grace list for emergencies).

Change management in plain words

You're not installing software. You're changing the front door. Like a shop that used to take orders by phone and now uses a counter ticket queue: the kitchen only cooks what has a ticket. Slack DMs become the phone calls you politely redirect.

Deep Dive: Updating the Right Spreadsheet Row

Beginners often use Create Spreadsheet Row for every status change and end up with duplicate rows. Brightline creates once (Pending), then updates.

Reliable pattern inside each path branch:

1. When you created the Pending row, have Zapier store the row number if the Create step returns it, or give every request a unique Request ID (form response ID works).

2. Before updating, add Google Sheets → Lookup Spreadsheet Row with the Request ID in the lookup column.

3. Then Update Spreadsheet Row using the row found by the lookup.

If lookup finds nothing, that's an error condition — your error handler or a Fallback path should alert ops rather than creating a second half-empty row.

This is the same "one row per record" discipline as the Sheets guide, applied to approvals (Google Sheets workflows).

Deep Dive: Sharing the Zap and App Connections

Human in the Loop reviewers must access the Zap. On Team:

1. Move the Zap into a shared folder.

2. Share the folder with manager and finance Zapier seats.

3. Prefer shared app connections for Google Sheets, Gmail and Slack so the Zap doesn't depend on one employee' s personal OAuth login when they leave (Zapier pricing — Team features).

If the Sheets connection is still "Maya's Google account" and Maya departs, the Zap breaks on a Monday morning. Shared connections are the spare key to the office.

Security and Access Notes (Without Waiting for the Safety Article)

Connecting apps always carries risk. A fuller treatment of connection safety is scheduled separately on this site; for this build, Brightline follows minimum hygiene:

Only ops owns publish rights on the Zap.
Reviewers can approve; they can't edit Path rules unless they're in the ops group.
The form doesn't ask for credit-card numbers or passwords — ever.
File uploads on the form stay off for v1 (quotes are links, not attachments), which also avoids large-attachment failure modes.
Decline and approve notes are business records; don't put unrelated personal data in Reviewer Note.

Measuring Whether the Automation Worked

After 30 days, Brightline reviews four numbers (all from the Log and Zap History — no vanity dashboards required):

1. Requests submitted via the form (should roughly match former Slack volume).

2. Bypass rate — purchases that hit finance without a Log row (target: near zero after week 2).

3. Median time to decision for Tier B and Tier C (Submitted At → Decided At).

4. Error runs per week in Zap History.

If median Tier B decision time is still three days because managers ignore Slack, the Zap is fine and the management habit isn't. Fix the habit with reminder timing and a weekly Pending filter view in Sheets — not with more tools.

Optional Hardening After Month One

Only after the basics are trusted:

Add a Digest by Zapier daily summary of Pending rows to the ops lead (built-in; task rules follow Zapier's digest behavior on your plan).
Add a Path rule: if Urgency is `Urgent` and Amount ≤ 2000, also @channel in Slack (still no auto-approve beyond policy).
Duplicate the Zap for a Vendor creation sequel when Category is Freelance and Status becomes Approved.
Replace Gmail confirmation with a branded email template — cosmetic, not structural.

Do not add AI "approve if this looks reasonable" steps until you have months of clean Decision Notes to learn from. Garbage policy in, confident garbage out.

Frequently Asked Questions About Automating Business Processes Without Coding

Can you really automate a full business process without coding?

Yes — for processes that follow clear rules and live in connected apps. A purchase-request flow with amount tiers, approvals and notifications is a strong fit for no-code tools like Zapier, Make or Power Automate. Processes that need heavy custom software, offline paper, or constantly changing judgment are poorer first targets. Our beginner's guide covers when not to automate.

What is the best first business process to automate without coding?

Pick something frequent, rule-based and painful when it goes wrong — purchase approvals, lead routing or form-to-sheet handoffs are common. Avoid your most political process first. Brightline started with purchases because the tiers were easy to write down. For prioritization across a whole company, use the automation roadmap.

How do you automate approval workflows in Zapier?

Use Human in the Loop → Request Approval to pause a Zap until a reviewer approves or declines, then branch with Paths on the `Decision` field (`approved` when they approve) (Zapier HITL) (Zapier Paths). Share the Zap with reviewers. On Professional, you can only request approval from yourself; Team or Enterprise is needed for other reviewers (Zapier HITL).

What is the difference between Paths and Filter in Zapier?

Filter stops the Zap when conditions aren't met. Paths route one Zap into different action branches for different cases (Zapier Paths). Use Paths when you need an "if this, do X; if that, do Y" process like amount tiers.

Do I need Slack to automate purchase approvals?

No. Human in the Loop can notify by Email, Slack, or Trigger a Zap (so you can push the request into almost any app) (Zapier HITL). Slack helps when your team already lives there.

How much does it cost to automate a process like this?

Software cost depends on plan. As of our 13 Oct 2026 check: Zapier Team starts at $69/month with yearly billing selected; Slack Free is $0; Google Forms/Sheets add $0 incremental for many teams (Zapier pricing) (Slack pricing). Your task volume and seat counts change the total. Re-check the vendor pages before you buy.

Is a purchase-request Zap the same as expense automation?

No. A purchase request asks for permission before spending. An expense report explains spending after the fact (receipts, policy checks). We build the first here. Short expense blueprints appear in our 20 workflow examples; don't merge the two processes into one confused Zap.

Can AI decide whether to approve a purchase?

Technically you can add an AI step, but Brightline shouldn't on day one. Amount thresholds are business policy, not language interpretation. Keep AI for messy text later; keep money rails deterministic. For how AI fits into workflows generally, see AI workflow automation explained.

What happens if an approver ignores the request?

You configure On timeout and optional reminders on the Human in the Loop step — for example end the run after 3 days, or skip and continue (Zapier HITL). Brightline ends the run on timeout for mid and large tiers so nothing auto-approves by neglect, then ops follows up from the Pending rows in the Log.

How do I test without spamming my team?

Use a test Slack channel, your own email, Zapier's step tests for field mapping, and one scheduled live end-to-end test per tier before launch (Zapier HITL).

Can I build this in Make or n8n instead?

Yes. The process design (trigger, tiers, approvals, log, alerts) transfers. The menu clicks differ. We used Zapier because Paths + Human in the Loop match this approval pattern closely and are documented for non-developers. Compare platforms in our tools guide.

How is this different from the beginner's "build your first automation" guide?

That guide teaches first principles with a small starter Zap. This article assumes those basics and walks one full business process — mapping, policy tiers, dual approvals, error handling, testing, handoff, monitoring and cost — without reteaching what a trigger is.