> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/utils/rss/get-feed.md).

# Get Feed

### Overview

The **Get Feed Component** retrieves and parses an RSS feed from a given URL, extracting key information such as feed title, description, and individual feed items.

### Usage

This component fetches RSS feeds and outputs structured data for further processing in workflows, making it useful for content aggregation and real-time updates.

#### Input Ports

| Port | Description                                  |
| ---- | -------------------------------------------- |
| `in` | Receives the RSS feed URL to fetch the feed. |

#### Output Ports

| Port  | Description                                                       |
| ----- | ----------------------------------------------------------------- |
| `out` | Emits the parsed RSS feed data, including feed details and items. |

#### Properties

| Property | Type     | Description                |
| -------- | -------- | -------------------------- |
| `url`    | `string` | The RSS feed URL to fetch. |

#### Processing Logic

1. **Receives Feed URL**: Accepts an input URL pointing to an RSS feed.
2. **Fetches Feed Data**: Uses an RSS parser to retrieve and parse feed details.
3. **Extracts Key Information**:
   * Feed title, description, and link.
   * Feed image details (if available).
   * Feed items including headlines, descriptions, and links.
4. **Emits Parsed Data**: Outputs the structured feed data through the `out` port.

#### Output Data Schema

| Property      | Type     | Description                                                       |
| ------------- | -------- | ----------------------------------------------------------------- |
| `feedUrl`     | `string` | The URL of the fetched feed.                                      |
| `title`       | `string` | The title of the RSS feed.                                        |
| `description` | `string` | The description of the RSS feed.                                  |
| `link`        | `string` | The main link to the RSS feed.                                    |
| `items`       | `array`  | List of feed items, each containing title, description, and link. |
| `image.link`  | `string` | The link to the feed's image (if available).                      |
| `image.url`   | `string` | The URL of the feed's image.                                      |
| `image.title` | `string` | The title of the feed's image.                                    |

### Notes

* **Supports Standard RSS Feeds**: Parses commonly used RSS formats.
* **Real-Time Content Retrieval**: Useful for monitoring and aggregating content updates.
* **Structured Data Output**: Provides a clean JSON representation of the feed for easy integration.

This component is ideal for workflows requiring automated RSS feed processing, news aggregation, and content distribution.


---

# 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://docs.appmixer.com/connector-configuration/utils/rss/get-feed.md?ask=<question>&goal=<user_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.