What’s worth automating — and what to leave manual

1. Lean the process first

Map trigger → inputs → outputs → owner. Cut waste before you encode it. NIST MEP’s Automation 101 says map the work and cut waste first: automation can amplify a bad process.

• Pass. The path is already lean. You would not be automating extra steps or a second copy of the row.
• Defer. You would encode a workaround, a duplicate tracker, or a step nobody can name.
• Example. Pass: a form already writes the fields finance needs, then a person files the PDF. Defer: the same request is typed into email, a Sheet, and a Notion page.

Source: NIST MEP — Automation 101 · accessed 2026-09-17 · if the hub is messy, name one hub and stop.

2. Frequency and volume math

How often does it run — weekly, daily, hourly? Estimate steps × runs. Zapier’s plan guide asks you to list the processes and how often they run; a task is a successful action, so tasks ≈ actions × volume. Triggers do not count. Compare that estimate in each vendor’s own unit — do not treat one task as one credit as one execution.

• Pass. You can estimate volume in the vendor’s unit and say why the job repeats.
• Defer. You cannot count runs, or you are guessing a monthly bill from a /500 score.
• Example. Pass: “about 20 paid-invoice writes a week, three actions after the trigger.” Defer: “this should save a lot of time” with no run count.

Source: Zapier — how to select your Zapier plan · accessed 2026-09-17 · Tasks vs credits vs executions · Same job, three meters

3. Rules you can write down

If two people still do the job differently, write the rule first. An automation will pick one version and run it at volume.

• Pass. The happy path and the exception path are written. Two people would follow the same rule.
• Defer. People still disagree on the edge cases, or nobody can state what success looks like.
• Example. Pass: “if status is Paid, copy the invoice id; if status is Void, skip.” Defer: “qualify this inbound lead” when two people still use different rules.

4. Cost of a quiet miss

Ask what happens if nobody notices a skip, a duplicate, or a bad write. For sensitive or high-consequence work, keep a person on the review step. Zapier’s AI Guardrails help page recommends a person review for sensitive workflows and says the product is not a standalone compliance tool.

• Pass. A miss is visible, or a person reviews the sensitive step.
• Defer. A silent failure is too costly — refund, contract, payroll, or a write nobody will check.
• Example. Pass: Slack the owner when the write fails; the empty hub row is also visible. Defer: a refund or contract change with no review step.

Source: Zapier — how to get started with AI Guardrails · accessed 2026-09-17 · after go-live, catch jobs that look fine.

5. One scoped job

Prefer a single critical job, or 3–5 related actions — not one flow that updates everything. Zapier’s Agents best practices: keep a limited scope, then test with real data and edge cases. On Make, split large work into subscenarios and apply Grid filters early so you process less data.

• Pass. The first job is one owned outcome.
• Defer. You are automating the whole shop in one run, or “keep the CRM in sync” across three trackers.
• Example. Pass: paid invoice → one hub row → notify finance. Defer: one scenario that updates CRM, billing, Slack, and a personal Sheet.

Source: Zapier — best practices for working with Zapier Agents · accessed 2026-09-17

6. Failure path before go-live

Decide who is alerted, and what happens when a connection dies. In Make, a run of consecutive errors can disable scheduling; AccountValidationError means the connection needs a fix and cannot be swallowed by an error handler. In n8n, set an Error Trigger workflow in the job’s settings so a failure can page someone. Name the class first — auth, bad data, rate limit, timeout, quota, handled versus unhandled, or expected non-match.

• Pass. Alerts and a dead-connection path exist. Someone would notice.
• Defer. Nobody would notice. The job can look on while the write never happens.
• Example. Pass: Error Trigger or consecutive-error disable pages the named owner. Defer: “we will check history if someone complains.”

Sources: Make — fix errors and warnings · n8n — handle errors gracefully · accessed 2026-09-17 · When automations fail — name the class first · When automations look fine

7. Owner and rollback

Name the person who gets the alerts. Operator, builder, or engineering is a different job — see Who should own your automations. Before you switch tools, keep the source job on, rebuild one critical job on the destination, compare outcomes, then cut over.

• Pass. An owner and a rollback path exist.
• Defer. The job is orphaned, or the only connection is under a contractor’s email.
• Example. Pass: named owner, documented reconnect, and a parallel-run before cutover. Defer: “whoever built it” left last quarter.

Parallel-run one job before you switch · What does not migrate

8. Then pick the tool

Only after the job passes the list above. Open Which automation tool for small teams — that page has the four-question flowchart. This page does not reprint it. Compare units on Tasks vs credits vs executions and Same job, three meters. If the hub is Notion, see when to hand off to Make. When-to-pick copy lives on Make vs n8n vs Zapier — when to pick each.

This page does not rank tools and adds no score cells.