# How to Get a Shared Phone Alert When an RSS Feed Updates

> Use a feed reader for one person's alerts, or connect RSS by Zapier to PingRoom for one bounded update shared with a small group.

- Published: 2026-11-05
- Author: PingRoom
- Category: Automation
- Topics: RSS feed phone notification, RSS update push notification, RSS by Zapier webhook, new content push notifications
- Canonical: https://pingroom.io/blog/rss-feed-update-push-notifications
- Cover image: https://pingroom.io/blog/rss-feed-update-push-notifications-cover.webp
- Cover description: Two PingRoom avatars and Pingo watch one blank feed item emerge from a brass reader beside a face-down phone.

If only you need an RSS alert, use a feed reader or IFTTT's own phone notification. If the same update should reach a small group, connect **RSS by Zapier → New Item in Feed** to a PingRoom incoming webhook. Keep the Ping short, and use the feed item's GUID or canonical URL as the stable event identity.

This is a Zapier webhook recipe, not a native RSS or Zapier integration. Zapier polls the feed; PingRoom sends the selected update to the Room.

## Choose the smaller setup first

The best route depends on who needs the update.

| Need                                                     | Better starting point                                                                                               | Why                                                                                        |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| One person's phone should show new feed items            | A feed reader such as [Feeder](https://feeder.co/help/get-started/get-notifications-about-important-things/)        | It already supports per-feed mobile notifications and opens the item in a reading workflow |
| One person's IFTTT app should show the alert             | [IFTTT's RSS notification applet](https://ifttt.com/applets/a7DCywTH-get-ifttt-notification-for-new-rss-feed-items) | It connects the RSS trigger directly to IFTTT's mobile notification action                 |
| The same bounded update should reach a small group       | RSS by Zapier → PingRoom                                                                                            | One automation can send one named signal to a private Room                                 |
| The group needs a digest, archive, or full reading queue | A feed reader, email digest, or shared knowledge tool                                                               | PingRoom is an attention signal, not an RSS archive                                        |

PingRoom publishes this guide. Feeder and IFTTT are often the better choice for personal reading alerts. Use the shared-Room path only when several people genuinely need the same short signal.

## Check the plan and timing boundaries

You need:

- a public RSS or Atom feed with stable item GUIDs or URLs;
- a Zapier plan that includes **Webhooks by Zapier**, which Zapier currently labels as a Premium action in its [RSS integration directory](https://zapier.com/apps/rss/integrations);
- a private PingRoom Room whose owner has active Pro, because incoming webhooks are a Pro connection;
- Room members with PingRoom notifications allowed on their phones.

Zapier's [RSS trigger guide](https://help.zapier.com/hc/en-us/articles/8496279482125-Trigger-Zap-workflows-from-new-RSS-feed-items) recommends **Different Guid/URL** for most feeds. Polling frequency depends on the Zapier plan. A new post can therefore appear after a delay, and an accepted Ping still does not guarantee that every phone displays it under every network, Focus, mute, or notification setting.

## Create the PingRoom destination

Open the Room in [PingRoom's browser app](/app/rooms), then go to **Settings → Connections → From another app**.

1. Add an incoming webhook named after the feed, such as **Release notes**.
2. Leave **Quick Ping** on **Custom message**.
3. Give it a recognizable icon, color, and sound.
4. Copy the webhook URL into Zapier.

The URL contains the credential. Keep it out of screenshots, public Zap templates, browser-side code, and shared notes. The [incoming-webhook walkthrough](/blog/webhook-to-push-notification) explains secret rotation, accepted fields, and response handling.

## Configure one feed trigger

In Zapier, create a Zap and select **RSS by Zapier** as the trigger.

1. Choose **New Item in Feed** for one feed.
2. Paste the feed URL.
3. Keep **What Triggers a New Feed Item?** on **Different Guid/URL** unless the publisher's feed requires another documented rule.
4. Test the trigger and inspect the sample item.

Do not use **Anything is Different** simply to make the Zap feel more responsive. That rule can treat an edit to an existing item as another trigger. For this workflow, the useful event is a genuinely new item.

## Send fixed copy and a stable identity

Add **Webhooks by Zapier → POST** as the action. This example deliberately leaves the article title, author, summary, and URL in the feed system. The Room receives only a fixed signal.

| Zapier field              | Value                                                                                                 |
| ------------------------- | ----------------------------------------------------------------------------------------------------- |
| URL                       | the protected PingRoom webhook URL                                                                    |
| Payload Type              | `json`                                                                                                |
| Data: `title`             | `Feed updated`                                                                                        |
| Data: `message`           | `New item in Release notes`                                                                           |
| Data: `correlation_id`    | the GUID or canonical URL only when it is no more than 255 characters; otherwise leave this field out |
| Header: `Accept`          | `application/json`                                                                                    |
| Header: `Idempotency-Key` | the trigger item's GUID; use its canonical URL only when the feed has no GUID                         |

Use a fixed feed label that is safe on a lock screen. Do not map the full item body, an unpublished draft, private feed credentials, or an unbounded title into the Ping.

The event identity matters. PingRoom limits `correlation_id` to 255 characters, so omit that optional field when the source identity is longer; the idempotency header still owns the retry. If Zapier retries one item with the same key and body, PingRoom can return the original completed response instead of creating another Ping. If the publisher assigns a new GUID to a corrected item, treat that as a new source event rather than guessing that it is a duplicate.

![Two PingRoom avatars separate one accepted blank card from a duplicate while Pingo watches from the other side of a brass divider.](/blog/rss-feed-update-push-notifications-1.webp)

[Pingo the Pigeon](/Pingo), PingRoom's official mascot and fictional Chief Marketing Officer, is giving the duplicate card his standard half-lidded review. He has no access to the feed, Zap, webhook URL, Room, or anyone's phone. The people who configure the workflow remain responsible for its sources and copy.

_AI-generated editorial artwork uses approved Pingo and PingRoom avatar references. The miniature workflow is an illustrative example, not a customer setup or product screen._

## Run four checks before turning it on

Use a harmless public feed or a feed you control.

1. **New item:** confirm Zapier finds one sample and the POST creates exactly one Ping with the fixed title and message.
2. **Edited item:** confirm an edit with the same GUID or URL does not become a second “new item” under the selected trigger rule.
3. **Exact replay:** repeat the same POST with the same body and idempotency key; Room history should still contain one Ping for that item.
4. **Locked phone:** check that the visible copy reveals only the feed label you intended to share.

HTTP 200 means PingRoom accepted and queued the event. It does not prove that every member saw it or read the source item. The publisher's feed remains the content record, and Zap history remains the automation record.

## Keep noisy feeds out of the Room

One item per day may be useful. Forty items per hour usually are not. If the feed is busy, filter for a stable category or keyword before the POST step, send a digest somewhere else, or keep it in a reader.

The Room should answer one question: **Is there a new item this group needs to notice?** It should not become another unread feed.

Start with one harmless feed and [create or choose the destination Room](/app/rooms). Test the duplicate boundary before enabling the Zap for real items. For the general POST and retry contract, read the [Zapier workflow guide](/blog/zapier-push-notifications) and the [webhook reference](/documents/webhooks).