5 n8n Workflow Mistakes That Will Break Your Production Automations

Most n8n tutorials show you how to build workflows. This one shows you the 5 mistakes that make those workflows fail in production. I've been running n8n workflows in production for over a year. Here's what breaks. Mistake 1: No Error Handling Every workflow that touches an external API will fail eventually. Rate limits, timeouts, server errors — they all happen. What breaks: HTTP Request → Process Data → Save to Sheet If the API returns 429, the workflow crashes and you never know. Fix: HTTP Request → Error Trigger → Retry Logic → Telegram Alert Add an Error Trigger node at the workflow level. Set up a Telegram notification (30 seconds to configure) so you know immediately when something fails. For retryable errors, use a Wait node + loop back to the HTTP Request. Mistake 2: Hardcoding Credentials in Node Config New users put API keys directly in HTTP Request nodes. This means: Keys are visible in exported JSON Can't rotate keys without editing every workflow Can't share workflows saf