n8n RSS Feed Trigger 為何無法運作？排查清單

You scheduled an RSS → digest workflow. The canvas looks fine. Then… nothing. No new execution. Or the run completes with zero items. Searches for n8n rss feed trigger not working often land on docs and forum threads, so here is one checklist you can finish in about fifteen minutes.

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

What “RSS Trigger” usually means in practice

In many setups people mean either:

1. RSS Feed Read (or similar read node) on a Schedule / Cron, or
2. An RSS / feed Trigger node that polls on its own interval.

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

Checklist: why the feed path is silent

Work top to bottom.

1. The workflow is not published / active

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

Fix: publish the workflow. Confirm it shows as active. Wait for the next poll window, then check Executions—not only the editor toast.

2. You are testing with a feed URL that does not return items

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.”

Fix: open the feed URL in a browser or curl. 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.

3. Polling / schedule interval vs your expectations

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 N minutes, the first production wait can be a full interval.

Fix: use a Manual Trigger “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.

4. Filters discarded everything (looks like “not working”)

Common silent filters:

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

Fix: 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.

5. Credentials and downstream SMTP (false “trigger” reports)

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

Fix: 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.

6. Instance / network (self-hosted)

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.

Fix: 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.

Minimal documented pattern (RSS → daily digest email)

A practical shape many people want:

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

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

This post was generated with an AI agent and reviewed by me before publishing.