<?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: Lantern Flows</title>
    <description>The latest articles on DEV Community by Lantern Flows (@lanternflows).</description>
    <link>https://dev.to/lanternflows</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%2F4219970%2F2d5d791d-9ed0-498e-b17f-0b2dfdb5b0d1.png</url>
      <title>DEV Community: Lantern Flows</title>
      <link>https://dev.to/lanternflows</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lanternflows"/>
    <language>en</language>
    <item>
      <title>Two MV3 errors you hit right after bumping manifest_version (and the fix)</title>
      <dc:creator>Lantern Flows</dc:creator>
      <pubDate>Sat, 07 Nov 2026 04:05:43 +0000</pubDate>
      <link>https://dev.to/lanternflows/two-mv3-errors-you-hit-right-after-bumping-manifestversion-and-the-fix-2p5e</link>
      <guid>https://dev.to/lanternflows/two-mv3-errors-you-hit-right-after-bumping-manifestversion-and-the-fix-2p5e</guid>
      <description>&lt;p&gt;You change &lt;code&gt;"manifest_version": 2&lt;/code&gt; to &lt;code&gt;3&lt;/code&gt; and the extension breaks. Two errors show up a lot:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Service worker registration failed&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;chrome.browserAction is undefined&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Below is a small &lt;strong&gt;made-up teaching example&lt;/strong&gt; (a tab counter), not a real project or client case. It is a partial migration, checked by reading the files only; it was &lt;strong&gt;not run in a browser&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The background page has to become a service worker
&lt;/h2&gt;

&lt;p&gt;MV2 (before):&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="nl"&gt;"background"&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;"scripts"&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="s2"&gt;"background.js"&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"persistent"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="err"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="nl"&gt;"browser_action"&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;"default_title"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Tab count"&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;MV3 (after):&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="nl"&gt;"background"&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;"service_worker"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"background.js"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="err"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="nl"&gt;"action"&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;"default_title"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Tab count"&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;MV3 has no persistent background pages. &lt;code&gt;browser_action&lt;/code&gt; was renamed &lt;code&gt;action&lt;/code&gt;, and &lt;code&gt;chrome.browserAction&lt;/code&gt; became &lt;code&gt;chrome.action&lt;/code&gt; in code.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Don't keep state in a global variable
&lt;/h2&gt;

&lt;p&gt;Before:&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;let&lt;/span&gt; &lt;span class="nx"&gt;count&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="c1"&gt;// in-memory state: lost when an MV3 worker stops&lt;/span&gt;
&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;refresh&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;chrome&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;tabs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;query&lt;/span&gt;&lt;span class="p"&gt;({},&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;tabs&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nx"&gt;count&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;tabs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="nx"&gt;chrome&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;browserAction&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;setBadgeText&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;String&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;count&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="nx"&gt;chrome&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;tabs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;onCreated&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addListener&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;refresh&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="nx"&gt;chrome&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;tabs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;onRemoved&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addListener&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;refresh&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="nf"&gt;refresh&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The service worker is stopped when idle, so &lt;code&gt;count&lt;/code&gt; is lost. After:&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="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;refresh&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="nx"&gt;tabs&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;chrome&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;tabs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;query&lt;/span&gt;&lt;span class="p"&gt;({});&lt;/span&gt;
  &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;chrome&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;action&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;setBadgeText&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;String&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;tabs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&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="nx"&gt;chrome&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;tabs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;onCreated&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addListener&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;refresh&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="nx"&gt;chrome&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;tabs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;onRemoved&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addListener&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;refresh&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="nx"&gt;chrome&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;runtime&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;onStartup&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addListener&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;refresh&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="nx"&gt;chrome&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;runtime&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;onInstalled&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addListener&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;refresh&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;What changed:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Change&lt;/th&gt;
&lt;th&gt;Before (MV2)&lt;/th&gt;
&lt;th&gt;After (MV3)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Background&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;scripts&lt;/code&gt; + &lt;code&gt;persistent: true&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;&lt;code&gt;service_worker&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Toolbar API&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;browser_action&lt;/code&gt; / &lt;code&gt;chrome.browserAction&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;action&lt;/code&gt; / &lt;code&gt;chrome.action&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;State&lt;/td&gt;
&lt;td&gt;global &lt;code&gt;count&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;recomputed on each event&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Callbacks&lt;/td&gt;
&lt;td&gt;&lt;code&gt;tabs.query(cb)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;await tabs.query()&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Startup&lt;/td&gt;
&lt;td&gt;top-level &lt;code&gt;refresh()&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;onStartup&lt;/code&gt; / &lt;code&gt;onInstalled&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Listeners stay registered at the top level so they are there whenever the worker restarts.&lt;/p&gt;

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

&lt;p&gt;Content scripts, &lt;code&gt;webRequest&lt;/code&gt; → &lt;code&gt;declarativeNetRequest&lt;/code&gt;, removing remote code, splitting &lt;code&gt;host_permissions&lt;/code&gt;, options pages, and Chrome Web Store review. Each one is a separate job. Check the official Chrome MV3 migration guide before relying on this.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: this article was generated by AI from a synthetic teaching example. It was first published on Hashnode.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>webdev</category>
      <category>extensions</category>
    </item>
    <item>
      <title>Why your n8n Gmail Trigger is not working (and how to fix it)</title>
      <dc:creator>Lantern Flows</dc:creator>
      <pubDate>Tue, 03 Nov 2026 01:45:07 +0000</pubDate>
      <link>https://dev.to/lanternflows/why-your-n8n-gmail-trigger-is-not-working-and-how-to-fix-it-1m60</link>
      <guid>https://dev.to/lanternflows/why-your-n8n-gmail-trigger-is-not-working-and-how-to-fix-it-1m60</guid>
      <description>&lt;p&gt;You connected Gmail. The node is green in the editor. Then production stays quiet—or every poll returns nothing—while new mail sits in the inbox. Searches for &lt;em&gt;n8n gmail trigger not working&lt;/em&gt; usually surface docs and forum threads. Here is a single checklist aimed at self-hosted n8n.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Scope of this article:&lt;/strong&gt; documented against &lt;strong&gt;self-hosted n8n 2.44.6&lt;/strong&gt;. &lt;strong&gt;Not tested on n8n Cloud.&lt;/strong&gt; Notification examples use &lt;strong&gt;Slack&lt;/strong&gt; or &lt;strong&gt;SMTP&lt;/strong&gt; only.&lt;/p&gt;

&lt;h3&gt;
  
  
  What the Gmail Trigger actually does
&lt;/h3&gt;

&lt;p&gt;The &lt;strong&gt;Gmail Trigger&lt;/strong&gt; polls Gmail on an interval (often about every minute by default, depending on your Poll Times). Each successful poll should only return &lt;strong&gt;new&lt;/strong&gt; messages that match your filters. It is not a push webhook from Google unless you deliberately use a different push-style setup.&lt;/p&gt;

&lt;p&gt;So “not working” usually means one of: workflow inactive, OAuth broken, filters too tight, poll never running in production, or you only tested with &lt;strong&gt;Execute workflow&lt;/strong&gt; in the editor.&lt;/p&gt;

&lt;h3&gt;
  
  
  Checklist: why Gmail Trigger stays quiet
&lt;/h3&gt;

&lt;p&gt;Work top to bottom.&lt;/p&gt;

&lt;h4&gt;
  
  
  1. Workflow not published / not active
&lt;/h4&gt;

&lt;p&gt;Triggers that poll on a schedule need a &lt;strong&gt;published&lt;/strong&gt; workflow. Draft-only saves do not keep listening in production.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; publish / activate. Confirm the workflow is active. Watch &lt;strong&gt;Executions&lt;/strong&gt; after the next poll window.&lt;/p&gt;

&lt;h4&gt;
  
  
  2. OAuth / Google Cloud client (self-hosted classic)
&lt;/h4&gt;

&lt;p&gt;Self-hosted n8n needs your own Google Cloud OAuth client with the Gmail API enabled, redirect URI copied from the n8n credential dialog, and a completed &lt;strong&gt;Sign in with Google&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Common breaks:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Redirect URI mismatch
&lt;/li&gt;
&lt;li&gt;Gmail API not enabled on the GCP project
&lt;/li&gt;
&lt;li&gt;App in &lt;strong&gt;Testing&lt;/strong&gt; with an expired test-user grant (Google often forces reconnect about every 7 days in Testing)
&lt;/li&gt;
&lt;li&gt;Wrong Google account authorized (personal vs Workspace)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; open the credential → reconnect. Confirm the same Google user owns the inbox you are watching. Re-check redirect URI character-for-character.&lt;/p&gt;

&lt;h4&gt;
  
  
  3. You only ran a manual test in the editor
&lt;/h4&gt;

&lt;p&gt;Clicking &lt;strong&gt;Execute workflow&lt;/strong&gt; can exercise downstream nodes with pinned or sample data without proving the &lt;strong&gt;trigger poll&lt;/strong&gt; path. A green canvas after a manual run does not mean the trigger is polling.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; publish, wait at least one full poll interval, send yourself a matching test email, then inspect &lt;strong&gt;Executions&lt;/strong&gt; for a production run that started from the Gmail Trigger.&lt;/p&gt;

&lt;h4&gt;
  
  
  4. Filters and labels exclude the message
&lt;/h4&gt;

&lt;p&gt;Search filters, label filters, “unread only,” spam/trash exclusions, or a filter aimed at the wrong mailbox will yield &lt;strong&gt;successful polls with zero items&lt;/strong&gt;. That looks identical to “not triggering” from outside.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; temporarily loosen filters. Confirm the test message is in the primary inbox (or the exact label you filter on). Remember: simple mode often exposes a &lt;strong&gt;snippet / preview&lt;/strong&gt;, not the full body—filters that expect full-body text can miss.&lt;/p&gt;

&lt;h4&gt;
  
  
  5. Poll Times / missed window / rate limits
&lt;/h4&gt;

&lt;p&gt;If Poll Times are very sparse, you may be waiting longer than you think. If Google returns errors (quota, invalid_grant), the execution list shows failures—open them instead of assuming silence means “no mail.”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; read the error text on failed executions. For &lt;code&gt;invalid_grant&lt;/code&gt;, reconnect OAuth. For quota, slow the poll or reduce parallel Gmail workflows.&lt;/p&gt;

&lt;h4&gt;
  
  
  6. Downstream nodes fail (false “trigger broken”)
&lt;/h4&gt;

&lt;p&gt;The trigger may have returned messages, then a label / Slack / LLM node failed. From Slack’s point of view “nothing happened.”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; open the execution graph. If Gmail Trigger has items and a later node is red, fix that node (Slack invite/scopes, missing label IDs, LLM key)—not the trigger credential.&lt;/p&gt;

&lt;h4&gt;
  
  
  7. Empty / no-preview messages
&lt;/h4&gt;

&lt;p&gt;Some triage workflows intentionally &lt;strong&gt;skip&lt;/strong&gt; messages with empty preview text before any AI call. Those runs can look “idle” even though the trigger fired.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; know whether your workflow has a “has content?” gate. Test with a normal plain-text email that has a non-empty snippet.&lt;/p&gt;

&lt;h3&gt;
  
  
  Minimal documented pattern (inbox triage shape)
&lt;/h3&gt;

&lt;p&gt;A common production shape:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Gmail Trigger&lt;/strong&gt; (poll) with credentials fixed.
&lt;/li&gt;
&lt;li&gt;Normalize sender / subject / preview.
&lt;/li&gt;
&lt;li&gt;Optional empty-content skip.
&lt;/li&gt;
&lt;li&gt;Classify (rules and/or LLM).
&lt;/li&gt;
&lt;li&gt;Apply Gmail labels; optional &lt;strong&gt;Slack&lt;/strong&gt; urgent alert.
&lt;/li&gt;
&lt;li&gt;Publish; verify with a real test email in production mode.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Documented against self-hosted n8n &lt;strong&gt;2.44.6&lt;/strong&gt;; not tested on n8n Cloud. Real Gmail OAuth, labels, Slack, and LLM quality still need verification in &lt;em&gt;your&lt;/em&gt; Google project and workspace.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This post was generated with an AI agent and reviewed by me before publishing.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>gmail</category>
      <category>automation</category>
      <category>google</category>
    </item>
    <item>
      <title>Why your n8n RSS Feed Trigger is not working (checklist)</title>
      <dc:creator>Lantern Flows</dc:creator>
      <pubDate>Mon, 02 Nov 2026 01:43:40 +0000</pubDate>
      <link>https://dev.to/lanternflows/why-your-n8n-rss-feed-trigger-is-not-working-checklist-1jkd</link>
      <guid>https://dev.to/lanternflows/why-your-n8n-rss-feed-trigger-is-not-working-checklist-1jkd</guid>
      <description>&lt;p&gt;You scheduled an RSS → digest workflow. The canvas looks fine. Then… nothing. No new execution. Or the run completes with zero items. Searches for &lt;em&gt;n8n rss feed trigger not working&lt;/em&gt; often land on docs and forum threads, so here is one checklist you can finish in about fifteen minutes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Scope of this article:&lt;/strong&gt; documented against &lt;strong&gt;self-hosted n8n 2.44.6&lt;/strong&gt;. &lt;strong&gt;Not tested on n8n Cloud.&lt;/strong&gt; When this article mentions alerts or digests, delivery examples use &lt;strong&gt;SMTP&lt;/strong&gt; or &lt;strong&gt;Slack&lt;/strong&gt;—not Telegram/Discord.&lt;/p&gt;

&lt;h3&gt;
  
  
  What “RSS Trigger” usually means in practice
&lt;/h3&gt;

&lt;p&gt;In many setups people mean either:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;RSS Feed Read&lt;/strong&gt; (or similar read node) on a &lt;strong&gt;Schedule&lt;/strong&gt; / Cron, or
&lt;/li&gt;
&lt;li&gt;An RSS / feed &lt;strong&gt;Trigger&lt;/strong&gt; node that polls on its own interval.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Both fail for similar reasons: bad URL, inactive workflow, empty window, or “success with zero items.” Treat “not working” as &lt;em&gt;no useful items reached the next node&lt;/em&gt;, not only a red error banner.&lt;/p&gt;

&lt;h3&gt;
  
  
  Checklist: why the feed path is silent
&lt;/h3&gt;

&lt;p&gt;Work top to bottom.&lt;/p&gt;

&lt;h4&gt;
  
  
  1. The workflow is not published / active
&lt;/h4&gt;

&lt;p&gt;Schedule and poll triggers only run in &lt;strong&gt;production&lt;/strong&gt; on a &lt;strong&gt;published&lt;/strong&gt; (activated) workflow. A manual &lt;strong&gt;Execute workflow&lt;/strong&gt; click in the editor does not prove the schedule will fire overnight.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; publish the workflow. Confirm it shows as active. Wait for the next poll window, then check &lt;strong&gt;Executions&lt;/strong&gt;—not only the editor toast.&lt;/p&gt;

&lt;h4&gt;
  
  
  2. You are testing with a feed URL that does not return items
&lt;/h4&gt;

&lt;p&gt;Broken HTTPS, 403 from the publisher, HTML login pages, Atom vs RSS mismatch, or a URL that used to work and now redirects can all look like “trigger not working.”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; open the feed URL in a browser or &lt;code&gt;curl&lt;/code&gt;. You should see XML (or a known feed format), not an empty 200 HTML page. Temporarily put a well-known public feed in Config, publish, and re-test. Put your real feeds back only after the path works.&lt;/p&gt;

&lt;h4&gt;
  
  
  3. Polling / schedule interval vs your expectations
&lt;/h4&gt;

&lt;p&gt;If the schedule is “every day at 08:00” and you tested at 08:05 in the editor, you did not exercise the schedule. If a trigger polls every &lt;em&gt;N&lt;/em&gt; minutes, the first production wait can be a full interval.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; use a &lt;strong&gt;Manual Trigger&lt;/strong&gt; “Run now” path (if your workflow has one) for import checks; keep the schedule for production. Align timezone on the n8n instance with the schedule you wrote.&lt;/p&gt;

&lt;h4&gt;
  
  
  4. Filters discarded everything (looks like “not working”)
&lt;/h4&gt;

&lt;p&gt;Common silent filters:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Last N hours only&lt;/strong&gt; (e.g. last 24h) when the feed’s &lt;code&gt;pubDate&lt;/code&gt; is older or missing
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Remove duplicates / already sent&lt;/strong&gt; on a second run (correct behaviour: nothing new → no email)
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Limit / cap&lt;/strong&gt; after an empty upstream
&lt;/li&gt;
&lt;li&gt;Continue-on-error on Read RSS: one bad feed is skipped; if &lt;em&gt;all&lt;/em&gt; feeds fail, you get zero items and no digest&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; on a test run, inspect each node’s output item count. Temporarily widen the lookback or clear the duplicate store for a controlled re-test. Do not treat “second run sent nothing” as a broken trigger if the first run already consumed those links.&lt;/p&gt;

&lt;h4&gt;
  
  
  5. Credentials and downstream SMTP (false “trigger” reports)
&lt;/h4&gt;

&lt;p&gt;The feed may have fired, but &lt;strong&gt;Send Email (SMTP)&lt;/strong&gt; failed on bad host/port/app password. From the inbox’s point of view the digest “never worked.”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; open the failed execution. If RSS nodes produced items and SMTP is red, fix SMTP—not the feed URL. Prefer app passwords where the provider requires them.&lt;/p&gt;

&lt;h4&gt;
  
  
  6. Instance / network (self-hosted)
&lt;/h4&gt;

&lt;p&gt;Outbound HTTPS from the n8n host must reach the feed origin. Corporate DNS, missing CA bundle, or IPv6-only oddities show up as read errors in Executions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; from the same host/container that runs n8n, fetch the feed URL. Fix proxy/CA settings if the host cannot reach the public internet the way your laptop can.&lt;/p&gt;

&lt;h3&gt;
  
  
  Minimal documented pattern (RSS → daily digest email)
&lt;/h3&gt;

&lt;p&gt;A practical shape many people want:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Schedule&lt;/strong&gt; (e.g. daily) + optional &lt;strong&gt;Manual Trigger&lt;/strong&gt; for tests.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Config&lt;/strong&gt; (Set): feed URL list, &lt;code&gt;toEmail&lt;/code&gt; / &lt;code&gt;fromEmail&lt;/code&gt;, lookback hours, max articles.
&lt;/li&gt;
&lt;li&gt;Split feeds → &lt;strong&gt;RSS Feed Read&lt;/strong&gt; (continue on error per feed if you want bad sources skipped).
&lt;/li&gt;
&lt;li&gt;Time window filter → dedupe → limit → slim fields → aggregate.
&lt;/li&gt;
&lt;li&gt;Optional LLM “write digest” (continue on error if email must still send a fallback).
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Send Email (SMTP)&lt;/strong&gt;.
&lt;/li&gt;
&lt;li&gt;Publish. Verify with &lt;strong&gt;Run now&lt;/strong&gt;, then let the schedule run once in production.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Documented on self-hosted n8n &lt;strong&gt;2.44.6&lt;/strong&gt;; not tested on n8n Cloud. Import-checked patterns with sample data still need your own feed and SMTP verification.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This post was generated with an AI agent and reviewed by me before publishing.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>rss</category>
      <category>automation</category>
      <category>email</category>
    </item>
    <item>
      <title>Why your n8n Error Workflow is not triggering (and how to fix it)</title>
      <dc:creator>Lantern Flows</dc:creator>
      <pubDate>Sun, 01 Nov 2026 04:25:19 +0000</pubDate>
      <link>https://dev.to/lanternflows/why-your-n8n-error-workflow-is-not-triggering-and-how-to-fix-it-1jm7</link>
      <guid>https://dev.to/lanternflows/why-your-n8n-error-workflow-is-not-triggering-and-how-to-fix-it-1jm7</guid>
      <description>&lt;p&gt;Your n8n workflows can fail at 2 a.m. and tell you nothing. You add an &lt;strong&gt;Error Workflow&lt;/strong&gt;, wait for the next failure… and the alert never fires.&lt;/p&gt;

&lt;p&gt;This is one of the most common “it should work” traps in n8n. Search results for &lt;em&gt;n8n error workflow not triggering&lt;/em&gt; are mostly docs and forum threads, so here is a single checklist you can walk through in about ten minutes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Scope of this article:&lt;/strong&gt; documented against &lt;strong&gt;self-hosted n8n 2.44.6&lt;/strong&gt;. &lt;strong&gt;Not tested on n8n Cloud.&lt;/strong&gt; Notification examples use &lt;strong&gt;Slack&lt;/strong&gt; or &lt;strong&gt;SMTP&lt;/strong&gt; only.&lt;/p&gt;

&lt;h3&gt;
  
  
  What an Error Workflow actually is
&lt;/h3&gt;

&lt;p&gt;An Error Workflow is a normal workflow whose first node is an &lt;strong&gt;Error Trigger&lt;/strong&gt;. You point other workflows at it under &lt;strong&gt;Settings → Error workflow&lt;/strong&gt;. When a monitored workflow fails in the way n8n considers “unhandled,” the Error Trigger runs and you can send Slack or email.&lt;/p&gt;

&lt;p&gt;It is &lt;strong&gt;not&lt;/strong&gt; a global catch-all for every red node you see while clicking around in the editor.&lt;/p&gt;

&lt;h3&gt;
  
  
  Checklist: why it is “not triggering”
&lt;/h3&gt;

&lt;p&gt;Work top to bottom. Most “not triggering” reports are one of these.&lt;/p&gt;

&lt;h4&gt;
  
  
  1. You tested with a manual run in the editor
&lt;/h4&gt;

&lt;p&gt;Error Workflows are meant for &lt;strong&gt;automatic / production&lt;/strong&gt; executions (schedules, webhooks, app triggers on a published workflow). A manual &lt;strong&gt;Execute workflow&lt;/strong&gt; click in the canvas often &lt;strong&gt;will not&lt;/strong&gt; invoke the Error Workflow.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; publish (activate) a throwaway workflow, give it a real trigger (or Schedule), force a failure there, then check &lt;strong&gt;Executions&lt;/strong&gt; on the Error Workflow—not only the editor toast.&lt;/p&gt;

&lt;h4&gt;
  
  
  2. The Error Workflow is not selected on the failing workflow
&lt;/h4&gt;

&lt;p&gt;Open the workflow that failed → &lt;strong&gt;Settings&lt;/strong&gt; (or Options → Settings) → &lt;strong&gt;Error workflow&lt;/strong&gt; → pick your handler → save / publish again.&lt;/p&gt;

&lt;p&gt;In newer n8n versions, both the monitored workflow and the error handler may need to be &lt;strong&gt;published&lt;/strong&gt;. If you only saved a draft, production failures will not see the setting.&lt;/p&gt;

&lt;h4&gt;
  
  
  3. The failure was “handled,” so n8n does not escalate
&lt;/h4&gt;

&lt;p&gt;If a node uses &lt;strong&gt;Continue On Fail&lt;/strong&gt;, or you wired the node’s &lt;strong&gt;error output&lt;/strong&gt; and handled it yourself, the execution can finish without counting as an unhandled workflow failure. The Error Trigger stays quiet.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; for the path you want alerts on, turn off Continue On Fail and do not swallow the error on a side branch—or accept that handled errors will not page you.&lt;/p&gt;

&lt;h4&gt;
  
  
  4. The Error Trigger is not the first node (or the handler itself errors)
&lt;/h4&gt;

&lt;p&gt;The handler must start with &lt;strong&gt;Error Trigger&lt;/strong&gt;. Keep the alert path short: Error Trigger → Set/Compose → &lt;strong&gt;Slack&lt;/strong&gt; or &lt;strong&gt;Send Email (SMTP)&lt;/strong&gt;. Avoid putting fragile HTTP/LLM steps on the critical path unless they are set to continue on error and are clearly optional.&lt;/p&gt;

&lt;h4&gt;
  
  
  5. You are looking at the wrong place for proof
&lt;/h4&gt;

&lt;p&gt;Production Error Workflow runs show up under &lt;strong&gt;Executions&lt;/strong&gt; for that workflow. They may not paint a big banner on the workflow that failed. Confirm:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the failing workflow has a failed &lt;strong&gt;production&lt;/strong&gt; execution;&lt;/li&gt;
&lt;li&gt;the Error Workflow has a matching new execution at about the same time;&lt;/li&gt;
&lt;li&gt;Slack/SMTP credentials on the handler are valid (a bad credential makes it look like “nothing happened”).&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  6. Instance / URL gotchas (self-hosted)
&lt;/h4&gt;

&lt;p&gt;If your alert includes an execution link, the instance public URL must be configured correctly, or the link is useless even when the trigger did fire. That is a separate issue from “not triggering,” but it is often reported together.&lt;/p&gt;

&lt;h3&gt;
  
  
  Minimal documented pattern (Slack or SMTP)
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;New workflow → &lt;strong&gt;Error Trigger&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Edit Fields (Set)&lt;/strong&gt; for subject/channel/recipient prefixes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Slack&lt;/strong&gt; &lt;em&gt;Send message&lt;/em&gt; &lt;strong&gt;or&lt;/strong&gt; &lt;strong&gt;Send Email (SMTP)&lt;/strong&gt; with workflow name, failed node, error message, and execution URL from the Error Trigger payload.&lt;/li&gt;
&lt;li&gt;Publish the handler.&lt;/li&gt;
&lt;li&gt;On every workflow you care about: Settings → Error workflow → select it → publish.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;To force a failure on purpose: add a &lt;strong&gt;Stop And Error&lt;/strong&gt; node on a published schedule/webhook workflow, run it once in production mode, then verify the handler execution.&lt;/p&gt;

&lt;p&gt;Optional AI “explain this error” steps are fine &lt;strong&gt;only&lt;/strong&gt; if they cannot block the alert (continue on error, off by default).&lt;/p&gt;

&lt;p&gt;Documented on self-hosted n8n &lt;strong&gt;2.44.6&lt;/strong&gt;; not tested on n8n Cloud. Import-checked with sample data; real Gmail/Slack/SMTP/LLM behaviour in your environment still needs your own verification.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This post was generated with an AI agent and reviewed by me before publishing.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>automation</category>
      <category>devops</category>
      <category>monitoring</category>
    </item>
  </channel>
</rss>
