x
Deleting an automation is not the same as ending one, and the order matters. Pause it rather than deleting it, wait a week and see what breaks. Then revoke its access everywhere — not just in the tool you built it in — export anything you'd miss, cancel whatever it was quietly paying for, and write one line recording what it did and why it stopped. Ten minutes now, or an afternoon of archaeology in six months when something you forgot about surfaces in the wrong place.
Deleting is the fast version and it leaves debris: orphaned permissions, a subscription still billing, and no record that the thing ever existed.
Because you're about to find out whether it was load-bearing, and you'd rather find out reversibly.
Set it to paused and leave it a full week. Two outcomes, both useful:
Nothing breaks. That's your green light. Delete with confidence — and note that the silence also tells you the automation was producing less value than it felt like, which is worth knowing before you build the next one.
Something breaks. Excellent, and much better discovered now. Something downstream depended on it — a report that stopped arriving, a folder that stopped filling, a client who noticed. That dependency was invisible while the thing ran. You've just learned the automation was doing real work, which moves it out of Kill and into Finish, or tells you what to replace it with.
A week is the right window because most business rhythms are weekly. Anything monthly — invoicing, reporting, reconciliation — needs a month, so pause those with a diary note rather than a guess.
It means the tool you built in is usually not the only place the permission lives, and deleting the automation doesn't withdraw the grant.
Work through four places:
The automation platform itself. Delete the scenario, flow or zap — but that's the last step, not the first.
The connected-apps list on each service it touched. Your email, cloud storage, calendar, CRM and accounting tools each keep their own list of what has been granted access. Removing the automation does not remove its entry there. This is the step almost everyone skips, and it's the one that leaves a live credential pointing at your files.
API keys and tokens. If you generated a key for this, revoke it at the source. A key that still works is a door that's still unlocked, whether or not anything is currently walking through it.
Anything it could post or send as. Social accounts, shared inboxes, channels. Check that the app is gone from the account's authorised list, not just that the workflow is off.
This is the difference between an automation being stopped and being ended. A stopped one with live credentials is exactly the unowned process that this week's hub is about — and it got there by neglect rather than decision, which is worse.
Two things, and they're small.
Whatever you'd miss. Export the outputs before you delete the thing that produced them — the logs, the drafts, the collected data. Deleting a workflow often takes its history with it, and history is usually the only part with residual value.
One line about why it stopped. "Invoice chaser, built Mar 2026, retired Aug — client base changed, no longer relevant. Access revoked in Gmail + Drive." Thirty seconds to write. It is the entire handover, and future you will ask for it — probably at the worst possible moment, when you're wondering whether to rebuild the same thing.
That line is also what makes killing feel like a decision rather than a loss, which matters more than it sounds. A written retirement is a record of judgement. A deleted folder is just a gap.
Cancel the money. Last check: was anything paying for this? A tier you upgraded to for one workflow, a per-run charge, an add-on. That cost survives the deletion unless you go and stop it.
Related Decodes
For the weekend plan that finishes one of them — free, vetted, 5-min read: The Weekend Automation Plan.
AI the Brief (@aithebrief) — AI advice you can act on and trust, for time-starved founders.
TL;DR: Ending an automation is a five-step job, not a delete. First pause rather than delete and wait a week: if nothing breaks that's the green light, and if something breaks you've discovered an invisible dependency reversibly — use a month for anything on a monthly rhythm. Second, revoke access in four places, because the automation platform is usually not where the permission lives: the connected-apps list on every service it touched, any API keys at source, and the authorised-app list on anything it could post or send as. Third, export whatever you'd miss, since deleting a workflow often takes its history with it. Fourth, write one line recording what it did and why it stopped — the entire handover, and what turns killing into a recorded judgement rather than a gap. Fifth, cancel any subscription or tier the automation alone justified, because that cost survives deletion.
