n8n workflow templates that survive production.

Each folder holds the workflow.json to import and a README: the accounts it needs and setup in five steps or fewer. The same notes sit on the canvas, so you never have to leave n8n. No credentials ship in the files; you pick your own on import.

A workflow that works once in the editor is a demo. The ones that run for months share a few habits, and every workflow in this pack has them. They are the same habits behind the n8n workflows we run in production.

• Retries on every outside call. Three tries, a few seconds apart, so a one-off timeout never becomes an incident.
• A failure path. A run that still fails reports to the shared error workflow, which posts the workflow, the step, the error and a link to Slack.
• Checked input. Webhooks reject a bad request with a clear reason instead of failing halfway through.
• No duplicates. Contacts are matched on email and posts on their canonical URL, so sending the same thing twice is harmless.
• An agent on a leash. The AI agent drafts emails rather than sending them, stops after 8 tool steps, and says when a tool fails instead of inventing a result.

// On every step that calls an outside service:
"retryOnFail": true,
"maxTries": 3,
"waitBetweenTries": 5000

// On every workflow (Settings > Error workflow):
"errorWorkflow": "Error alerts (shared)"

And this is what a real failure looks like when it reaches you:

Lead capture to HubSpot failed at Create or update the contact
> Request failed with status code 401
HTTP status: 401
Open the failed execution  ->  link to the run in n8n

1. Import 05-error-alerts, paste a Slack incoming-webhook URL into its Settings step, and activate it.
2. Import the others: Workflows, then Import from file.
3. Pick your own credentials on each step that asks, and follow the note on the canvas.
4. In each workflow, set Settings, then Error workflow, to “Error alerts (shared)”, and activate.

Error workflows only fire for production runs, never for a test click in the editor. The KPI digest needs the workflow’s own timezone set, or it drifts an hour when the clocks change: here is why, and the fix.

Building an agent from a blank canvas instead? Our n8n AI agent tutorial walks through every step. Still choosing a tool? See n8n vs Zapier first. And if you would rather have it built and run for you, that is what our n8n automation services are for.