From 5969cc2432908ca3b9d4f51836ac35d1f983a31f Mon Sep 17 00:00:00 2001 From: "@mrubens" <2600+mrubens@users.noreply.github.com> Date: Sun, 13 Sep 2026 19:43:42 +0000 Subject: [PATCH] docs: correct Resend cookbook setup --- apps/docs/cookbook/product-updates-newsletter.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/apps/docs/cookbook/product-updates-newsletter.mdx b/apps/docs/cookbook/product-updates-newsletter.mdx index a27b01cd68..e0d41f2e25 100644 --- a/apps/docs/cookbook/product-updates-newsletter.mdx +++ b/apps/docs/cookbook/product-updates-newsletter.mdx @@ -13,13 +13,13 @@ 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) @@ -27,7 +27,7 @@ It's how we actually generate the ones we send every Friday. - 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 @@ -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`. @@ -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. @@ -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.