Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -306,6 +306,7 @@
"guides/media",
"migration",
"guides/navigation",
"guides/rss-email-campaigns",
"guides/seo",
"guides/style-and-tone",
"guides/understand-your-audience"
Expand Down
130 changes: 130 additions & 0 deletions guides/rss-email-campaigns.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,130 @@
---
title: "Set up email notifications from your changelog RSS feed"
sidebarTitle: "RSS email campaigns"
description: "Send automatic email notifications to subscribers when you publish changelog updates using your RSS feed with Zapier, Make, or other automation tools."
keywords: ["RSS", "email", "changelog", "Zapier", "Make", "notifications", "campaign"]
---

Mintlify generates an [RSS feed](/create/changelogs#subscribable-changelogs) for any page that uses `Update` components. You can connect this feed to an automation tool like Zapier or Make to send email notifications whenever you publish a new changelog entry.

## Prerequisites

- A Mintlify changelog page with `Update` components
- A [Zapier](https://zapier.com) or [Make](https://www.make.com) account (free tiers available)
- An email service or mailing list (Mailchimp, SendGrid, or the built-in email options in Zapier/Make)

Check warning on line 14 in guides/rss-email-campaigns.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

guides/rss-email-campaigns.mdx#L14

Did you really mean 'Mailchimp'?

## Find your RSS feed URL

Your RSS feed URL is your changelog page URL with `/rss.xml` appended. For example, if your changelog is at `https://docs.example.com/changelog`, your RSS feed is at:

```text
https://docs.example.com/changelog/rss.xml
```

To verify, open the URL in your browser. You should see an XML document with your changelog entries.

<Tip>
Add `rss: true` to your changelog page frontmatter to display an RSS icon button that links to the feed. See [subscribable changelogs](/create/changelogs#subscribable-changelogs) for details.
</Tip>

## Set up email notifications

<Tabs>
<Tab title="Zapier">

Use Zapier to connect your RSS feed to an email action.

<Steps>
<Step title="Create a new Zap">
1. Log in to [Zapier](https://zapier.com) and click **Create**.
2. Select **Zaps** to start a new automation.
</Step>
<Step title="Set up the RSS trigger">
1. Search for **RSS by Zapier** as your trigger app.
2. Select **New Item in Feed** as the trigger event.
3. Paste your RSS feed URL (for example, `https://docs.example.com/changelog/rss.xml`) into the **Feed URL** field.
4. Click **Test trigger** to confirm Zapier can read your feed.
</Step>
<Step title="Set up the email action">
Choose one of these options:

**Option A: Send a simple email notification**
1. Search for **Email by Zapier** as your action app.
2. Select **Send Outbound Email** as the action event.
3. Fill in the email fields:
- **To**: The recipient email address (or a distribution list)
- **Subject**: Use the RSS item title from the trigger data, for example: `New update: {{title}}`
- **Body**: Use the RSS item description or link, for example: `We just published a new update. Read it here: {{link}}`

{/* TODO: Verify this Mailchimp flow in Zapier. "Send Campaign" may not be the right action event — Zapier's Mailchimp integration more commonly uses "Add/Update Subscriber". Consider replacing this option with a more reliable step or removing it entirely. */}

Check warning on line 59 in guides/rss-email-campaigns.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

guides/rss-email-campaigns.mdx#L59

Did you really mean 'Mailchimp'?
**Option B: Send to a mailing list (Mailchimp)**
1. Search for **Mailchimp** as your action app.
2. Select **Send Campaign** as the action event.
3. Connect your Mailchimp account and select your audience.
4. Map the RSS item title and link to your email template fields.
</Step>
<Step title="Turn on the Zap">
Click **Publish** to activate your Zap. Zapier checks your RSS feed periodically and sends an email whenever a new entry appears.
</Step>
</Steps>

</Tab>
<Tab title="Make">

Use Make to connect your RSS feed to an email action with a visual workflow builder.

<Steps>
<Step title="Create a new scenario">
1. Log in to [Make](https://www.make.com) and click **Create a new scenario**.
</Step>
<Step title="Add the RSS module">
1. Click the **+** button to add a module.
2. Search for **RSS** and select **Watch RSS feed items**.
3. Paste your RSS feed URL into the **URL** field.
4. Set the **Maximum number of items** to a reasonable limit such as `5`.
5. Click **OK** and then **Run once** to test the connection.
</Step>
<Step title="Add the email module">
1. Click the **+** button after the RSS module.
2. Search for your email service:
- **Email**: Use the built-in **Send an email** module for simple notifications.

Check warning on line 90 in guides/rss-email-campaigns.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

guides/rss-email-campaigns.mdx#L90

Use 'email' instead of 'Email'.
- **Mailchimp**, **SendGrid**, or **Brevo**: Use the respective module for mailing list campaigns.

Check warning on line 91 in guides/rss-email-campaigns.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

guides/rss-email-campaigns.mdx#L91

Did you really mean 'Brevo'?
3. Connect your email account.
4. Map the RSS fields to the email fields:
- **Subject**: Map the item `title`
- **Content**: Map the item `description` or `link`
</Step>
<Step title="Activate the scenario">
1. Set the schedule (for example, every 15 minutes).
2. Toggle the scenario to **On**.
</Step>
</Steps>

</Tab>
</Tabs>

## Test your setup

1. Add a new `Update` component to your changelog page and deploy the change.
2. Wait for the automation tool to check your feed (or trigger a manual run).
3. Confirm the email arrives with the correct content.

{/* TODO: The `rss` prop takes an object `{ title, description }`, not just plain text. Consider updating this note to show the shape or link to /components/update for full prop details. */}
<Note>
RSS feed entries contain pure Markdown only. Components, code blocks, and HTML elements are excluded. Use the `rss` property on your `Update` components to provide alternative text for subscribers. See [subscribable changelogs](/create/changelogs#subscribable-changelogs) for details.
</Note>

## Alternative tools

Other automation platforms that support RSS-to-email workflows:

| Tool | Description |
|------|-------------|
| [IFTTT](https://ifttt.com) | Simple RSS-to-email applets with a free tier |
| [Mailchimp RSS campaigns](https://mailchimp.com/help/share-your-blog-posts-with-mailchimp/) | Native RSS-to-email feature within Mailchimp |
| [n8n](https://n8n.io) | Self-hosted or cloud automation with RSS and email nodes |
| [Buttondown](https://buttondown.com) | Newsletter tool with built-in RSS feed import |

The setup process is similar across all tools: point the tool at your RSS feed URL and configure an email action for each new item.

{/* TODO: Manually test all external links in the Alternative Tools table before publishing: IFTTT, Mailchimp RSS campaigns URL, n8n, Buttondown. */}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO comments indicate unfinished content shipped to production

Low Severity

Three {/* TODO */} comments remain in the file (lines 59, 112, and 130), indicating unresolved tasks: unverified Mailchimp steps, an inaccurate description of the rss prop shape (it takes an object { title, description }, not plain text), and untested external links. While hidden from readers via MDX comments, they represent unfinished verification work that ideally gets resolved before merging.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit ee98116. Configure here.

Loading