Draft product updates

​

Overview

• Trigger: Schedule
• Setup time: About 30 minutes
• Requires: Member access, an admin-configured custom Resend MCP server
• Serves: PMs, Founders, Marketing
• Cooked By: Bruno Bergher from Roomote

​

Ingredients

• A custom automation
• An environment covering the product repositories
• The Resend MCP server configured under Settings > Integrations, with a Resend API key
• A report destination such as #product-updates, so the draft lands in a replyable thread

​

Steps

1. Confirm an admin has added the Resend MCP server 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.
5. Use Run now to generate the first draft, then calibrate its tone by replying in the thread.

​

Automation prompt

Write this week's product-updates newsletter.

1. Collect the PRs merged to the default branch in the last 7 days across the
   product repositories.
2. Keep only customer-visible changes: features, improvements, and fixes a
   user would notice. Skip refactors, internal tooling, and dependency bumps.
3. Write the newsletter:
   - a one-line subject
   - 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
   the "Product updates" audience. Do not send it.
5. Post the draft content and the Resend draft link in this thread for review.

If nothing customer-visible shipped this week, say so in the thread and skip
the draft. Do not pad the newsletter.

​

Variations

• Without Resend, remove step 4 and post ready-to-paste Markdown for any email tool.
• Run monthly with first Monday of the month at 9am.
• Use separate automations for customer notes and a technical internal changelog.