> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/platform/journeys/sending-feed-notifications.md).
# Sending Feed Notifications
A journey can now send a notification straight from an existing Feed. Add a **Send Feed Notification** step, choose which Feed to pull from, and the step sends that Feed's current eligible article whenever a subscriber reaches it, driven by journey entry, delays and split tests rather than only by the Feed's own fixed schedule.
You do not build separate content for this step. The article comes from the Feed you choose, the same way it would if the Feed sent it on its own schedule.
### Availability
Sending Feed Notifications from a journey is enabled for all existing Pushly customers.
### Adding a Feed Notification step
1. Open a journey in the **Journey Builder** and add a **Send Feed Notification** step.
2. Choose an existing **Feed** as the source. A Feed is created and configured on the Feeds page; this step selects one that already exists rather than letting you build one inline.
3. Save the step.
On the journey canvas, the step shows which Feed it is sourced from beneath its name.
### How it works
When a subscriber reaches the step, Pushly resolves the Feed's current eligible article the same way the Feed itself would: applying that Feed's Article Constraints (age, keywords, URL allow/deny lists, and so on), then sends it to the subscriber.
If the Feed has nothing eligible at that moment, the step sends nothing for that subscriber and the journey continues.
### Relationship to the Feed's own schedule
A Feed used in a journey does not need a Delivery Strategy of its own. You can leave **Delivery Strategy** unset on the Feed and use it purely as a content source for journeys, or keep the Feed's schedule active and also use it in one or more journeys. Both work at the same time.
Whichever path sends an article first, the Feed's own schedule or a journey step, the other will not send that same article again. You will not get a duplicate of the same article from a Feed just because it is wired into both a schedule and a journey.
### Writing the notification
Because the step sends from an existing Feed, the notification content follows the same fields as a regularly scheduled Feed notification (title, description, image, and landing URL sourced from the article). There is nothing additional to configure here beyond choosing the Feed itself.
### Reporting
Notifications sent this way appear in **Insights > Notifications** like any other notification, and are attributed back to the Feed they came from.
### Limits
| | |
| ------------------------- | --------- |
| Feed sent per step run | 1 article |
| Feeds selectable per step | 1 |
### Troubleshooting
**The step is not sending anything.** The most common cause is that the Feed has no eligible article at the moment a subscriber reaches the step, usually because its Article Constraints (age, keywords, URL lists) are excluding everything currently available. Check the Feed's constraints on the Feeds page.
**Send Feed Notification is not available as a step.** It is enabled per domain. Contact your Pushly representative.
**A subscriber didn't get an article they should have.** Confirm the Feed's own schedule or another journey hasn't already sent that same article; the Feed will not send the same article twice across both paths.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.pushly.com/platform/journeys/sending-feed-notifications.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
