n8n automation
n8n workflows that still work in month fourteen
n8n makes it easy to connect a form to an AI model to a spreadsheet in an afternoon. What it doesn't do for you is decide what happens when the API times out, the model returns nonsense or the same webhook arrives twice. That is the part I build in from the start.
Sounds familiar?
Where the hours go today
- Workflows that worked in testing fail quietly in production and nobody notices for days.
- A failed run means someone re-running it by hand, sometimes twice.
- AI steps return output in a different shape every few hundred runs and break the next node.
- The person who built the workflows has left and nobody dares to touch them.
How it works
The same job, before and after.
AI steps with validation and a fallback
Every AI step returns structured output that is checked before the workflow continues. Output that doesn't fit is retried once, then routed to a person instead of breaking the run.
By hand today
- Webhook
- AI step
- Breaks on odd output
With automation
- Webhook
- AI step with a fixed schema
- Checked, then saved
- Bad output goes to review
Errors you hear about
A shared error workflow catches every failure, retries what is safe to retry, and sends you a message with the run, the input and the reason, instead of a red dot nobody checks.
By hand today
- Run fails
- Found days later
With automation
- Run fails
- Retry if safe
- Alert with the reason
What you get
- New workflows, or an audit and rescue of the ones you already have
- Self-hosted n8n on your server (Docker, backups, updates) or n8n Cloud
- Error workflow, retries, deduplication of repeated webhooks
- Structured AI output with validation, plus a human review queue
- Documentation your team can follow without me
Built so it doesn't embarrass you
- Credentials stay in n8n's credential store, never in workflow JSON.
- Workflows are exported to Git, so every change can be reviewed and rolled back.
- Duplicate webhook deliveries are detected, so nothing is processed twice.
Questions
Frequently asked
Self-hosted n8n or n8n Cloud?
Cloud if you want no server to look after. Self-hosted if you have data that shouldn't leave your infrastructure or many executions, where it is much cheaper. I set up either, including backups and updates for self-hosted.
Can you fix workflows someone else built?
Yes, that is a common start. I go through them, list what can fail and how, fix the risky parts first and document the rest.
n8n, Make or Zapier?
Zapier is the simplest for small, linear tasks. Make and n8n handle branching and larger volumes; n8n can be self-hosted and lets you write code where a node isn't enough. For AI-heavy workflows I usually recommend n8n.
Not sure this fits your business?
Answer eight short questions about how your week looks. Within two working days you get a written answer: what can be automated, how it would work and roughly what it would cost. Free, no call needed.
Start the free checkOther automations