For automation agencies and freelancers on support retainers: watch every client's n8n workflows, get alerted on failed runs and on schedules that stopped firing, and give each client a status page or monthly report.
I need thisService in preparation · No payment is accepted on this page
Agency with 8 clients and 3 n8n instances. Tuesday 06:00: the CRM sync of one client did not run — alert in Slack within minutes. Fixed by 07:30. The client's status page shows the incident as resolved, and it appears in the monthly report.
Choose your planAn agency that builds automations in n8n usually keeps maintaining them after launch, on a monthly retainer. The hard part of that retainer is not fixing a broken workflow, but knowing that it broke. The built-in error workflow fires when a run fails; a schedule that simply stops firing produces no error at all, and the client may notice the missing data before the agency does.
FlowWatch connects to your n8n instances and watches the workflows you mark as important. For each workflow you set who the client is and what normal looks like: a run every hour, every morning at six, or on every new order. When a run fails, you get an alert. When a run that should have happened did not, you get an alert too.
Alerts arrive where you work — email, Slack or a phone notification — and are grouped by client, so it is clear whose automation needs attention. You can set quiet hours and decide which workflows wake someone up at night and which can wait until morning.
Each client can have a status page: a simple list of their automations with the latest run and its result. It shows the client that the work they pay for is running, without giving them access to your n8n instance.
At the end of the month FlowWatch prepares a report for each client: how many runs, which failed, which were missed, and when each issue was resolved. You can add a note about what you changed. The report helps the conversation about the retainer — it shows the maintenance that otherwise stays invisible.
Several instances and many clients are handled in one account: self-hosted n8n and n8n cloud alike. The agency sees all clients on one screen; each client sees only their own page.
FlowWatch is built for small agencies and freelancers with a handful of clients to a few dozen. Pricing depends on the number of n8n instances you connect.
Setup takes a few minutes per instance. You connect it with an API key, choose the workflows that matter for each client and confirm how often each one is expected to run; FlowWatch suggests the expected schedule from past runs. You can mute a workflow during planned maintenance, so a client's status page does not show an incident while you deliberately stop their automations for an update, and you can pause monitoring for a client whose retainer has ended.
FlowWatch is an independent tool and is not affiliated with n8n. It reads run information from your instances; it does not change your workflows.
A scheduled or expected run that did not happen. It produces no error, so it needs separate monitoring.
Yes, each client can have a page showing only their automations.
Yes, self-hosted and cloud instances can be connected.
No. It reads run information; your workflows stay as they are.
Not yet. The service is in preparation, and we are checking whether agencies need it.