I will build production n8n workflows with error handling and docs

Most automations fail silently. You find out a week later when a customer complains.

I build n8n workflows the way you'd build production software: every API call has

retry and error handling, every run is logged, and you get a runbook so you know

what to do when something breaks.

What you get:

- Clean node structure with named branches (no spaghetti)

- Retry + fallback on every external API call

- An error workflow that alerts you instead of failing silently

- All workflows exported to your GitHub, version-controlled

- A one-page runbook: what it does, who owns it, what to do when it fails

I self-host n8n in production myself. I'm not a no-code reseller if your workflow

needs custom JavaScript or a Python transform, I write it instead of telling you

it can't be done.

See my work before you hire me:

- Source code: github.com/xjl5620145/schema-lint

Before ordering, message me with: (1) what you're automating, (2) which apps are

involved, (3) roughly how many runs per month. I'll tell you honestly if it's a

good fit or if there's a simpler way.