Skip to content

[Docs] Correct Resend cookbook setup #2633

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
roomote-community wants to merge 1 commit into
base: develop
Choose a base branch
from
Draft

[Docs] Correct Resend cookbook setup #2633

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 6 additions & 6 deletions apps/docs/cookbook/product-updates-newsletter.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,21 +13,21 @@ Product-update emails are chronically late because someone has to remember what
shipped, translate commit-speak into customer language, and then fight the
email tool. This automation does all three: every week it reads merged PRs
across your product repositories, writes the newsletter, and creates a draft in
Resend through a custom MCP server, ready for review.
Resend through the built-in integration, ready for review.

It's how we actually generate the ones we send every Friday.

- **Trigger**: Schedule
- **Setup time**: About 30 minutes
- **Requires**: Member access, an admin-configured custom Resend MCP server
- **Requires**: Member access, an admin-connected Resend integration
- **Serves**: PMs, Founders, Marketing
- **Cooked By**: [Bruno Bergher](https://github.com/brunobergher) from [Roomote](https://roomote.dev)

## Ingredients

- A [custom automation](/automations#custom-automations)
- An environment covering the product repositories
- The Resend MCP server configured under **Settings > Integrations**, with a Resend API key
- The Resend integration connected under **Settings > Integrations** using OAuth
- A report destination such as `#product-updates`, so the draft lands in a replyable thread

Members can create and manage their own custom automations once the environment
Expand All @@ -37,7 +37,7 @@ including those without a creator.

## Steps

1. Confirm an admin has added the Resend MCP server and its tools are available in the environment.
1. Confirm an admin has connected Resend and its tools are available in the environment.
2. Create a custom automation named **Product Updates Newsletter**. Choose **Custom schedule**, enter `Mondays at 9am`, and select the environment.
3. Paste the prompt below.
4. Set the report destination to `#product-updates`.
Expand All @@ -57,7 +57,7 @@ Write this week's product-updates newsletter.
- a two-sentence introduction
- one short section per change: what is new, why it matters, how to try it
Use plain language. Do not include ticket numbers or internal codenames.
4. Using the Resend MCP server, create a DRAFT broadcast with this content for
4. Using the Resend integration, create a DRAFT broadcast with this content for
the "Product updates" audience. Do not send it.
5. Post the draft content and the Resend draft link in this thread for review.

Expand All @@ -71,7 +71,7 @@ the draft. Do not pad the newsletter.
- Run monthly with `first Monday of the month at 9am`.
- Use separate automations for customer notes and a technical internal changelog.

This recipe showcases custom MCP servers, natural-language scheduling, and
This recipe showcases built-in integrations, natural-language scheduling, and
replyable automation threads. Review the draft before sending it; the automation
is deliberately instructed to create a draft, not send a broadcast.

Expand Down
Loading