> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Subscribe to Release Notes

> Follow MoEngage SDK release notes through RSS in your email client, browser, Slack, or an automation tool.

RSS (Really Simple Syndication) is an open standard, so you can read these feeds in most email clients, browsers, team chat tools, and dedicated feed readers.

<Note>
  MoEngage publishes an RSS feed for each SDK's release notes. Product and Partner release notes don't have RSS feeds yet. Check the [Product](/release-notes/product) and [Partners](/release-notes/partners) release notes on the docs site for those updates.
</Note>

Subscribe to a feed to get new SDK versions, changelogs, and breaking-change notices delivered to the reader of your choice, without checking the docs site manually.

## Available Feeds

Each SDK release notes page has its own feed. Copy the feed URL for the SDKs you use.

| SDK                 | Feed URL                                                                     |
| ------------------- | ---------------------------------------------------------------------------- |
| Android             | `https://www.moengage.com/docs/release-notes/sdks/android/rss.xml`           |
| iOS                 | `https://www.moengage.com/docs/release-notes/sdks/ios/rss.xml`               |
| Web                 | `https://www.moengage.com/docs/release-notes/sdks/web/rss.xml`               |
| React Native        | `https://www.moengage.com/docs/release-notes/sdks/react-native/rss.xml`      |
| Expo (React Native) | `https://www.moengage.com/docs/release-notes/sdks/expo-react-native/rss.xml` |
| Flutter             | `https://www.moengage.com/docs/release-notes/sdks/flutter/rss.xml`           |
| Cordova             | `https://www.moengage.com/docs/release-notes/sdks/cordova/rss.xml`           |
| Capacitor           | `https://www.moengage.com/docs/release-notes/sdks/capacitor/rss.xml`         |
| Unity               | `https://www.moengage.com/docs/release-notes/sdks/unity/rss.xml`             |
| Segment             | `https://www.moengage.com/docs/release-notes/sdks/segment/rss.xml`           |
| mParticle           | `https://www.moengage.com/docs/release-notes/sdks/mparticle/rss.xml`         |

## Subscribe to a Feed

Pick the method that matches where you want to receive updates. Each method uses the same feed URL from the table above.

<Tabs>
  <Tab title="Slack">
    Post new releases to a Slack channel using Slack's built-in RSS app. Best for teams that track updates together.

    <Info>
      Your workspace admin must install the [RSS app](https://slack.com/apps/A0F81R7U7-rss) before you can use the `/feed` command.
    </Info>

    <Steps>
      <Step title="Open the channel">
        Go to the channel where you want release updates to appear.
      </Step>

      <Step title="Subscribe to the feed">
        Send the following message, replacing the URL with your SDK's feed URL:

        ```text wrap theme={null}
        /feed subscribe https://www.moengage.com/docs/release-notes/sdks/android/rss.xml
        ```
      </Step>
    </Steps>

    Use `/feed list` to see your subscriptions and `/feed remove [ID]` to unsubscribe. For the full command reference, see Slack's guide on [adding RSS feeds to Slack](https://slack.com/help/articles/218688467-Add-RSS-feeds-to-Slack).
  </Tab>

  <Tab title="Microsoft Teams">
    Post new releases to a Teams channel using a Workflows (Power Automate) automation. Best for teams that track updates together.

    <Info>
      Microsoft retired the classic Office 365 RSS connector for Teams. Use the **Workflows** app, powered by Power Automate, instead.
    </Info>

    <Steps>
      <Step title="Open Workflows">
        In Teams, go to the channel where you want updates, select the more options (**...**) menu, and choose **Workflows**.
      </Step>

      <Step title="Choose an RSS template">
        Search for an RSS template, such as **Post to a channel when a feed item is published**, and select it.
      </Step>

      <Step title="Add the feed URL and destination">
        Paste your SDK's feed URL, then confirm the target team and channel.
      </Step>

      <Step title="Save the workflow">
        Save the workflow. New releases post to the channel automatically.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Microsoft Outlook">
    Use Outlook to receive each release as an email-style message in a dedicated folder. Best for individuals who want updates in their email client.

    <Steps>
      <Step title="Open RSS Feeds">
        In the left navigation pane, right-click **RSS Feeds**.
      </Step>

      <Step title="Add a new feed">
        Select **Add a New RSS Feed**.
      </Step>

      <Step title="Paste the feed URL">
        Paste the feed URL for your SDK, then click **Add** and confirm with **Yes**.
      </Step>
    </Steps>

    A new folder appears under **RSS Feeds**, and each release entry shows up like an email message.

    <Tip>
      Right-click the feed and select **Data File Properties** to rename it (for example, "MoEngage Android Release Notes"). To share updates with your team, create a rule that forwards new entries to a shared mailbox.
    </Tip>
  </Tab>

  <Tab title="Browser Extension">
    Most modern browsers, including Microsoft Edge and Google Chrome, don't display RSS feeds natively. Use a feed-reader extension instead. Best for quick access without email notifications.

    <Steps>
      <Step title="Install a feed reader">
        Add an RSS extension from your browser's extension store, such as Feedbro or RSS Feed Reader.
      </Step>

      <Step title="Add a new feed">
        Open the extension and choose the option to add or subscribe to a feed.
      </Step>

      <Step title="Paste the feed URL">
        Paste the feed URL for your SDK and save. New releases appear in the extension.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Automated Email">
    If your email client doesn't support RSS, use an automation tool such as [Zapier](https://zapier.com/apps/email/integrations/rss) to email you when a feed updates. Best for sending updates to any inbox or distribution list.

    <Steps>
      <Step title="Create an RSS-to-email automation">
        In your automation tool, create a workflow that triggers on new RSS feed items.
      </Step>

      <Step title="Add the feed URL">
        Set the RSS source to your SDK's feed URL.
      </Step>

      <Step title="Set the email action">
        Configure the action to send an email to the recipients you choose whenever a new release is published.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Other Things You Can Do with the Feed

Because the feed is machine-readable, an automation tool such as [Zapier](https://zapier.com/apps/rss/integrations), [Make](https://www.make.com/en/integrations/rss), or [Power Automate](https://make.powerautomate.com/) can watch it and route new releases anywhere your team works. Common options include:

* **Filtered alerts** — notify only when an entry matches a keyword, such as "breaking" or a specific module name.
* **Upgrade tracking** — log each release to a Google Sheet, Airtable, or Notion database to track which SDK versions you've reviewed.
* **Merged feeds** — combine the feeds for the SDKs you use into a single stream in a feed reader.

### Create an Upgrade Task for Each Release

Turn every new SDK release into a tracked task in Jira or Linear, so upgrades don't get missed.

<Steps>
  <Step title="Add an RSS trigger">
    In your automation tool, create a workflow that triggers on new items from your SDK's feed URL.
  </Step>

  <Step title="Add the issue-tracker action">
    Add an action to create an issue in Jira or Linear.
  </Step>

  <Step title="Map the release details to the issue">
    Use the feed item's title and link to fill the issue. For example, set the summary to `Review [SDK] release: {{title}}` and add the release link in the description.
  </Step>

  <Step title="Set the assignee and project">
    Route the issue to the team or project that owns SDK upgrades, then turn on the workflow.
  </Step>
</Steps>