<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Shawn Carter</title>
    <description>The latest articles on DEV Community by Shawn Carter (@shawncarter_autoesta).</description>
    <link>https://dev.to/shawncarter_autoesta</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4253621%2F73635791-ca81-40d6-a536-86989e08d41e.png</url>
      <title>DEV Community: Shawn Carter</title>
      <link>https://dev.to/shawncarter_autoesta</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shawncarter_autoesta"/>
    <language>en</language>
    <item>
      <title>Making n8n Workflows Reliable: Error Workflows, Retries and Idempotency</title>
      <dc:creator>Shawn Carter</dc:creator>
      <pubDate>Thu, 19 Nov 2026 11:14:47 +0000</pubDate>
      <link>https://dev.to/shawncarter_autoesta/making-n8n-workflows-reliable-error-workflows-retries-and-idempotency-4epf</link>
      <guid>https://dev.to/shawncarter_autoesta/making-n8n-workflows-reliable-error-workflows-retries-and-idempotency-4epf</guid>
      <description>&lt;p&gt;&lt;em&gt;By Shawn Carter, Manager at Autoesta. We build and host n8n workflows for service businesses.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The scary failure in automation isn't the one that throws a red error. It's the one that fails quietly: a webhook times out, a lead never reaches the CRM, and nobody notices for a week. Here's the checklist we use on every n8n build before it goes live.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Add an error workflow to every production workflow
&lt;/h2&gt;

&lt;p&gt;n8n lets you set an &lt;strong&gt;Error Workflow&lt;/strong&gt; in each workflow's settings. Build one small workflow that starts with the &lt;strong&gt;Error Trigger&lt;/strong&gt; node and sends the workflow name, the failed node, the error message and the execution URL to Slack or email. Then point every production workflow at it.&lt;/p&gt;

&lt;p&gt;Without this, a failed execution just sits in the executions list until someone happens to look.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Retry what is temporary, stop on what isn't
&lt;/h2&gt;

&lt;p&gt;Most nodes have &lt;strong&gt;Retry On Fail&lt;/strong&gt; in their settings, with a maximum number of tries and a wait between them. Turn it on for calls to outside APIs, where timeouts and rate limits are normal. Keep the wait long enough to get past a rate limit (several seconds, not milliseconds).&lt;/p&gt;

&lt;p&gt;Don't retry errors that won't fix themselves, like a 400 Bad Request or a missing required field. Retrying those only fills the logs. Route them to the error workflow instead.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Make every write idempotent
&lt;/h2&gt;

&lt;p&gt;Retries create a new problem: the same lead gets created twice. Fix it before it happens:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Search before create.&lt;/strong&gt; Look up the contact by email or phone, and update it if it exists.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use the source system's ID.&lt;/strong&gt; Store the form submission ID or webhook event ID, and skip events you've already processed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prefer upsert endpoints&lt;/strong&gt; when the API offers them.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  4. Answer webhooks fast
&lt;/h2&gt;

&lt;p&gt;If the sending service waits for a reply and your workflow does heavy work first, the sender may time out and resend the event. Set the Webhook node to respond immediately (or use the &lt;strong&gt;Respond to Webhook&lt;/strong&gt; node early), then do the slow work after. Combined with idempotent writes, resends stop being a problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Keep secrets in credentials
&lt;/h2&gt;

&lt;p&gt;Put API keys in n8n &lt;strong&gt;Credentials&lt;/strong&gt;, never in node parameters or Code nodes. They stay out of exported workflow JSON, and rotating a key means changing it in one place.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Watch the executions weekly
&lt;/h2&gt;

&lt;p&gt;Even with alerts, look at the failed executions once a week. Patterns show up: one API that times out every Monday morning, or a form field someone renamed. Fifteen minutes a week saves a lot of lost leads.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where n8n fits
&lt;/h2&gt;

&lt;p&gt;We keep messaging and pipeline logic inside the CRM (usually GoHighLevel) and use n8n for work that crosses systems: syncing to accounting tools, enriching leads, moving data between apps. If you'd rather not host and monitor it yourself, this is the kind of work we do at &lt;a href="https://autoesta.com/n8n-automation/" rel="noopener noreferrer"&gt;Autoesta&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>automation</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
