DA9: Running automation for a business
Maintaining workflows over time
🎯You'll be able to
Keep workflows healthy over time with reviews, version notes, dependency checks and safe updates.
🏠The everyday picture
A two-wheeler needs servicing: oil, brakes, tyres. Ignore it and it works until the day it doesn't, usually at the worst moment. Automations need servicing too.
📘What it really is
- Workflows break over time even if nobody touches them:
- apps change APIs or retire versions (DA7);
- tokens expire and staff leave (DA6);
- the business changes: new products, prices, stages;
-
volume grows past plan limits (DA3).
-
A maintenance routine:
- weekly: read the run log summary and open alerts;
- monthly: check plan usage and costs, token expiry dates, and failed-run patterns;
-
quarterly: review each workflow with the owner: still needed? still right? any new manual work around it?
-
Keep a workflow catalogue: name, purpose, owner, systems, last reviewed, status (active, paused, retired).
- Retire workflows nobody needs, so they don't keep running, costing money and holding data.
- Watch provider announcements for API changes and deprecations.
📝A worked example
Sharma Textiles' quarterly review found:
| Workflow | Finding | Action |
|---|---|---|
| Order → CRM | Fine; volume up 80% | Check plan limit before Diwali |
| Weekly CRM tidy-up | Fine | None |
| Old Google Form → sheet | Form no longer used | Retire; delete stored data per data map |
| WhatsApp reminders | Token expires in 3 weeks | Renew now; add a calendar reminder |
| Inbox router | Staff manually re-route "bulk" emails | Add "bulk" keyword to the table |
The review took an hour and prevented a token expiry in the middle of the festive season.
🌍Where it's used
- Retainer work with clients.
- In-house automation teams looking after dozens of workflows.
- Before busy seasons such as Diwali, weddings and year-end.
📝Case scenario
In the first week of the wedding season, the order workflow stops: the n8n plan's monthly execution limit was reached because order volume tripled. You move to a higher plan that day, and add a monthly usage check to the maintenance routine with an alert at 70% of the limit.
🖱️Try it
Create a workflow catalogue for everything you've built in this path. For each workflow, add an owner, a last-reviewed date and one thing to check at the next review.
⚠️Common mistakes
- No owner after launch. Sign: a broken workflow is found weeks later. Fix: name an owner and a review date in the catalogue.
- Updating n8n or an API version without testing. Sign: everything fails after an upgrade. Fix: run your acceptance tests on a copy first.
🛠️For your project
Your acceptance tests are also your maintenance tests: rerunning tests/payment.js after any change is how you know nothing broke.
✅Quick check
Name two ways a workflow can break even if nobody edits it.
Show the answer
An app changes its API, or a token expires. Volume growth past a plan limit is another.
Why retire unused workflows?
Show the answer
They keep costing money, can fail confusingly and keep holding personal data.