What happens when an automation breaks or fails?
Someone gets told. Our n8n workflows report a failure to a named person, with the step that failed. The usual causes are an expired login, a service changing its API, or data arriving in an unexpected format. We fix the cause, then re-run the failed items.
Why automations fail
- A login or API key expires
- A service changes how its API works
- A field arrives empty or in a different format
- The server the automation runs on needs an update
How we find out
Each workflow has an error alert that goes to a named person, saying which workflow failed and at which step. A failure doesn't sit unnoticed in a log.
How we fix it
We look at the run history, find the step, fix the cause and re-run the items that failed. Because each workflow is small and does one job, it's clear where to look.
The risk of running it ourselves
We host n8n on our own server, so server updates and backups are down to us. That's part of the ongoing management service.
Also worth asking
Other answers about the same tools.
How do you measure the return on an automation, whether it's n8n or Zapier?
We count what it replaces. Before we build, we write down how long the manual job takes and how often it happens. After launch, we look at how many times the workflow ran, how often it failed, and the time it saved against what it costs to run.
We don't quote a standard payback period, because it depends on the job.
Can n8n handle complex multi-step marketing workflows, and how does it compare with Zapier?
Yes. We build multi-step workflows in n8n that branch on conditions, loop over lists, wait, run a bit of code and call any service with an API. Zapier can do multi-step work too, with paths, filters and delays, but it bills by task, so long workflows that run often get expensive. On an n8n server we run ourselves, you pay for the server, not the number of steps.
Here's one of ours: a form comes in on this site, a switch routes it by form name, a row goes into a sheet, a person and an opportunity are created in the CRM, the team gets an alert, and any failure goes to a named person.
How does n8n pricing work, and how does it compare with Zapier?
Zapier bills by how many tasks you run each month, in plan tiers. n8n's own cloud plans bill by workflow executions. We go a third way: we run n8n ourselves on a small server, so we pay for the server and the time to keep it updated, not for each task.
For current prices, check Zapier's and n8n's pricing pages.
What are the most useful automations for a marketing agency?
The ones that move a lead along without anyone copying it. These are the ones we rely on, built in n8n:
- Form fill to CRM person, opportunity and team alert
- Real leads sent back to Google Ads as offline conversions
- Alerts when a workflow or a form fails
- A cache clear when a site ships
Zapier can do some of these too.
How do you set up and manage n8n automations for clients?
We start with the manual process and the record it should end up with. Then we build the smallest workflow that does that, test it with a real submission, and send any error to a named person.
- Write down the manual process and what it should produce
- Build one small workflow, named for its job
- Test it with a real submission before it goes live
- Send failures to a person, not to a log nobody reads
- Check the runs after launch, then regularly
It's part of our ongoing management service.
Still have questions?Talk to us
Bring your numbers.
We'll tell you if the spend makes sense.
- A 15-minute callYour goals, your challenges, and whether we're the right fit.
- A 1-hour discovery callWe dig into your numbers. Worth a hundred emails.
- A concrete planAds, a custom build or both, as a one-off project or ongoing.