n8n Workflows
Production n8n workflows, hardened patterns
Multi-provider LLM, no memory required. For cross-session memory see n8n-templates.
What it solves
Most public n8n templates show the happy path and stop. They skip signature verification on public webhooks, swallow model errors silently, write duplicate records when a provider retries, and leave rate limiting as an exercise for the reader. We audited five widely starred template repositories in April 2026 and the gap was consistent across all of them.
How it works
Fifteen or so workflows covering the usual production jobs: a CRM router, Stripe, uptime and certificate checks, a Slack digest, Calendly, GitHub, RSS, calendar, CSV, mail into Notion, Postgres into Sheets, a webhook audit, a Telegram translator and YouTube into Notion. Every one of them ships four production patterns as nodes inside the workflow file, gated by environment variables and off by default so the import boots clean: signature verification on the webhook, an idempotency check, a rate limit, and error branches with a graceful fallback. Flip one variable to turn a pattern on for production.
When to use it
Take these when the workflow is going to run unattended against someone else system, which is exactly where the missing patterns bite. They are deliberately memory-free, so they are also the simpler starting point when the workflow does not need to remember anything.
When not to use it
If you want the bot to remember who called yesterday, this is the wrong repository: n8n-templates is the sibling with memory wired in. Both share the same production-pattern foundation and the only difference is whether the memory layer is connected.
Stars
★ 0
Clones (14d)
⊟ 14
Language
Python
Updated
2026-08-01