Keep Reddit automations running in Zapier and IFTTT

Why the automation stops

Zapier's RSS trigger and IFTTT's RSS Feed service both watch a feed address and fire when a new item appears. Reddit retires all of its feeds on 13 Nov 2026. After that the trigger finds nothing new, so the zap or applet stops running without an obvious error, and the spreadsheet, task list or inbox it fed simply stops growing.

The steps after the trigger are fine. The address at the start is the one thing to change.

Zapier: edit the trigger

1. Create a free Redlisten account and copy your key from the dashboard.
2. Open the zap and the RSS by Zapier trigger, New Item in Feed.
3. Replace the Feed URL with the same path on api.redlisten.com, ending in .rss, with ?key= and your key.
4. Test the trigger. Zapier pulls a recent item, and its fields keep the names the later steps already map: title, link, author, published time and content.
5. Publish the zap.

# The Feed URL field in the RSS trigger, before
https://www.reddit.com/r/forhire/new.rss

# After
https://api.redlisten.com/r/forhire/new.rss?key=rl_live_YOUR_KEY

IFTTT: edit the applet

1. Open the applet and its RSS Feed trigger, New feed item or New feed item matches.
2. Replace the Feed URL with the Redlisten address and save.
3. Wait for the next new post in that community to check it fires.

If the applet used New feed item matches to filter on a word, consider a Redlisten search feed in its place: /search.rss?q= narrows at the source, so IFTTT sees fewer items and the matches arrive faster.

Watch the polling count

Both services check the feed on a schedule set by your plan with them, and Zapier can check as often as every few minutes. Each check is one Redlisten request, so a zap checking every two minutes spends about 21,600 requests a month on a single feed. That is a Pro key. A zap checking every fifteen minutes spends about 2,900. Set the slowest interval the workflow tolerates, and combine communities into one feed with a plus, /r/a+b+c/new.rss, so one check covers them all.

If the trigger test fails

A 401 or an empty feed means the key is missing or mistyped. Open the address in a browser: a working feed shows XML with entries, a bad key shows an error naming the problem. A 429 means the key has used its requests for the month or is being polled faster than its per minute limit; the dashboard shows which.

Zapier says no items were found when the feed is valid but has nothing new since the last check, which is common on a narrow search feed; pick a busier community to test with, then switch back. Duplicate runs after the switch happen because the services remember items by id per feed address, so the new address can fire once for a few recent entries. Turn the zap or applet off while you edit and back on afterwards to keep that to one batch.

When a webhook beats a feed

On paid plans a keyword stream pushes each match to a webhook address the moment it is collected. Zapier's Catch Hook trigger and IFTTT's Webhooks service both accept one, so the automation runs on each match with no polling and no requests spent waiting. For a lead watch or a support alert where minutes matter, that is the better shape.

What it costs

Every time the trigger checks a feed it makes one request, and each entry in the feed counts as one result. A free key has 250 requests a month, which fits one feed checked every three hours, enough to test the switch. A Pro key at $29 a month has 50,000 requests and covers about fifty feeds checked hourly. Plans are listed on the pricing page, dated 6 Nov 2026, and there are no daily caps.

See the RSS switch page for every feed path, and the docs for streams and webhooks.