How do I show clients what my n8n automations did?
Last updated · Written by the Bot Office team; it names Bot Office where it fits and says where it does not.
The short answer
Pull the run history from n8n (its executions are in the n8n public API), turn each run into one plain line a client understands (what ran, whether it worked, what it saved), and share that on a page or in a regular report. Do not give clients your n8n editor: it shows nodes and errors, not outcomes, and it exposes every credential-bearing workflow.
Agencies usually add three things on top: a client-branded view, a weekly or monthly summary, and a clear note of anything that failed or waited for a person.
Steps (with any tool)
- Decide what a client should see. Pick the outcomes, not the nodes: "Invoice reminders sent", "Leads routed", "Failed: CRM rejected 2 records". Keep customer data out of the summary; task titles and counts are enough.
- Collect the runs. Either read executions with an n8n API key (no change to the workflows), or add a last HTTP Request node to each workflow that posts a short status line to wherever you keep the record.
- Catch failures too. Set an n8n error workflow (it starts with the Error Trigger node and runs when another workflow fails) so a failure is recorded, not just a success.
- Estimate the time saved honestly. Agree a per-run estimate with the client ("a person took about 5 minutes to do this by hand") and multiply by the runs. Write down that it is an estimate and who agreed it.
- Share it on a schedule. A page the client can open any time, plus a weekly or monthly report they can forward. Name what failed and what you did about it; that builds more trust than a clean chart.
How Bot Office does it
Bot Office does these steps for you. On the connect page, "Watch my workflows" takes an n8n API key and reads your run history, with no changes to your workflows (n8n guide; Make works the same way). Each workflow gets a desk in an office branded from the client's website.
Clients sign in with their own login and role (viewer, member, approver or admin), and the weekly and monthly reports print or save as PDF, with hours saved, value and failures. A bot that never reported a figure shows "not reported", not zero. To see what it looks like first, open the sandbox or an example use case (sample data, marked DEMO).
Questions
Do my clients need an n8n account?
No. The record lives outside n8n; clients see outcomes, never the editor or its credentials.
Does Bot Office change my n8n workflows?
No. With an API key it only reads run history. Adding a reporting node is optional, for richer step-by-step lines.
Is it free?
Yes. Bot Office is free, with no card and no plan to pick (pricing).
Sources
Facts about other products are from their own documentation, linked above, as read on the date at the top. Bot Office is not certified or endorsed by their makers.