When you automate processes for one client, everything is straightforward: one workflow, one database, one dashboard. When you have five, ten, or more clients with active automations — WhatsApp reminders, inactive client reactivation, weekly summaries — management gets complicated fast.
This article documents how we solved that problem for ourselves. A single admin panel that shows the status of every client, every automation, and every metric in one place. Infrastructure cost: under €5 a month.
The problem: many clients, many automations, no overview
Each client we onboard has their own set of automations. A personal trainer with session reminders. A dental clinic with post-treatment follow-ups. An ecommerce store with abandoned cart recovery. Each with its own logic, data, and messages.
Without a centralised panel, the daily routine looked like this:
- Checking each system separately: opening n8n, finding the client’s workflow, checking for errors, reading the logs. Multiplied by every client
- Scattered metrics: messages sent were in one table, sessions in another, orders in another. Impossible to tell at a glance whether everything was working
- Late detection of failures: if a workflow stopped working at 3am, you wouldn’t know until the client called asking why their customers hadn’t received a reminder
- Time wasted on repetitive checks: every Monday, manually reviewing the status of each automation before starting the week
The problem wasn’t technical. The systems worked. The problem was visibility: there was no single place to see everything together.
The solution: a centralised admin dashboard
We built a web panel accessible from any device that consolidates information from all clients into a single interface. It’s not a generic product — it’s designed specifically for monitoring automations in production.
Overview: every client at a glance
The main screen shows a card for each active client with:
- Name and business type (trainer, clinic, ecommerce…)
- System status: active, paused, or errored
- Key metrics from the past week: messages sent, actions completed, incidents
- Last activity: when the last successful execution of each automation ran
If everything is green, there’s nothing to do. If something is orange or red, you know exactly where to look.
Per-client metrics
Opening a client’s card shows the detail:
- Messages sent: reminders, follow-ups, reactivations — broken down by type and channel (WhatsApp, Telegram, email)
- Response rate: what percentage of messages triggered an action from the recipient
- Active automations: list of running workflows with their frequency and last result
- Incident history: errors, retries, and resolutions, with timestamps
This isn’t about generating pretty reports. It’s about knowing in 10 seconds whether a client’s system is working as it should.
Message tracking
Every message the system sends — whether a session reminder, a reactivation message, or a weekly summary — is logged with:
- Recipient, channel, and send time
- Message content (or summary if AI-generated)
- Delivery status
- Recipient’s response, if any
This solves a common problem: when a client says “my patient didn’t get the reminder”, you can verify in seconds whether the message went out, when, and through which channel.
System health
The monitoring section shows:
- Workflow status: which are active, which are paused, which failed on their last execution
- Resource usage: database, storage, workflow executions consumed
- Automatic alerts: if a critical workflow fails, an immediate Telegram notification arrives with the client name, affected workflow, and the error
It doesn’t replace infrastructure-level monitoring. It complements what already exists with business-specific information.
How something like this gets built
The foundation: structured data from client one
The key to making a panel like this work is that all clients share a coherent data structure. From the very first project we designed database tables with a schema that supports cross-client queries:
- Client table with unique identifier, business type, and status
- Sent messages table referencing the client, type, channel, and result
- Workflow execution table with result and timestamp
When we onboard a new client, their data fits the same schema. No panel adaptation needed.
The panel: static HTML served via webhook
The dashboard is an HTML page served directly from n8n via a webhook. No frontend framework, no build process, no dependencies. Vanilla HTML, CSS, and JavaScript calling API endpoints for data.
This has concrete advantages:
- Instant deployment: any change to the panel takes effect immediately
- Zero frontend maintenance: no packages to update, no builds to break
- Performance: a static page with API calls is as fast as it gets
Security: controlled access without complexity
The panel is protected by a URL token. Only someone with the link can access it. For an internal admin panel, this is sufficient and avoids maintaining an authentication system with users, sessions, and password recovery.
The API endpoints that feed the panel validate every request and sanitise all inputs before touching the database.
Cost and maintenance
| Item | Detail |
|---|---|
| Infrastructure | < €5/month (VPS shared with other services) |
| Licences | €0 (fully open source) |
| Initial development time | ~1 day |
| Monthly maintenance | Virtually zero (the panel reads data that’s already being generated) |
The marginal cost of adding a new client to the panel is zero. The data already exists in the database; the panel just queries it.
What changes in day-to-day operations
Before the panel, Monday started by reviewing workflows one by one. Now it starts by opening a page and seeing everything green — or knowing exactly what needs attention.
The concrete benefits:
- Problem detection in minutes, not hours: automatic alerts notify before the client notices
- More productive client meetings: the data is there, no preparation needed
- Real scalability: going from 3 clients to 10 doesn’t multiply management time
- Client confidence: being able to demonstrate with data that their automations work builds a stronger relationship
Does this make sense for your case?
If you manage automations for multiple clients — or if within your company you have several departments with automated processes — a centralised panel like this eliminates a surprising amount of operational friction.
It doesn’t need to be exactly like ours. The idea is the same: one place to see everything together, without relying on memory or checking systems one by one.
Related articles
- Custom session management dashboard for personal trainers — A concrete example of a bespoke panel for a trainer: the kind of project we then monitor from this centralised dashboard.
- Self-Hosted Automation vs Zapier in 2026: real costs — Why we chose a self-hosted stack to build these panels instead of relying on platforms like Zapier.
Tell us what you’re managing today and we’ll assess together whether it makes sense to consolidate it into a dashboard.