<?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: Viet Automation</title>
    <description>The latest articles on DEV Community by Viet Automation (@vietautomation).</description>
    <link>https://dev.to/vietautomation</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%2F4216812%2Fe9bdba16-ea49-4bd4-bfe2-aae95572e38b.png</url>
      <title>DEV Community: Viet Automation</title>
      <link>https://dev.to/vietautomation</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vietautomation"/>
    <language>en</language>
    <item>
      <title>Your AI Outreach Read "No" as "Yes": Classify Replies Before the Next Step (n8n / Make, 2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Fri, 20 Nov 2026 02:11:38 +0000</pubDate>
      <link>https://dev.to/vietautomation/your-ai-outreach-read-no-as-yes-classify-replies-before-the-next-step-n8n-make-2026-3nlg</link>
      <guid>https://dev.to/vietautomation/your-ai-outreach-read-no-as-yes-classify-replies-before-the-next-step-n8n-make-2026-3nlg</guid>
      <description>&lt;h1&gt;
  
  
  Why does my AI email automation treat "no" as "yes"?
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; because the sequence is usually wired to advance on &lt;em&gt;any&lt;/em&gt; reply. The AI writes a polite follow-up, and the workflow treats "a reply arrived" as "the person agreed". The fix is a small gate between the inbound reply and the next step: &lt;strong&gt;classify the reply into a fixed set of intents, stop the sequence on "no" or "stop", send anything unclear to a human, and only advance on an explicit yes.&lt;/strong&gt; Default to &lt;em&gt;not&lt;/em&gt; advancing.&lt;/p&gt;

&lt;p&gt;This came up in r/automation on 18 November 2026. The poster got an AI-written outreach email inviting them to an interview, replied "no" because they were not interested, and the automation "wrote back, thanked me for confirming, and moved me to the next step." Their conclusion: "the only word these kinds of AI automations understand is 'stop.'" (&lt;a href="https://www.reddit.com/r/automation/comments/1xzmqdj/slop_email_automation_that_took_my_no_as_a_yes/" rel="noopener noreferrer"&gt;thread&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;That is not just embarrassing. It burns the sender's reputation, and in many places ignoring someone who asked you to stop contacting them is a legal problem, not only a UX one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the bug usually lives
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Pattern&lt;/th&gt;
&lt;th&gt;What goes wrong&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Trigger: "new reply in thread" → next step&lt;/td&gt;
&lt;td&gt;Any reply, including "no", "wrong person" or an auto-reply, counts as engagement&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LLM asked to "write a friendly response to this reply"&lt;/td&gt;
&lt;td&gt;The model is optimised to be agreeable, so it confirms whatever the sequence wanted&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Keyword filter for "unsubscribe" / "stop" only&lt;/td&gt;
&lt;td&gt;"No thanks", "not interested", "please remove me" slip through&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Out-of-office treated as a reply&lt;/td&gt;
&lt;td&gt;The sequence advances while the person is away&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  The reply-intent gate
&lt;/h2&gt;

&lt;p&gt;Put one step between "reply received" and anything that sends, books or updates a CRM stage.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Classify into a closed list, not free text.&lt;/strong&gt; Ask the model (or a rules step) to return exactly one label as JSON:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;yes&lt;/code&gt;: clear agreement to the specific next step&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;no&lt;/code&gt;: declines, not interested&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;stop&lt;/code&gt;: asks to be removed, unsubscribe, do not contact&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;wrong_person&lt;/code&gt;: not the right contact&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;auto_reply&lt;/code&gt;: out-of-office, bounce, ticket acknowledgement&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;question&lt;/code&gt;: asks something before deciding&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;unclear&lt;/code&gt;: anything else&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Validate the output. If the label is not in the list, or the JSON does not parse, treat it as &lt;code&gt;unclear&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Route on the label, with a safe default.&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Label&lt;/th&gt;
&lt;th&gt;Action&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;yes&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Advance, but only if the reply is from the same address you contacted&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;no&lt;/code&gt;, &lt;code&gt;stop&lt;/code&gt;, &lt;code&gt;wrong_person&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;End the sequence, mark the contact do-not-contact, send nothing automated (or one short confirmation if your policy requires it)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;auto_reply&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Pause the sequence; do not count it as a reply&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;question&lt;/code&gt;, &lt;code&gt;unclear&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Send to a human review queue; the sequence waits&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The key rule: &lt;strong&gt;the only path that advances is an explicit &lt;code&gt;yes&lt;/code&gt;.&lt;/strong&gt; Everything else stops or waits.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Check the suppression list before every send, not just at the start.&lt;/strong&gt; A contact can opt out between step 2 and step 3. Read the do-not-contact flag right before each outgoing message.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Keep the AI out of the decision on what happens next.&lt;/strong&gt; The model can classify and draft. The workflow decides, based on the label. Never let a "write a reply" prompt also choose whether to move the person forward.&lt;/p&gt;

&lt;h2&gt;
  
  
  In n8n
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Trigger on the inbound email (IMAP, Gmail or your outreach tool's webhook).&lt;/li&gt;
&lt;li&gt;AI step (or Text Classifier) with the closed label list; ask for JSON only.&lt;/li&gt;
&lt;li&gt;A Code or IF step that checks the label against the allowed list and falls back to &lt;code&gt;unclear&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;A Switch node on the label: &lt;code&gt;yes&lt;/code&gt; → next step; &lt;code&gt;no/stop/wrong_person&lt;/code&gt; → update CRM / sheet do-not-contact column and stop; &lt;code&gt;auto_reply&lt;/code&gt; → pause; &lt;code&gt;question/unclear&lt;/code&gt; → Slack or email to a human with the original reply.&lt;/li&gt;
&lt;li&gt;Before every send node, a lookup on the do-not-contact column with an IF that stops the run.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  In Make
&lt;/h2&gt;

&lt;p&gt;The same shape: watch replies → AI module returning one label → a Router with a filter per label → a Data store or sheet acting as the suppression list, checked by a filter before every send module. If you want to build it visually, you can &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;try Make here&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test it before it touches real people
&lt;/h2&gt;

&lt;p&gt;Feed the gate a small set of sample replies and check every label. Include at least:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"No" / "No thanks" / "Not interested"&lt;/li&gt;
&lt;li&gt;"Please remove me from your list"&lt;/li&gt;
&lt;li&gt;"Wrong person, I left the company"&lt;/li&gt;
&lt;li&gt;An out-of-office message&lt;/li&gt;
&lt;li&gt;"What does the role pay?" (a question, not a yes)&lt;/li&gt;
&lt;li&gt;"Sure" (a yes)&lt;/li&gt;
&lt;li&gt;"Yes, please stop emailing me" (contains "yes" but means stop)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If any "no" or "stop" sample advances, the gate is not ready.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Sequence never advances on "any reply"&lt;/li&gt;
&lt;li&gt;[ ] Closed list of intent labels, validated, unknown → &lt;code&gt;unclear&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] Only explicit &lt;code&gt;yes&lt;/code&gt; advances&lt;/li&gt;
&lt;li&gt;[ ] &lt;code&gt;no&lt;/code&gt;, &lt;code&gt;stop&lt;/code&gt;, &lt;code&gt;wrong_person&lt;/code&gt; end the sequence and set do-not-contact&lt;/li&gt;
&lt;li&gt;[ ] Out-of-office pauses instead of advancing&lt;/li&gt;
&lt;li&gt;[ ] Suppression list checked before every send&lt;/li&gt;
&lt;li&gt;[ ] Unclear replies go to a human&lt;/li&gt;
&lt;li&gt;[ ] Tested with tricky samples like "Yes, please stop emailing me"&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Bottom line
&lt;/h2&gt;

&lt;p&gt;An automation that only understands "stop" will eventually upset someone who said "no". Make "no" a first-class outcome, make "advance" the hardest path, and respect opt-outs on every step, not just the first.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Source: r/automation thread collected 19 November 2026 (Asia/Saigon). Opt-out and anti-spam rules differ by country; check the rules that apply to your recipients.&lt;/em&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>automation</category>
      <category>n8n</category>
      <category>ai</category>
      <category>email</category>
    </item>
    <item>
      <title>Self-Hosted n8n Keeps Crashing on a 2GB VPS: Concurrency Limit, Queue Mode or More RAM? (2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Thu, 19 Nov 2026 02:11:55 +0000</pubDate>
      <link>https://dev.to/vietautomation/self-hosted-n8n-keeps-crashing-on-a-2gb-vps-concurrency-limit-queue-mode-or-more-ram-2026-1jc1</link>
      <guid>https://dev.to/vietautomation/self-hosted-n8n-keeps-crashing-on-a-2gb-vps-concurrency-limit-queue-mode-or-more-ram-2026-1jc1</guid>
      <description>&lt;h1&gt;
  
  
  Why does self-hosted n8n crash when a few workflows run at once?
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; on a small VPS, the usual cause is memory, not CPU. Each running execution keeps its items (and often binary data) in the memory of the n8n process. When three heavy workflows overlap, that process grows until the Linux OOM killer stops it, and everything else on the box (editor, webhooks, Postgres) suffers with it. The fix order is: &lt;strong&gt;limit how many production executions run at once, shrink what each execution holds, stop saving data you never read, and only then choose between more RAM and queue mode.&lt;/strong&gt; Queue mode on its own does not give you more memory; it adds Redis and worker processes that also need RAM.&lt;/p&gt;

&lt;p&gt;This came up in r/n8n on 17 November 2026: someone running "n8n in Docker with Postgres on a 2 vCPU, 2GB VPS" with "about 40 active workflows" said that when "three of the heavier workflows fire together, executions hang, the editor times out and dmesg shows 'Out of memory: Killed process (node)'" (&lt;a href="https://www.reddit.com/r/n8n/comments/1xyf17k/selfhosted_n8n_on_a_2gb_vps_falls_over_when_three/" rel="noopener noreferrer"&gt;thread&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  Confirm it is really memory
&lt;/h2&gt;

&lt;p&gt;Before changing anything, check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;dmesg -T | grep -i "out of memory"&lt;/code&gt; or &lt;code&gt;journalctl -k | grep -i oom&lt;/code&gt;: an entry naming &lt;code&gt;node&lt;/code&gt; means the n8n process was killed.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;docker stats&lt;/code&gt; while the heavy workflows run: watch the n8n and Postgres containers.&lt;/li&gt;
&lt;li&gt;Which workflows were running at the time of the kill (execution list, start times).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If there is no OOM entry and the box is just slow, look at CPU, disk I/O and swap instead. Swap keeps the process alive but can make it so slow that webhooks time out, which looks like a hang.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: cap concurrent production executions
&lt;/h2&gt;

&lt;p&gt;Recent n8n versions support a concurrency limit for production executions in regular mode. Set &lt;code&gt;N8N_CONCURRENCY_PRODUCTION_LIMIT&lt;/code&gt; (for example to 2 on a 2GB box). Executions above the limit wait in a queue instead of all starting at once. Check the concurrency control page in the n8n docs for your version; manual and test executions are not counted the same way.&lt;/p&gt;

&lt;p&gt;This alone often stops the "three heavy jobs at once" crash, at the cost of some jobs starting later.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: make each execution hold less
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Habit&lt;/th&gt;
&lt;th&gt;Why it eats memory&lt;/th&gt;
&lt;th&gt;Change&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Pulling a whole table or API result in one call&lt;/td&gt;
&lt;td&gt;Every item sits in memory until the run ends&lt;/td&gt;
&lt;td&gt;Paginate, and process in batches (Loop Over Items)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Binary files kept in memory&lt;/td&gt;
&lt;td&gt;Large files multiply per item&lt;/td&gt;
&lt;td&gt;Set binary data mode to filesystem (&lt;code&gt;N8N_DEFAULT_BINARY_DATA_MODE=filesystem&lt;/code&gt;), check docs for your version&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scraping full HTML and passing it along&lt;/td&gt;
&lt;td&gt;Big strings copied through every node&lt;/td&gt;
&lt;td&gt;Extract the fields you need early, drop the rest with a Set/Edit Fields node&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;One giant workflow doing everything&lt;/td&gt;
&lt;td&gt;All data lives in one execution&lt;/td&gt;
&lt;td&gt;Split into sub-workflows that each return only a small result&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Step 3: stop saving what you never read
&lt;/h2&gt;

&lt;p&gt;Saved execution data lives in Postgres and is loaded when you open executions. On a small box, keep it lean:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;EXECUTIONS_DATA_PRUNE=true&lt;/code&gt; with a short &lt;code&gt;EXECUTIONS_DATA_MAX_AGE&lt;/code&gt; (hours).&lt;/li&gt;
&lt;li&gt;Do not save successful runs of high-volume webhooks (&lt;code&gt;EXECUTIONS_DATA_SAVE_ON_SUCCESS=none&lt;/code&gt;), keep errors.&lt;/li&gt;
&lt;li&gt;Give Postgres its own memory budget so it is not fighting n8n for the same 2GB.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 4: more RAM or queue mode?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;What it fixes&lt;/th&gt;
&lt;th&gt;What it costs&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Bigger VPS (e.g. 4GB)&lt;/td&gt;
&lt;td&gt;Headroom for spikes, simplest change&lt;/td&gt;
&lt;td&gt;Monthly cost, same single point of failure&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Queue mode (Redis + workers)&lt;/td&gt;
&lt;td&gt;Separates editor/webhooks from heavy execution, lets you add workers&lt;/td&gt;
&lt;td&gt;More moving parts, Redis and each worker need memory; on the same 2GB box it can make things worse&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Move heavy scraping elsewhere&lt;/td&gt;
&lt;td&gt;Keeps n8n for orchestration only&lt;/td&gt;
&lt;td&gt;Another service to run&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A reasonable rule: if steps 1 to 3 keep you stable, stay on one box. If you still hit the limit with concurrency capped, add RAM first. Move to queue mode when you need workers on separate machines or need the editor and webhooks to stay responsive while heavy jobs run.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] OOM kill confirmed in kernel logs, not guessed&lt;/li&gt;
&lt;li&gt;[ ] Production concurrency limit set&lt;/li&gt;
&lt;li&gt;[ ] Heavy workflows paginate and batch&lt;/li&gt;
&lt;li&gt;[ ] Binary data not held in memory&lt;/li&gt;
&lt;li&gt;[ ] Execution data pruned; successful high-volume runs not saved&lt;/li&gt;
&lt;li&gt;[ ] Postgres has its own memory budget&lt;/li&gt;
&lt;li&gt;[ ] Decision on RAM vs queue mode made after the above&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Does the same problem exist in Make?
&lt;/h2&gt;

&lt;p&gt;Make is hosted, so you do not manage server memory, but you still pay per operation and hit scenario limits if you pull everything at once. The same habits (paginate, filter early, avoid passing large payloads) apply. If you would rather not run a server at all, you can &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;try Make here&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Sources: r/n8n thread collected 18 November 2026 (Asia/Saigon). Environment variable names and defaults change between n8n versions; check the official n8n docs for your version before applying.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Want to build this visually? You can &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;try Make here&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>selfhosted</category>
      <category>devops</category>
      <category>automation</category>
    </item>
    <item>
      <title>Voice Agent Call Drops in n8n: How to Handle and Test Them Before a Client Does (2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Tue, 17 Nov 2026 02:17:45 +0000</pubDate>
      <link>https://dev.to/vietautomation/voice-agent-call-drops-in-n8n-how-to-handle-and-test-them-before-a-client-does-2026-4f3k</link>
      <guid>https://dev.to/vietautomation/voice-agent-call-drops-in-n8n-how-to-handle-and-test-them-before-a-client-does-2026-4f3k</guid>
      <description>&lt;h1&gt;
  
  
  How do I handle a dropped call in a voice agent automation?
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; stop treating a call as one webhook that either succeeds or fails. Treat it as a record with a status (&lt;code&gt;started&lt;/code&gt;, &lt;code&gt;in_progress&lt;/code&gt;, &lt;code&gt;completed&lt;/code&gt;, &lt;code&gt;dropped&lt;/code&gt;, &lt;code&gt;unknown&lt;/code&gt;) that your workflow opens when the call starts and closes when the call ends. Every downstream action (booking, CRM update, follow-up SMS or email) reads that status first. A call that never reports a proper end gets closed by a timeout job and routed to a human or a callback queue, not silently forgotten.&lt;/p&gt;

&lt;p&gt;This came up in r/n8n on 16 November 2026: "if u are automating using voice agents, how do u handle call-drop situtation or bad network scenarios?" and whether people "manually dry-run those cases" (&lt;a href="https://www.reddit.com/r/n8n/comments/1xxrp0c/if_you_are_building_automation_with_voice_agents/" rel="noopener noreferrer"&gt;thread&lt;/a&gt;). The same day another r/n8n thread described the wider problem for people running agents for clients: "a workflow dies, nobody notices for days, and the client finds out first" (&lt;a href="https://www.reddit.com/r/n8n/comments/1xxlptb/how_do_you_find_out_when_a_client_ai_agent_or/" rel="noopener noreferrer"&gt;thread&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  What actually goes wrong when a call drops
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Situation&lt;/th&gt;
&lt;th&gt;What the workflow sees&lt;/th&gt;
&lt;th&gt;Typical damage&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Caller hangs up mid-sentence&lt;/td&gt;
&lt;td&gt;An end event with a short or partial transcript&lt;/td&gt;
&lt;td&gt;Half-filled booking, or an AI summary that guesses the missing part&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Network drops, call ends abnormally&lt;/td&gt;
&lt;td&gt;An end event with an error or unusual end reason, or no end event at all&lt;/td&gt;
&lt;td&gt;Record stays "in progress" forever&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Call reconnects as a new call&lt;/td&gt;
&lt;td&gt;Two separate call IDs for one person&lt;/td&gt;
&lt;td&gt;Duplicate leads, two follow-ups&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Your webhook is down when the end event fires&lt;/td&gt;
&lt;td&gt;Nothing, unless the provider retries&lt;/td&gt;
&lt;td&gt;Call happened, workflow never knew&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;End event arrives twice (provider retry)&lt;/td&gt;
&lt;td&gt;Same call ID twice&lt;/td&gt;
&lt;td&gt;Double SMS, double CRM note&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;None of these are exotic. If your agent takes real calls, all of them will happen.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pattern
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Open a call record at the start
&lt;/h3&gt;

&lt;p&gt;When the call starts (or when your workflow places an outbound call), write one row to a table you control: call ID, phone number, client, started_at, status &lt;code&gt;started&lt;/code&gt;. A Postgres table, Airtable, or a Google Sheet all work for small volume. The call ID from your voice provider is the key.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Close it from the end-of-call event
&lt;/h3&gt;

&lt;p&gt;Most voice agent platforms can send an end-of-call webhook with the call ID, an end reason, a duration, and the transcript. Field names differ by provider, so read your provider's docs and map them once. In n8n:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Webhook&lt;/strong&gt; node receives the end event.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Look up&lt;/strong&gt; the call row by call ID. If the row is already closed, stop here (this is your duplicate guard).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Classify&lt;/strong&gt; the call with plain rules, not with the LLM:

&lt;ul&gt;
&lt;li&gt;normal end reason and the required fields captured -&amp;gt; &lt;code&gt;completed&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;caller hung up or error end reason, or required fields missing -&amp;gt; &lt;code&gt;dropped&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;anything you do not recognise -&amp;gt; &lt;code&gt;unknown&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Update&lt;/strong&gt; the row with status, end reason, duration, and transcript.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Route&lt;/strong&gt; by status (Switch node).&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  3. Only act on what was actually captured
&lt;/h3&gt;

&lt;p&gt;The dangerous step is the AI summary. Given half a transcript, a model will often produce a confident, complete-looking summary. So:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Define the fields a call must capture to count (for a booking: name, date, time, confirmation).&lt;/li&gt;
&lt;li&gt;Check those fields exist in the structured output before you book anything.&lt;/li&gt;
&lt;li&gt;If any are missing, the status is &lt;code&gt;dropped&lt;/code&gt;, whatever the summary says.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  4. Route dropped calls to a recovery path
&lt;/h3&gt;

&lt;p&gt;For &lt;code&gt;dropped&lt;/code&gt; and &lt;code&gt;unknown&lt;/code&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Create a task or Slack message for a human with the phone number, what was captured, and the transcript.&lt;/li&gt;
&lt;li&gt;Or queue one callback attempt, if the client has agreed to callbacks and local rules allow it. Keep it to a small, fixed number of attempts and log each one.&lt;/li&gt;
&lt;li&gt;Never send the "your appointment is confirmed" message from this path.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  5. Close stuck calls with a timeout job
&lt;/h3&gt;

&lt;p&gt;A &lt;strong&gt;Schedule Trigger&lt;/strong&gt; every 10 to 15 minutes finds rows still &lt;code&gt;started&lt;/code&gt; or &lt;code&gt;in_progress&lt;/code&gt; older than your longest realistic call plus a margin. Mark them &lt;code&gt;unknown&lt;/code&gt;, and send them down the same recovery path. This catches the case where the end event never arrived, which is the one nobody notices.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Merge reconnects
&lt;/h3&gt;

&lt;p&gt;Before creating a new lead from a call, check for another call from the same number for the same client in the last few minutes. If there is one, attach this call to it instead of creating a second lead.&lt;/p&gt;

&lt;h2&gt;
  
  
  Testing drop cases without making live calls
&lt;/h2&gt;

&lt;p&gt;You do not need to dry-run calls by hand. Once your workflow is built around the call record:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Save real payloads.&lt;/strong&gt; From your provider's logs or n8n execution history, save one end-of-call payload for each case: normal end, caller hang-up, error end, very short call, and a duplicate of a normal end.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Replay them.&lt;/strong&gt; Use a Manual Trigger plus a Code or Set node that emits each saved payload into the same processing sub-workflow the webhook uses. Pinned data in n8n works for this too.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Assert the outcome.&lt;/strong&gt; For each payload, check the row ends in the expected status and that only the expected side effects ran (no booking for a hang-up, one SMS for a duplicate end event).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test the silent case.&lt;/strong&gt; Insert a &lt;code&gt;started&lt;/code&gt; row with an old timestamp and confirm the timeout job picks it up.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Re-run after every change&lt;/strong&gt; to the prompt, the provider, or the field mapping.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Keep the payloads free of real personal data: replace names and numbers with test values before you store them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Every call has one row keyed by the provider call ID&lt;/li&gt;
&lt;li&gt;[ ] End events are idempotent (second arrival does nothing)&lt;/li&gt;
&lt;li&gt;[ ] Status comes from rules and captured fields, not from the AI summary&lt;/li&gt;
&lt;li&gt;[ ] Confirmation messages only go out on &lt;code&gt;completed&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] Dropped and unknown calls reach a human or a bounded callback queue&lt;/li&gt;
&lt;li&gt;[ ] A timeout job closes calls that never reported an end&lt;/li&gt;
&lt;li&gt;[ ] Reconnects from the same number merge into one lead&lt;/li&gt;
&lt;li&gt;[ ] Saved payloads replay every drop case after each change&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Does this work in Make too?
&lt;/h2&gt;

&lt;p&gt;Yes. The same shape applies: a webhook scenario for the end event, a Data Store or sheet for call records, a router on status, and a scheduled scenario for the timeout sweep. If you are choosing a tool to run this, you can &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;try Make here&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Sources: r/n8n threads collected 17 November 2026 (Asia/Saigon). Field names and end-reason values depend on your voice provider; check its documentation before mapping.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Want to build this visually? You can &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;try Make here&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>automation</category>
      <category>ai</category>
      <category>voiceagents</category>
    </item>
    <item>
      <title>Validate Every Row Before It Costs Money: Pre-flight Checks for Paid AI Batches in n8n (2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Mon, 16 Nov 2026 02:12:54 +0000</pubDate>
      <link>https://dev.to/vietautomation/validate-every-row-before-it-costs-money-pre-flight-checks-for-paid-ai-batches-in-n8n-2026-1fnp</link>
      <guid>https://dev.to/vietautomation/validate-every-row-before-it-costs-money-pre-flight-checks-for-paid-ai-batches-in-n8n-2026-1fnp</guid>
      <description>&lt;h1&gt;
  
  
  How do I stop bad rows from burning money in an n8n AI batch?
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; put a validation step between "read the sheet" and "call the paid API". For each row, look up the rules for the model that row targets (allowed durations, resolutions, aspect ratios, whether audio or a reference image is supported, prompt length), check the row against them, and split the batch in two. Valid rows go to the paid call. Invalid rows go back to the sheet with status &lt;code&gt;rejected&lt;/code&gt; and a plain reason, and nothing is spent on them.&lt;/p&gt;

&lt;p&gt;This came up in r/n8n on 15 November 2026. A builder running batch video through n8n, with some rows going to Seedance 2.5 and some to Kling 4.0, put it this way: a row that is fine for one model is "a 400 error, or worse a valid but wrong render, for another" (&lt;a href="https://www.reddit.com/r/n8n/comments/1xwrlzy/mixing_seedance_25_and_kling_40_in_one_n8n_batch/" rel="noopener noreferrer"&gt;thread&lt;/a&gt;). A day earlier, another r/n8n thread asked for people's most expensive n8n mistake, listing "duplicate emails, lost leads, incorrect invoices", with a bonus for cases where "n8n said the execution was successful" (&lt;a href="https://www.reddit.com/r/n8n/comments/1xwbe6e/whats_the_most_expensive_mistake_youve_made_with/" rel="noopener noreferrer"&gt;thread&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a 400 is the cheap failure
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What happens&lt;/th&gt;
&lt;th&gt;Cost&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;API rejects the row with a 400&lt;/td&gt;
&lt;td&gt;Usually free, but the batch may stop or retry&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;API accepts a row it silently adjusts (wrong duration, cropped ratio, audio dropped)&lt;/td&gt;
&lt;td&gt;You pay for a render you cannot use&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Retry logic re-sends a bad row several times&lt;/td&gt;
&lt;td&gt;You pay for the same failure again&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Row is valid but a duplicate of one already rendered&lt;/td&gt;
&lt;td&gt;You pay twice for the same output&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The expensive cases are the ones the API accepts. That is why the check belongs in your workflow, before the call, not in the provider's error handling.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pattern
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Keep model rules in one place.&lt;/strong&gt; A small JSON object (or a "Model Rules" sheet tab) keyed by model name. Fill the values from each provider's current documentation, and record the date you checked, because limits change between model versions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Normalize the row first.&lt;/strong&gt; Trim strings, lowercase the model name, turn "10s" into &lt;code&gt;10&lt;/code&gt;, turn "yes"/"TRUE" into &lt;code&gt;true&lt;/code&gt;. Most rejects are formatting, not intent.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Validate against the rules for that row's model.&lt;/strong&gt; Unknown model, value not in the allowed list, reference image required but missing, prompt too long: each one becomes a short reason string.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Skip what you already paid for.&lt;/strong&gt; Hash the normalized row (model + prompt + settings). If the hash is already marked &lt;code&gt;done&lt;/code&gt; in your sheet or database, skip it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Split, then spend.&lt;/strong&gt; Use an IF node on &lt;code&gt;valid&lt;/code&gt;. The true branch goes to the paid call. The false branch writes &lt;code&gt;rejected&lt;/code&gt; and the reasons back to the sheet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cap the batch.&lt;/strong&gt; Before the paid branch, count the valid rows and stop if the count is above a limit you set, so a pasted sheet of 2,000 rows cannot run by accident.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The rules object
&lt;/h2&gt;

&lt;p&gt;The values below are &lt;strong&gt;placeholders, not real model limits&lt;/strong&gt;. Replace them with what each provider documents today.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"checked_on"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"YYYY-MM-DD"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"models"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"model-a"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nl"&gt;"durations"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;5&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"resolutions"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"720p"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"1080p"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"aspect_ratios"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"16:9"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"9:16"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"1:1"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"audio"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"reference_image"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"optional"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"max_prompt_chars"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;2000&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"model-b"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nl"&gt;"durations"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;5&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"resolutions"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"720p"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"aspect_ratios"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"16:9"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"9:16"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"audio"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"reference_image"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"required"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"max_prompt_chars"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1500&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  The Code node
&lt;/h2&gt;

&lt;p&gt;Run this in "Run Once for All Items" mode. It reads the rules from a previous node named &lt;code&gt;Model Rules&lt;/code&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;rules&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nv"&gt;$(&lt;/span&gt;&lt;span class="s1"&gt;'Model Rules'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;first&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;models&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;out&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;item&lt;/span&gt; &lt;span class="k"&gt;of&lt;/span&gt; &lt;span class="nv"&gt;$input&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;all&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;item&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;row&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;model&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;model&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;trim&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toLowerCase&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;prompt&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;prompt&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;trim&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;duration&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;parseInt&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;duration&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="o"&gt;^&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;9&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;g&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;resolution&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;resolution&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;trim&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toLowerCase&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;aspect_ratio&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;aspect_ratio&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;trim&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;audio&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'true'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;'yes'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;'1'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;audio&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;trim&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toLowerCase&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;reference_image&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;reference_image&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;trim&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;m&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;model&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`unknown model "${row.model}"`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;else&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;prompt&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'empty prompt'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;prompt&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;length&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;max_prompt_chars&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`prompt over ${m.max_prompt_chars} chars`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;durations&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;duration&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`duration ${row.duration} not in [${m.durations}]`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;resolutions&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;resolution&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`resolution ${row.resolution} not allowed`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;aspect_ratios&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;aspect_ratio&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`aspect ratio ${row.aspect_ratio} not allowed`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;audio&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;audio&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'audio not supported by this model'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;reference_image&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="s1"&gt;'required'&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;reference_image&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'reference image required'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;reference_image&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="s1"&gt;'none'&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;reference_image&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'reference image not supported'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;key&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;model&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;prompt&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;duration&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;resolution&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;aspect_ratio&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;audio&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;reference_image&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'|'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="n"&gt;out&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;row_key&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;valid&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;length&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;reasons&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'; '&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;out&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For the duplicate check, compare &lt;code&gt;row_key&lt;/code&gt; (or a hash of it) against rows already marked &lt;code&gt;done&lt;/code&gt; before the IF node. For the batch cap, add a Code node on the valid branch that throws if &lt;code&gt;$input.all().length&lt;/code&gt; is above your limit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick test
&lt;/h2&gt;

&lt;p&gt;Make a five-row test sheet: one valid row per model, one row with an unknown model name, one with a duration the model does not support, and one exact copy of a valid row that is already marked &lt;code&gt;done&lt;/code&gt;. Run the workflow with the paid node disabled. You should see two rows on the valid branch, two rejected with clear reasons in the sheet, and one skipped as a duplicate. Only then enable the paid node.&lt;/p&gt;

&lt;h2&gt;
  
  
  Doing it in Make
&lt;/h2&gt;

&lt;p&gt;The same pattern works in Make: a Google Sheets "Search Rows" module, a Data Store holding the model rules, a router with filters per rule (or one "Set multiple variables" step that builds the reason string), and a filter so only rows with an empty reason reach the paid HTTP module. Rejected rows go to an "Update a Row" module. You can build it on the free plan: &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;Make free plan&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>automation</category>
      <category>ai</category>
      <category>workflow</category>
    </item>
    <item>
      <title>n8n Says Success, but the WhatsApp Message Never Arrived: Track Delivery with Status Webhooks (2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Fri, 13 Nov 2026 01:58:05 +0000</pubDate>
      <link>https://dev.to/vietautomation/n8n-says-success-but-the-whatsapp-message-never-arrived-track-delivery-with-status-webhooks-2026-45e4</link>
      <guid>https://dev.to/vietautomation/n8n-says-success-but-the-whatsapp-message-never-arrived-track-delivery-with-status-webhooks-2026-45e4</guid>
      <description>&lt;h1&gt;
  
  
  Why does n8n show success when the WhatsApp message never arrived?
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; the WhatsApp Cloud API answers your send request as soon as it accepts the message, so the n8n node goes green. Whether the message was actually delivered is reported later, in a separate status webhook (&lt;code&gt;sent&lt;/code&gt;, &lt;code&gt;delivered&lt;/code&gt;, &lt;code&gt;read&lt;/code&gt; or &lt;code&gt;failed&lt;/code&gt;). If your workflow never listens to that webhook, a failed message looks exactly like a successful one. Fix it by saving the message ID from every send, recording each status update against that ID, and alerting on &lt;code&gt;failed&lt;/code&gt; or on messages that stay stuck without &lt;code&gt;delivered&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;This came up repeatedly in r/n8n on 12 November 2026. One builder wrote that the WhatsApp node returns 200 and the execution is green, but the message fails a few seconds later and "the real error only shows up in the status webhook, which most flows ignore" (&lt;a href="https://www.reddit.com/r/n8n/comments/1xuajwy/n8n_showed_success_but_my_whatsapp_messages_never/" rel="noopener noreferrer"&gt;thread&lt;/a&gt;). The same day, another self-hoster described a lead workflow that quietly dropped leads for 30 hours and cost them their first client (&lt;a href="https://www.reddit.com/r/n8n/comments/1xujqlo/my_n8n_instance_quietly_dropped_leads_for_30/" rel="noopener noreferrer"&gt;thread&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  "Accepted" is not "delivered"
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What you see&lt;/th&gt;
&lt;th&gt;What it really means&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Green execution in n8n&lt;/td&gt;
&lt;td&gt;Every node ran without throwing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HTTP 200 and a message ID from the send call&lt;/td&gt;
&lt;td&gt;Meta accepted the request into its queue&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;sent&lt;/code&gt; status webhook&lt;/td&gt;
&lt;td&gt;Meta sent it toward the recipient&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;delivered&lt;/code&gt; status webhook&lt;/td&gt;
&lt;td&gt;It reached the recipient's device&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;failed&lt;/code&gt; status webhook&lt;/td&gt;
&lt;td&gt;It did not go out; the &lt;code&gt;errors&lt;/code&gt; field says why&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Common reasons a send is accepted and then fails: the 24-hour customer service window has closed and you sent free text instead of an approved template, the template was paused or rejected, the number is not on WhatsApp, or the account hit a messaging limit. None of these make the n8n node red.&lt;/p&gt;

&lt;p&gt;The same gap exists for email (accepted by the provider, then bounced) and SMS (queued, then undelivered). The pattern below works for all three.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pattern: log the ID, listen for status, reconcile
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Log every send.&lt;/strong&gt; Right after the WhatsApp node, write one row: message ID, recipient, workflow name, execution ID, &lt;code&gt;sent_at&lt;/code&gt;, and status &lt;code&gt;accepted&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Subscribe to status webhooks.&lt;/strong&gt; In your Meta app, point the WhatsApp webhook at an n8n Webhook trigger (verify the request signature before trusting it). Each payload under &lt;code&gt;statuses&lt;/code&gt; carries the message ID and the new status.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Update by message ID, never insert blindly.&lt;/strong&gt; Webhooks can arrive late, twice, or out of order. Only move a row forward (&lt;code&gt;accepted&lt;/code&gt; to &lt;code&gt;sent&lt;/code&gt; to &lt;code&gt;delivered&lt;/code&gt; to &lt;code&gt;read&lt;/code&gt;), and let &lt;code&gt;failed&lt;/code&gt; override anything, storing the error code and title.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Alert on two conditions.&lt;/strong&gt; A row turns &lt;code&gt;failed&lt;/code&gt;: alert immediately with the recipient and error. A row is still &lt;code&gt;accepted&lt;/code&gt; or &lt;code&gt;sent&lt;/code&gt; after a set time (for example 15 minutes for chat replies): alert once, because either delivery or your webhook is broken.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Close the loop for important messages.&lt;/strong&gt; For leads or invoices, a &lt;code&gt;failed&lt;/code&gt; row should create a follow-up task or fall back to email, not just ping Slack.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The table
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;CREATE&lt;/span&gt; &lt;span class="k"&gt;TABLE&lt;/span&gt; &lt;span class="k"&gt;IF&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="k"&gt;EXISTS&lt;/span&gt; &lt;span class="n"&gt;msg_delivery&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="n"&gt;message_id&lt;/span&gt;   &lt;span class="kt"&gt;TEXT&lt;/span&gt; &lt;span class="k"&gt;PRIMARY&lt;/span&gt; &lt;span class="k"&gt;KEY&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;channel&lt;/span&gt;      &lt;span class="kt"&gt;TEXT&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="kc"&gt;NULL&lt;/span&gt; &lt;span class="k"&gt;DEFAULT&lt;/span&gt; &lt;span class="s1"&gt;'whatsapp'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;recipient&lt;/span&gt;    &lt;span class="kt"&gt;TEXT&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="kc"&gt;NULL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;workflow&lt;/span&gt;     &lt;span class="kt"&gt;TEXT&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="kc"&gt;NULL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;execution_id&lt;/span&gt; &lt;span class="kt"&gt;TEXT&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;status&lt;/span&gt;       &lt;span class="kt"&gt;TEXT&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="kc"&gt;NULL&lt;/span&gt; &lt;span class="k"&gt;DEFAULT&lt;/span&gt; &lt;span class="s1"&gt;'accepted'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;error_code&lt;/span&gt;   &lt;span class="kt"&gt;TEXT&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;error_title&lt;/span&gt;  &lt;span class="kt"&gt;TEXT&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;sent_at&lt;/span&gt;      &lt;span class="kt"&gt;TIMESTAMPTZ&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="kc"&gt;NULL&lt;/span&gt; &lt;span class="k"&gt;DEFAULT&lt;/span&gt; &lt;span class="nb"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;updated_at&lt;/span&gt;   &lt;span class="kt"&gt;TIMESTAMPTZ&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="kc"&gt;NULL&lt;/span&gt; &lt;span class="k"&gt;DEFAULT&lt;/span&gt; &lt;span class="nb"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;alerted_at&lt;/span&gt;   &lt;span class="kt"&gt;TIMESTAMPTZ&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Forward-only status update from the webhook workflow:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;UPDATE&lt;/span&gt; &lt;span class="n"&gt;msg_delivery&lt;/span&gt;
&lt;span class="k"&gt;SET&lt;/span&gt; &lt;span class="n"&gt;status&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nv"&gt;$2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;error_code&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nv"&gt;$3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;error_title&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nv"&gt;$4&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;updated_at&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="n"&gt;message_id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nv"&gt;$1&lt;/span&gt;
  &lt;span class="k"&gt;AND&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="nv"&gt;$2&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'failed'&lt;/span&gt;
    &lt;span class="k"&gt;OR&lt;/span&gt; &lt;span class="nf"&gt;array_position&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;ARRAY&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'accepted'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="s1"&gt;'sent'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="s1"&gt;'delivered'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="s1"&gt;'read'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nv"&gt;$2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
       &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="nf"&gt;array_position&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;ARRAY&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'accepted'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="s1"&gt;'sent'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="s1"&gt;'delivered'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="s1"&gt;'read'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;status&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
  &lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Stuck-message check, run on a schedule, which claims each alert once:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;UPDATE&lt;/span&gt; &lt;span class="n"&gt;msg_delivery&lt;/span&gt;
&lt;span class="k"&gt;SET&lt;/span&gt; &lt;span class="n"&gt;alerted_at&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="n"&gt;alerted_at&lt;/span&gt; &lt;span class="k"&gt;IS&lt;/span&gt; &lt;span class="kc"&gt;NULL&lt;/span&gt;
  &lt;span class="k"&gt;AND&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;status&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'failed'&lt;/span&gt;
       &lt;span class="k"&gt;OR&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;status&lt;/span&gt; &lt;span class="k"&gt;IN&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'accepted'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="s1"&gt;'sent'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;AND&lt;/span&gt; &lt;span class="n"&gt;sent_at&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; &lt;span class="nb"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="kt"&gt;interval&lt;/span&gt; &lt;span class="s1"&gt;'15 minutes'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;RETURNING&lt;/span&gt; &lt;span class="n"&gt;message_id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;recipient&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;workflow&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;status&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;error_code&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;error_title&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Quick test
&lt;/h2&gt;

&lt;p&gt;Send a free-text message to a test number that has not messaged you in the last 24 hours. The n8n execution should still be green, and within a short time your table should show &lt;code&gt;failed&lt;/code&gt; with an error, and you should get exactly one alert. If you get nothing, your webhook is not wired up, and that is the problem this whole article is about.&lt;/p&gt;

&lt;h2&gt;
  
  
  How this fits with a heartbeat watchdog
&lt;/h2&gt;

&lt;p&gt;A heartbeat watchdog tells you the workflow ran and processed items. Delivery tracking tells you the last step actually reached a person. You want both: one catches "nothing happened", the other catches "something happened but nobody got it".&lt;/p&gt;

&lt;h2&gt;
  
  
  Doing it in Make
&lt;/h2&gt;

&lt;p&gt;The same pattern works in Make: a scenario sends the message and adds a row to a Data Store or Google Sheet, a second scenario with a custom webhook receives the WhatsApp status updates and updates the row, and a scheduled third one alerts on failed or stuck rows. You can build it on the free plan: &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;Make free plan&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>automation</category>
      <category>whatsapp</category>
      <category>monitoring</category>
    </item>
    <item>
      <title>How to Let AI Edit an Existing DOCX Without Breaking the Formatting (n8n &amp; Make, 2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Thu, 12 Nov 2026 01:56:14 +0000</pubDate>
      <link>https://dev.to/vietautomation/how-to-let-ai-edit-an-existing-docx-without-breaking-the-formatting-n8n-make-2026-mlc</link>
      <guid>https://dev.to/vietautomation/how-to-let-ai-edit-an-existing-docx-without-breaking-the-formatting-n8n-make-2026-mlc</guid>
      <description>&lt;h1&gt;
  
  
  How do you let AI edit an existing DOCX without breaking the formatting?
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; never ask the model to produce a new Word file. Ask it for a short list of changes, each tied to an exact place in the original (a paragraph, a table cell, a placeholder), apply those changes to the original file with a library that edits in place, and show a person a before-and-after view before the file is saved or sent.&lt;/p&gt;

&lt;p&gt;A recent r/AI_Agents thread asked exactly this: an agent updates a clause and a few table cells in an existing DOCX, so where does the human review happen, and how do you catch formatting changes, especially when the user has already made their own edits? (&lt;a href="https://www.reddit.com/r/AI_Agents/comments/1xtp8sq/how_are_you_letting_ai_edit_existing_docx_files/" rel="noopener noreferrer"&gt;thread&lt;/a&gt;)&lt;/p&gt;

&lt;h2&gt;
  
  
  Why AI edits break Word files
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A DOCX is a zip of XML. Text that looks like one sentence is often split across several "runs", each with its own font, bold or tracked-change markup.&lt;/li&gt;
&lt;li&gt;When a model regenerates the whole document from plain text, everything it did not see (styles, numbering, headers, comments, the user's own edits) is lost.&lt;/li&gt;
&lt;li&gt;Replacing a whole paragraph to change three words resets the formatting of the other words in it.&lt;/li&gt;
&lt;li&gt;Reviewers who only get a new file cannot see what changed, so they approve by trust.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The pattern: propose, locate, apply, review
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Extract, don't convert.&lt;/strong&gt; Read the document into a list of addressable pieces: paragraph number and text, table and cell position and text, and any placeholders such as &lt;code&gt;{{client_name}}&lt;/code&gt;. Keep the original file untouched.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ask the model for a change list, not a document.&lt;/strong&gt; Require JSON like &lt;code&gt;{location, old_text, new_text, reason}&lt;/code&gt;. &lt;code&gt;old_text&lt;/code&gt; must match the current text exactly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reject anything that does not match.&lt;/strong&gt; If &lt;code&gt;old_text&lt;/code&gt; is not found at that location, the user probably edited it since extraction. Skip the change and flag it; do not guess.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Apply changes at the smallest level possible.&lt;/strong&gt; Replace text inside the existing run where you can, so the surrounding formatting stays. For table cells, write into the existing cell rather than rebuilding the table.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Save as a new version, never over the original.&lt;/strong&gt; Keep both files, so a bad edit is one click to undo.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Show a redline before it goes anywhere.&lt;/strong&gt; Either write the changes as tracked changes, or produce a simple comparison (Word's own Compare feature works) and send it to the document owner for approval.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Where the human review fits
&lt;/h2&gt;

&lt;p&gt;Put the approval between step 5 and anything that sends, signs or publishes the file. The reviewer should see three things: the list of proposed changes with reasons, the redline, and any changes that were skipped because the text had moved. That last list is what catches the "user already edited it" case from the thread.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tools that fit this pattern
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Python (&lt;code&gt;python-docx&lt;/code&gt;)&lt;/strong&gt; in an n8n Code node or a small service can read paragraphs, runs and table cells and edit them in place.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Template engines&lt;/strong&gt; (for example docxtemplater in JavaScript) are a better fit when the document is a template you control: the AI fills placeholders and never touches layout.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google Docs&lt;/strong&gt; is easier if the team can work there: Make and n8n both have Google Docs modules that replace text in an existing document, and Docs keeps version history for you.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Quick test
&lt;/h2&gt;

&lt;p&gt;Take a contract where the user has bolded one word inside a clause, then ask the workflow to change a different word in the same clause. If the bold disappears, your apply step is replacing the whole paragraph instead of the run.&lt;/p&gt;

&lt;h2&gt;
  
  
  Doing it in Make
&lt;/h2&gt;

&lt;p&gt;A Make scenario can run the change list through an iterator, skip items whose old text does not match, and route the rest to a Google Docs "replace text" step and then an approval message, all without code. You can try it on the free plan: &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;Make free plan&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>automation</category>
      <category>ai</category>
      <category>n8n</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Which CRM Fields Should an AI Automation Never Write? A Simple Write Policy (n8n &amp; Make, 2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Wed, 11 Nov 2026 01:55:08 +0000</pubDate>
      <link>https://dev.to/vietautomation/which-crm-fields-should-an-ai-automation-never-write-a-simple-write-policy-n8n-make-2026-3eb0</link>
      <guid>https://dev.to/vietautomation/which-crm-fields-should-an-ai-automation-never-write-a-simple-write-policy-n8n-make-2026-3eb0</guid>
      <description>&lt;h1&gt;
  
  
  Which CRM fields should an AI automation never write?
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; give every CRM field one of three labels: the automation may write it directly, the automation may only suggest it for a person to approve, or the automation never touches it. Then enforce that list in one place in your workflow, not in the prompt.&lt;/p&gt;

&lt;p&gt;A recent thread in r/automation described the problem well: an AI notetaker wrote a kickoff date that a customer had only floated, and someone who was not on the call approved it. The question that followed was simple, which CRM fields would you never let an automation write?&lt;/p&gt;

&lt;h2&gt;
  
  
  Why AI updates go wrong in a CRM
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The model only sees the one call or email it is processing, so it can contradict what was agreed earlier.&lt;/li&gt;
&lt;li&gt;A "maybe next month" becomes a hard date, because the field only accepts a date.&lt;/li&gt;
&lt;li&gt;Approvers who were not in the conversation cannot tell a guess from a commitment, so they click approve.&lt;/li&gt;
&lt;li&gt;The bad value looks official once it is in the CRM, and other automations start using it.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The three-label write policy
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Label&lt;/th&gt;
&lt;th&gt;What it means&lt;/th&gt;
&lt;th&gt;Typical fields&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Auto-write&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Low risk, easy to verify, easy to undo&lt;/td&gt;
&lt;td&gt;Call logged, meeting date that already happened, contact's job title from their own signature, activity notes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Suggest only&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Useful, but a wrong value changes what people do&lt;/td&gt;
&lt;td&gt;Next step, close date, kickoff date, deal stage, product interest, budget mentioned&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Never&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Commitments, money, legal or ownership&lt;/td&gt;
&lt;td&gt;Contract value, discount, payment terms, deal owner, closed won or lost, consent and opt-out flags&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Adjust the table to your own CRM, but write it down. The list is the policy; the prompt is not.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to enforce it in about 30 minutes
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Keep the policy in one place.&lt;/strong&gt; A Set node in n8n, or a data store in Make, holding each field name and its label.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Make the AI return proposals, not updates.&lt;/strong&gt; Ask for JSON with the field, the proposed value, and a short quote from the source that supports it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Filter by label before writing.&lt;/strong&gt; Auto-write fields go straight to the CRM. Suggest-only fields go to a review list (a sheet, a Slack message or a CRM task). Never fields are dropped and logged.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Require the quote for every suggestion.&lt;/strong&gt; If the model cannot point to the exact words, the suggestion does not go to review. That alone removes most invented dates.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Send suggestions to the person who owns the deal,&lt;/strong&gt; not to whoever is free. The thread above is a good reminder of why.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Store who approved what.&lt;/strong&gt; Write the approver and the time into a note on the record, so later questions have an answer.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Quick test
&lt;/h2&gt;

&lt;p&gt;Feed the workflow a call transcript where the customer says "we might start in March, but nothing is confirmed." If the kickoff date field changes in the CRM without a review step, your filter is not wired correctly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where Make helps
&lt;/h2&gt;

&lt;p&gt;Make scenarios can route each proposed field through a router with a filter per label, which suits this pattern without code. You can try it on the free plan: &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;Make free plan&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>automation</category>
      <category>n8n</category>
      <category>crm</category>
      <category>ai</category>
    </item>
    <item>
      <title>How to Catch an AI Step That Breaks When a Model Gets Retired (n8n &amp; Make, 2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Tue, 10 Nov 2026 02:03:45 +0000</pubDate>
      <link>https://dev.to/vietautomation/how-to-catch-an-ai-step-that-breaks-when-a-model-gets-retired-n8n-make-2026-34j0</link>
      <guid>https://dev.to/vietautomation/how-to-catch-an-ai-step-that-breaks-when-a-model-gets-retired-n8n-make-2026-34j0</guid>
      <description>&lt;h1&gt;
  
  
  How to catch an AI step that breaks when a model gets retired
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; treat the model name like any other dependency. Keep it in one place, run a tiny daily test call against it, and alert a human when the call fails or the answer changes shape.&lt;/p&gt;

&lt;p&gt;Builders in automation communities keep asking how to notice this early, because the failure is often quiet: a step returns an error that a branch swallows, or a replacement model answers in a slightly different format and downstream steps carry on with bad data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it breaks
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Providers retire or rename models on their own schedule, and a workflow with the name typed into ten nodes fails in ten places.&lt;/li&gt;
&lt;li&gt;Some providers silently route an old alias to a newer model, so output style, length or JSON format can shift without any error.&lt;/li&gt;
&lt;li&gt;Error branches that "continue on fail" hide the problem until someone notices missing results.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A 20-minute pattern
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;One config node.&lt;/strong&gt; Store the model name once (a Set node in n8n, a data store or variable in Make) and reference it everywhere. Changing it is then a one-line edit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A daily canary.&lt;/strong&gt; A scheduled workflow sends one short fixed prompt and checks three things: the call succeeded, the reply is not empty, and it still parses into the structure your real workflows expect.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Alert on failure only.&lt;/strong&gt; If any check fails, send a message with the workflow name and the model name, never the prompt contents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Validate output in every AI workflow.&lt;/strong&gt; After the AI step, check required fields exist before writing anywhere. Route failures to a review list instead of continuing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep a fallback model&lt;/strong&gt; in the config node, and note the date you last tested it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Read provider deprecation notices&lt;/strong&gt; monthly and write the retirement dates next to the config entry.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Quick test
&lt;/h2&gt;

&lt;p&gt;Change the model name in your config node to a made-up value on a copy of your workflow. If you do not get an alert within a day, your canary is not wired correctly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where Make helps
&lt;/h2&gt;

&lt;p&gt;Make scenarios can run on a schedule with a built-in error handler route, which suits the daily canary and alert. You can try it on the free plan: &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;Make free plan&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>automation</category>
      <category>n8n</category>
      <category>ai</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>What to Keep Out of Your Automation Logs (n8n &amp; Make Redaction Checklist, 2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Mon, 09 Nov 2026 02:03:49 +0000</pubDate>
      <link>https://dev.to/vietautomation/what-to-keep-out-of-your-automation-logs-n8n-make-redaction-checklist-2026-3hbm</link>
      <guid>https://dev.to/vietautomation/what-to-keep-out-of-your-automation-logs-n8n-make-redaction-checklist-2026-3hbm</guid>
      <description>&lt;h1&gt;
  
  
  What to keep out of your automation logs
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; log &lt;em&gt;that&lt;/em&gt; something happened and &lt;em&gt;which record&lt;/em&gt; it touched, not the sensitive content itself. Execution history is useful for debugging, but it is also a second copy of your data that more people can read, export, and forget about.&lt;/p&gt;

&lt;p&gt;The question comes up regularly in automation communities ("what information do you deliberately keep out of your logs?"), and most builders only think about it after a log leaks something.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to keep out
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Category&lt;/th&gt;
&lt;th&gt;Why it is risky in logs&lt;/th&gt;
&lt;th&gt;What to log instead&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;API keys, tokens, auth headers&lt;/td&gt;
&lt;td&gt;Anyone with log access can reuse them&lt;/td&gt;
&lt;td&gt;Credential name only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Passwords, reset links, magic links&lt;/td&gt;
&lt;td&gt;Direct account takeover&lt;/td&gt;
&lt;td&gt;Nothing; just "link sent"&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Full email bodies and attachments&lt;/td&gt;
&lt;td&gt;Personal and business data copied everywhere&lt;/td&gt;
&lt;td&gt;Message id + subject hash&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Payment details, bank info&lt;/td&gt;
&lt;td&gt;Compliance exposure&lt;/td&gt;
&lt;td&gt;Last 4 digits or an order id&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Personal data (phone, address, ID numbers)&lt;/td&gt;
&lt;td&gt;Privacy law obligations&lt;/td&gt;
&lt;td&gt;Internal customer id&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Raw LLM prompts containing customer text&lt;/td&gt;
&lt;td&gt;Prompts quietly carry the data above&lt;/td&gt;
&lt;td&gt;Template name + record id&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  A 15-minute redaction pattern
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Add one "Log Safe" step&lt;/strong&gt; at the end of each branch (a Set / Code node in n8n, a Set variable module in Make) that builds a small object: &lt;code&gt;workflow&lt;/code&gt;, &lt;code&gt;record_id&lt;/code&gt;, &lt;code&gt;status&lt;/code&gt;, &lt;code&gt;timestamp&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Send only that object&lt;/strong&gt; to your log destination (sheet, database, Slack alert).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Turn down built-in retention.&lt;/strong&gt; In n8n, review the settings that control saving execution data for successful and failed runs, and how long old executions are pruned. In Make, review scenario history retention for your plan.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mask before alerting.&lt;/strong&gt; Error alerts to chat should name the workflow and record id, never paste the payload.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep secrets in credential stores,&lt;/strong&gt; not in node parameters or hard-coded in Code nodes where they show up in exports.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Quick test
&lt;/h2&gt;

&lt;p&gt;Pick your busiest workflow, open the last failed execution, and ask: if I pasted this screen into a public forum for help, what would I regret? Whatever you listed is what needs redacting.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where Make helps
&lt;/h2&gt;

&lt;p&gt;If your team prefers a visual scenario builder, Make lets you keep the log step as a single reusable module at the end of each route. You can start on the free plan: &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;Make free plan&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Redacting in the log node but not in the error path.&lt;/strong&gt; Error workflows often receive the full payload.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pinning real customer data while testing&lt;/strong&gt; and leaving it in the workflow.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sharing workflow exports&lt;/strong&gt; that still contain pinned data or hard-coded keys.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Assuming "internal" means safe.&lt;/strong&gt; Contractors, backups and screenshots all widen the audience.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Bottom line
&lt;/h2&gt;

&lt;p&gt;Log identifiers and outcomes, not content. A tiny "Log Safe" step per workflow costs minutes now and avoids a painful cleanup later.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>automation</category>
      <category>n8n</category>
      <category>security</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to Share n8n/Make Workflows With Coworkers Without Slack Archaeology (2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Sun, 08 Nov 2026 02:04:23 +0000</pubDate>
      <link>https://dev.to/vietautomation/how-to-share-n8nmake-workflows-with-coworkers-without-slack-archaeology-2026-2e9m</link>
      <guid>https://dev.to/vietautomation/how-to-share-n8nmake-workflows-with-coworkers-without-slack-archaeology-2026-2e9m</guid>
      <description>&lt;h1&gt;
  
  
  How to share what you built with coworkers (without Slack archaeology)
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; stop pasting screenshots into chat. Keep a one-row-per-workflow catalog, a one-page README next to each workflow, and a short "safe to share" checklist before anyone else presses Run. The sharing problem is usually discovery and trust, not file transfer.&lt;/p&gt;

&lt;p&gt;This is a common question in r/automation: builders have working automations and no clean way for teammates to find or reuse them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three pieces
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Piece&lt;/th&gt;
&lt;th&gt;Lives where&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Catalog&lt;/td&gt;
&lt;td&gt;Sheet / Notion / Airtable&lt;/td&gt;
&lt;td&gt;Searchable index: name, owner, trigger, systems touched, link, status&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;README&lt;/td&gt;
&lt;td&gt;Same folder / workflow sticky / doc page&lt;/td&gt;
&lt;td&gt;How to run, what it changes, how to stop it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Handoff check&lt;/td&gt;
&lt;td&gt;5-minute review&lt;/td&gt;
&lt;td&gt;Credentials, test mode, idempotency, who gets alerted&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  1. Catalog columns that actually get used
&lt;/h2&gt;

&lt;p&gt;Minimum useful columns:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Name&lt;/strong&gt; — human title, not the internal id.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Owner&lt;/strong&gt; — one person on the hook.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Trigger&lt;/strong&gt; — cron, webhook, form, manual.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Systems&lt;/strong&gt; — Gmail, Sheets, CRM, Slack, …&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Link&lt;/strong&gt; — n8n workflow URL, Make scenario URL, or repo path.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Status&lt;/strong&gt; — &lt;code&gt;draft&lt;/code&gt; / &lt;code&gt;pilot&lt;/code&gt; / &lt;code&gt;production&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Last verified&lt;/strong&gt; — date someone ran it successfully on purpose.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Anything else (ROI, screenshots, long essays) can wait. If the catalog is painful to update, people will ignore it.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. One-page README template
&lt;/h2&gt;

&lt;p&gt;Paste this into an n8n Sticky Note, a Make note, or a markdown file next to the export:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;# &amp;lt;Workflow name&amp;gt;
Owner: &amp;lt;name&amp;gt; | Status: draft|pilot|production
Trigger: &amp;lt;cron / webhook / manual&amp;gt;
What it changes: &amp;lt;list side effects&amp;gt;
What it does NOT do: &amp;lt;boundaries&amp;gt;
How to test safely: &amp;lt;test inbox / dry-run flag / sample sheet&amp;gt;
How to stop it: &amp;lt;deactivate / pause / kill switch&amp;gt;
Alerts go to: &amp;lt;channel or email&amp;gt;
Last verified: &amp;lt;YYYY-MM-DD&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If a coworker cannot answer "what does this change?" from that page alone, it is not shareable yet.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Safe-to-share checklist (before you hand over Run)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Credentials are team-owned (or clearly personal and not required for the demo).&lt;/li&gt;
&lt;li&gt;[ ] Side effects hit a &lt;strong&gt;test&lt;/strong&gt; inbox, sheet, or CRM sandbox first.&lt;/li&gt;
&lt;li&gt;[ ] Retries cannot double-create (idempotency key or "already exists" guard).&lt;/li&gt;
&lt;li&gt;[ ] There is an obvious off switch.&lt;/li&gt;
&lt;li&gt;[ ] Failure alerts go somewhere a human looks.&lt;/li&gt;
&lt;li&gt;[ ] Catalog row and README are updated the same day.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is the same reliability mindset as silent-failure watchdogs and approval queues — sharing multiplies mistakes unless those guards exist.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ways to share the actual workflow
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Method&lt;/th&gt;
&lt;th&gt;Good when&lt;/th&gt;
&lt;th&gt;Watch out for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Invite teammate into the same n8n/Make workspace&lt;/td&gt;
&lt;td&gt;Day-to-day ops&lt;/td&gt;
&lt;td&gt;Overwrite risk; use naming + status&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Export JSON / Make blueprint&lt;/td&gt;
&lt;td&gt;Handoff, backup, Git&lt;/td&gt;
&lt;td&gt;Secrets may be stripped or embedded — review before sending&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Screen recording + catalog link&lt;/td&gt;
&lt;td&gt;Training&lt;/td&gt;
&lt;td&gt;Goes stale; always pair with README&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Internal template gallery&lt;/td&gt;
&lt;td&gt;Agency with many repeats&lt;/td&gt;
&lt;td&gt;Needs an owner to curate or it rots&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;On n8n, inviting a teammate to a workflow is built in on Cloud (every plan) and on self-hosted Business or Enterprise (&lt;a href="https://docs.n8n.io/build/manage-workflows/share-with-others" rel="noopener noreferrer"&gt;n8n sharing docs&lt;/a&gt;). On Community self-hosted, &lt;a href="https://docs.n8n.io/build/manage-workflows/export-and-import" rel="noopener noreferrer"&gt;export the workflow as JSON&lt;/a&gt; or give them access to the same instance instead. Review exports before you send them: n8n's docs note that JSON can include credential names and IDs, and HTTP Request nodes may still carry auth headers from a cURL import.&lt;/p&gt;

&lt;h2&gt;
  
  
  A tiny "publish to catalog" automation
&lt;/h2&gt;

&lt;p&gt;When a workflow moves to &lt;code&gt;pilot&lt;/code&gt; or &lt;code&gt;production&lt;/code&gt;, have a button or short scenario that:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Reads name, owner, trigger, systems from a form or sticky fields.&lt;/li&gt;
&lt;li&gt;Upserts one row in the catalog (key = workflow id).&lt;/li&gt;
&lt;li&gt;Posts a short message to the team channel with the catalog link — not the full JSON.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You can build that button in n8n or in Make. If your team already thinks in visual scenarios, Make's free tier is enough for the catalog upsert + Slack notify path: &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;Make free plan&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common failure modes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Sharing the JSON and nothing else.&lt;/strong&gt; Teammates import it, it fails on missing credentials, and they never trust automation again.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One hero owns every production scenario.&lt;/strong&gt; Vacation = outage. Put a backup owner on the catalog row.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No status field.&lt;/strong&gt; People rerun &lt;code&gt;draft&lt;/code&gt; workflows against live customers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Catalog in six places.&lt;/strong&gt; Pick one source of truth.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Bottom line
&lt;/h2&gt;

&lt;p&gt;Coworkers do not need your entire brain dump. They need a searchable catalog, a one-page README, and proof the workflow is safe to touch. Build those three once; every new automation reuses the same pattern.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>automation</category>
      <category>n8n</category>
      <category>productivity</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Self-Hosted n8n Audit Trail: Who Changed What, When, and What Ran (2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Sat, 07 Nov 2026 02:01:47 +0000</pubDate>
      <link>https://dev.to/vietautomation/self-hosted-n8n-audit-trail-who-changed-what-when-and-what-ran-2026-boi</link>
      <guid>https://dev.to/vietautomation/self-hosted-n8n-audit-trail-who-changed-what-when-and-what-ran-2026-boi</guid>
      <description>&lt;h1&gt;
  
  
  Self-hosted n8n audit trail: who changed what, when, and what ran
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; treat audit as three append-only streams — workflow version snapshots, credential/user events, and production execution summaries — written to one Postgres table you control. Self-hosted n8n does not give you a polished compliance console out of the box; you build a thin logger that answers "who changed this workflow?" and "what did production actually send?" without guessing from chat history.&lt;/p&gt;

&lt;p&gt;This came up on r/n8n on 6 November 2026 ("How is a audit trail implemented in a self hosted setup", 11 comments): operators need a paper trail for edits and runs, not another dashboard toy.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "audit trail" means here
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Stream&lt;/th&gt;
&lt;th&gt;Question it answers&lt;/th&gt;
&lt;th&gt;Source&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Workflow versions&lt;/td&gt;
&lt;td&gt;Who edited which workflow, and what did it look like before?&lt;/td&gt;
&lt;td&gt;Export / webhook on save, or periodic snapshot&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Access events&lt;/td&gt;
&lt;td&gt;Who logged in, who touched credentials, who activated a workflow?&lt;/td&gt;
&lt;td&gt;n8n DB tables + reverse proxy auth logs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Execution summaries&lt;/td&gt;
&lt;td&gt;What ran in production, with how many items, success or fail?&lt;/td&gt;
&lt;td&gt;n8n execution data or a heartbeat node&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;You do &lt;strong&gt;not&lt;/strong&gt; need to store full input payloads of every customer email. Store identifiers, counts, hashes, and status. Keep PII out of the audit table unless you have a documented reason and retention policy.&lt;/p&gt;

&lt;h2&gt;
  
  
  One table that stays readable
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;CREATE&lt;/span&gt; &lt;span class="k"&gt;TABLE&lt;/span&gt; &lt;span class="n"&gt;IF&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="k"&gt;EXISTS&lt;/span&gt; &lt;span class="n"&gt;n8n_audit_events&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="n"&gt;id&lt;/span&gt;            &lt;span class="n"&gt;BIGSERIAL&lt;/span&gt; &lt;span class="k"&gt;PRIMARY&lt;/span&gt; &lt;span class="k"&gt;KEY&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;seen_at&lt;/span&gt;       &lt;span class="n"&gt;TIMESTAMPTZ&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="k"&gt;NULL&lt;/span&gt; &lt;span class="k"&gt;DEFAULT&lt;/span&gt; &lt;span class="n"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(),&lt;/span&gt;
  &lt;span class="n"&gt;event_type&lt;/span&gt;    &lt;span class="nb"&gt;TEXT&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="k"&gt;NULL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;          &lt;span class="c1"&gt;-- workflow_version | access | execution&lt;/span&gt;
  &lt;span class="n"&gt;actor&lt;/span&gt;         &lt;span class="nb"&gt;TEXT&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;                   &lt;span class="c1"&gt;-- user email / system / 'cron'&lt;/span&gt;
  &lt;span class="n"&gt;workflow_id&lt;/span&gt;   &lt;span class="nb"&gt;TEXT&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;workflow_name&lt;/span&gt; &lt;span class="nb"&gt;TEXT&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;resource&lt;/span&gt;      &lt;span class="nb"&gt;TEXT&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;                   &lt;span class="c1"&gt;-- credential id, path, etc.&lt;/span&gt;
  &lt;span class="n"&gt;summary&lt;/span&gt;       &lt;span class="nb"&gt;TEXT&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="k"&gt;NULL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;          &lt;span class="c1"&gt;-- one-line human readable&lt;/span&gt;
  &lt;span class="n"&gt;content_hash&lt;/span&gt;  &lt;span class="nb"&gt;TEXT&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;                   &lt;span class="c1"&gt;-- sha256 of workflow JSON or payload fingerprint&lt;/span&gt;
  &lt;span class="n"&gt;meta&lt;/span&gt;          &lt;span class="n"&gt;JSONB&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="k"&gt;NULL&lt;/span&gt; &lt;span class="k"&gt;DEFAULT&lt;/span&gt; &lt;span class="s1"&gt;'{}'&lt;/span&gt;&lt;span class="p"&gt;::&lt;/span&gt;&lt;span class="n"&gt;jsonb&lt;/span&gt;
&lt;span class="p"&gt;);&lt;/span&gt;

&lt;span class="k"&gt;CREATE&lt;/span&gt; &lt;span class="k"&gt;INDEX&lt;/span&gt; &lt;span class="n"&gt;IF&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="k"&gt;EXISTS&lt;/span&gt; &lt;span class="n"&gt;n8n_audit_seen_at_idx&lt;/span&gt; &lt;span class="k"&gt;ON&lt;/span&gt; &lt;span class="n"&gt;n8n_audit_events&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;seen_at&lt;/span&gt; &lt;span class="k"&gt;DESC&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="k"&gt;CREATE&lt;/span&gt; &lt;span class="k"&gt;INDEX&lt;/span&gt; &lt;span class="n"&gt;IF&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="k"&gt;EXISTS&lt;/span&gt; &lt;span class="n"&gt;n8n_audit_workflow_idx&lt;/span&gt; &lt;span class="k"&gt;ON&lt;/span&gt; &lt;span class="n"&gt;n8n_audit_events&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;workflow_id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;seen_at&lt;/span&gt; &lt;span class="k"&gt;DESC&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Append only. No &lt;code&gt;UPDATE&lt;/code&gt; of old rows. If something was wrong, write a compensating event.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stream 1: workflow versions on every meaningful save
&lt;/h2&gt;

&lt;p&gt;Options that work on self-hosted setups:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Scheduled export.&lt;/strong&gt; Every N minutes, pull workflow JSON from the n8n API, hash it, and insert a &lt;code&gt;workflow_version&lt;/code&gt; row only when the hash changed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Git backup.&lt;/strong&gt; Many teams already dump workflows to a private repo. Treat each commit as the audit record; still mirror a one-line summary into Postgres so non-git users can query it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Manual "publish" workflow.&lt;/strong&gt; Editors click a button that posts the current workflow JSON to an audit webhook before activating.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The important part is the hash: two saves with the same hash are noise; a new hash is a real change.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;summary example:
  workflow_version | alice@agency.com | lead-sync | hash=ab12… | nodes=14→16
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Stream 2: access and credential events
&lt;/h2&gt;

&lt;p&gt;Self-hosted n8n stores users and credentials in its own database. For a first version:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Log &lt;strong&gt;activations / deactivations&lt;/strong&gt; of workflows (who turned production on).&lt;/li&gt;
&lt;li&gt;Log &lt;strong&gt;credential create/update&lt;/strong&gt; events if you can read them from the DB or admin API — never log the secret itself, only the credential id and name.&lt;/li&gt;
&lt;li&gt;Put SSO or reverse-proxy auth in front of the editor UI and ship those login logs to the same table as &lt;code&gt;access&lt;/code&gt; events.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you cannot hook the DB yet, start with activations + versions. That already answers most "who broke prod?" questions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stream 3: production execution summaries
&lt;/h2&gt;

&lt;p&gt;Reuse the same idea as a silent-failure watchdog: at the end of each critical workflow, POST a small heartbeat:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"event_type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"execution"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"workflow_id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"lead-sync"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"workflow_name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Lead sync"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"actor"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"system"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"summary"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"execution ok items=42"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"content_hash"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"exec:2026-11-06T01:00:00Z:42:ok"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"meta"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"items"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;42&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"status"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"ok"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"execution_id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"12345"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Do &lt;strong&gt;not&lt;/strong&gt; dump the full items array into &lt;code&gt;meta&lt;/code&gt;. Keep counts, ids, and status.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to query it when something goes wrong
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="c1"&gt;-- Last 20 changes to one workflow&lt;/span&gt;
&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="n"&gt;seen_at&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;actor&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;event_type&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;summary&lt;/span&gt;
&lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="n"&gt;n8n_audit_events&lt;/span&gt;
&lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="n"&gt;workflow_id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'lead-sync'&lt;/span&gt;
&lt;span class="k"&gt;ORDER&lt;/span&gt; &lt;span class="k"&gt;BY&lt;/span&gt; &lt;span class="n"&gt;seen_at&lt;/span&gt; &lt;span class="k"&gt;DESC&lt;/span&gt;
&lt;span class="k"&gt;LIMIT&lt;/span&gt; &lt;span class="mi"&gt;20&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="c1"&gt;-- Everything Alice touched today&lt;/span&gt;
&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="n"&gt;seen_at&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;event_type&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;workflow_name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;summary&lt;/span&gt;
&lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="n"&gt;n8n_audit_events&lt;/span&gt;
&lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="n"&gt;actor&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'alice@agency.com'&lt;/span&gt;
  &lt;span class="k"&gt;AND&lt;/span&gt; &lt;span class="n"&gt;seen_at&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="n"&gt;date_trunc&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'day'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;now&lt;/span&gt;&lt;span class="p"&gt;())&lt;/span&gt;
&lt;span class="k"&gt;ORDER&lt;/span&gt; &lt;span class="k"&gt;BY&lt;/span&gt; &lt;span class="n"&gt;seen_at&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Common mistakes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Logging secrets.&lt;/strong&gt; Credential values, API keys, and raw email bodies do not belong in audit storage.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Updating instead of appending.&lt;/strong&gt; An audit row is a fact about the past; correct it with a new row.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Only logging errors.&lt;/strong&gt; Successful production runs matter when a customer asks "did you send that on Tuesday?"&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No retention policy.&lt;/strong&gt; Keep enough history for your contracts (often 90–180 days), then archive or delete on a schedule.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  n8n or Make?
&lt;/h2&gt;

&lt;p&gt;If you already self-host n8n, keep the audit writer as a small n8n workflow (webhook + Postgres). If a teammate prefers a visual router for the alert/digest side — daily email of "workflows changed yesterday" — Make can subscribe to the same webhook and format the digest: &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;Make free plan&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this does not replace
&lt;/h2&gt;

&lt;p&gt;SOC2 evidence packs, legal holds, and full SIEM correlation. This pattern is the minimum useful trail for a small team running self-hosted automation: enough to reconstruct edits and production runs without pretending you bought an enterprise compliance suite.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>automation</category>
      <category>security</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Stop Chasing Freelancers for Hours: An End-of-Month Timesheet Collection Workflow (n8n or Make, 2026)</title>
      <dc:creator>Viet Automation</dc:creator>
      <pubDate>Fri, 06 Nov 2026 02:04:53 +0000</pubDate>
      <link>https://dev.to/vietautomation/stop-chasing-freelancers-for-hours-an-end-of-month-timesheet-collection-workflow-n8n-or-make-5g5a</link>
      <guid>https://dev.to/vietautomation/stop-chasing-freelancers-for-hours-an-end-of-month-timesheet-collection-workflow-n8n-or-make-5g5a</guid>
      <description>&lt;h1&gt;
  
  
  Stop chasing freelancers for hours at the end of the month
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; don't automate "send the timesheet to accounting". Automate the four steps around it: pull the hours, find who is missing or odd, nudge only those people, and hold everything for one human approval before a single, de-duplicated push to accounting. Most of the pain is the chasing, not the copying.&lt;/p&gt;

&lt;p&gt;This came up on r/automation on 4 November 2026 ("How do you automate your end-of-month timesheet reporting?"), where the poster pulls hours from a time tracker into accounting with Zapier and still ends up chasing people. Here is a tool-neutral pattern you can build in n8n, Make or Zapier.&lt;/p&gt;

&lt;h2&gt;
  
  
  The workflow in five steps
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Step&lt;/th&gt;
&lt;th&gt;Trigger / node&lt;/th&gt;
&lt;th&gt;What it does&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1. Roster&lt;/td&gt;
&lt;td&gt;Sheet or database&lt;/td&gt;
&lt;td&gt;One row per person: name, email, tracker user ID, expected hours, rate, approver&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2. Pull&lt;/td&gt;
&lt;td&gt;Schedule (e.g. 2 working days before month end)&lt;/td&gt;
&lt;td&gt;Read each person's logged hours for the period from the tracker's API or export&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3. Check&lt;/td&gt;
&lt;td&gt;Code / filter&lt;/td&gt;
&lt;td&gt;Flag people with 0 hours, hours far from expected, or entries still running&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4. Nudge&lt;/td&gt;
&lt;td&gt;Email / Slack / Telegram&lt;/td&gt;
&lt;td&gt;Message only the flagged people, with their current total and a deadline&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5. Approve and push&lt;/td&gt;
&lt;td&gt;Approval step, then accounting&lt;/td&gt;
&lt;td&gt;After a human approves, send one invoice or bill per person, keyed so it can't be created twice&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Step 3: the check is where the value is
&lt;/h2&gt;

&lt;p&gt;A useful first version flags only three things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Missing:&lt;/strong&gt; no hours logged for the period.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Out of range:&lt;/strong&gt; logged hours differ from expected by more than a threshold you choose (for example 20%).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Open entries:&lt;/strong&gt; a timer that was never stopped, which inflates totals.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Everyone else goes straight to the approval list. That way the reminder email reaches the two or three people who need it, not the whole team.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: nudges that people actually answer
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Send it from a real person's address or channel, not a no-reply.&lt;/li&gt;
&lt;li&gt;Include their current number: "You have 96.5 hours logged for October. Please fix or confirm by Friday 12:00."&lt;/li&gt;
&lt;li&gt;Re-run steps 2 and 3 before each reminder so people who already fixed it don't get pinged again.&lt;/li&gt;
&lt;li&gt;Cap reminders (two is usually enough) and escalate the rest to the approver.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 5: approve once, push once
&lt;/h2&gt;

&lt;p&gt;Accounting is the side effect you can't undo, so treat it carefully:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Write the final totals to an "approval" sheet or table with a status column.&lt;/li&gt;
&lt;li&gt;A manager marks each row approved (or approves the whole batch).&lt;/li&gt;
&lt;li&gt;The push step only reads approved rows and builds a key such as &lt;code&gt;timesheet:2026-10:&amp;lt;person_id&amp;gt;&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Before creating the bill or invoice, check that key in a small table or data store. If it exists, skip.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This is the same idempotency idea from our earlier post on safe retries: a retried run, or someone clicking "run" twice, must not create two bills.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Pulling on the last day.&lt;/strong&gt; Run the first pull a couple of working days early so there is time to fix gaps.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rounding before summing.&lt;/strong&gt; Sum raw durations, then round once.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Time zones.&lt;/strong&gt; Define the period in one time zone; a remote worker's late-night entry can land in the wrong month otherwise.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No audit trail.&lt;/strong&gt; Keep the approved snapshot. If a number is disputed later, you need what was approved, not what the tracker says today.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  n8n or Make?
&lt;/h2&gt;

&lt;p&gt;Both handle this well. n8n is a good fit if you already self-host and like writing the check step in a Code node. Make's scheduler, routers and Data Store cover the same steps without code; you can try it on the free plan here: &lt;a href="https://www.make.com/en/register?pc=vietautomation" rel="noopener noreferrer"&gt;Make free plan&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

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