Marketing

Report email performance every month

Every month, Merlin posts each Customer.io automation's sends, opens, clicks and unsubscribes in Slack. The month before sits next to them, and drops are called out.

@Merlin on the 1st of every month at 9:00, read last month's delivery metrics for each active automation in Customer.io: messages sent, open rate, click rate and unsubscribes, each next to the month before. Post them here ordered by messages sent and point out any automation whose open or click rate fell by 20% or more. Only read: don't change any automation or message.

#marketing
Get started for free
  1. Starts whenOn the 1st of every month at 09:00, a monthly Merlin schedule posts to #marketing
  2. Merlin worksClaude Code or Codex reads last month's delivery metrics for each Customer.io automation and the month before
  3. You getSends, open rate, click rate and unsubscribes by automation in #marketing, with the drops called out

Tools

  • Slack
  • Customer.io

Capabilities

  • Automations
  • Your agent's MCP

How it works

From Customer.io's delivery metrics to the month's email results.

On the 1st of every month at 9:00, the automation you created from #marketing starts a run.

/AcmeTeam/Automations/Report email performanceFeedback?C

Overview

Agents

Skills

Memory

Automations

Integrations

Settings

Report email performance

Pause
StatusActive
CreatorC Chloe You
ScopeWorkspace
Last runOct 1, 2026, 9:00 AM

DetailsRun history

Trigger

When Merlin runs it.

RuleHow often Merlin runs it.Monthly
Day of monthShort months use their final day.1
TimeNext run Nov 1, 2026, 9:00 AM.09:00

Run

What Merlin does each time, where it runs, and where the result goes.

Run instruction

on the 1st of every month at 9:00, read last month's delivery metrics for each active automation in Customer.io: messages sent, open rate, click rate and unsubscribes, each next to the month before. Post them here ordered by messages sent and point out any automation whose open or click rate fell by 20% or more. Only read: don't change any automation or message.

RuntimeThe computer and coding agent that run it.Chloe's MacBook Pro · Claude Code
DestinationWhere Merlin posts the result. Choose None when the instruction already acts in your tools.#marketing

Before and after

The month starts with the email numbers, not with exporting them.

Without Merlin

Someone opens each automation's metrics for two months, copies them into a sheet and works out what changed.

  1. 01Open each automation's metrics
  2. 02Set last month's dates
  3. 03Copy sends, opens and clicks
  4. 04Repeat for the month before
  5. 05Work out each change
  6. 06Flag the drops
  7. 07Post the numbers in #marketing

With Merlin

A monthly schedule posts the numbers, so the team starts on what to fix.

  1. Day 1 of every month at 09:00Monthly Merlin schedule in #marketing
  2. Reads both months on Chloe's MacBookCustomer.io delivery metrics, read only
  3. Results by automation in #marketingWith the drops called out

Setup

Give your agent Customer.io, then schedule the report from #marketing.

Set these up once and the numbers arrive on the 1st of every month. Merlin only reads, so your automations stay as they are.

  1. 01Connect a machineRuntimeInstall the Merlin desktop app or CLI on a computer running Claude Code or Codex. You can also use a machine a teammate shares with your workspace.
  2. 02Add Merlin to SlackIntegrationsInstall the Slack app and add Merlin to the channel you work in. A private channel needs /invite @Merlin.
  3. 03Add Customer.io to your agentYour agent's MCPConnect the Customer.io MCP server to Claude Code or Codex on the machine that runs this. Its credentials stay on that machine.
  4. 04Connect Customer.io with read accessYour agent's MCP

    An account admin turns on Customer.io MCP in Settings > AI. The run only needs the default read scope, which covers automations and delivery metrics, so approve nothing more when the agent connects (permission scopes).

  5. 05Paste the setup promptAutomationsSend the prompt below to @Merlin in Slack, in the channel it should post to. Merlin creates the automation and tells you what it set up.

Prompt

Schedule the monthly email report with one message in #marketing.

@Merlin on the 1st of every month at 9:00, read last month's delivery metrics for each active automation in Customer.io: messages sent, open rate, click rate and unsubscribes, each next to the month before. Post them here ordered by messages sent and point out any automation whose open or click rate fell by 20% or more. Only read: don't change any automation or message.

#marketing

Once, when you send it

  1. PromptYou send the prompt to @Merlin
  2. AutomationMerlin creates the automation

Every scheduled run

  1. ScheduleThe schedule starts a run
  2. RuntimeMerlin picks the creator's machine first
  3. ContextThe run gathers context
  4. WorkClaude Code or Codex reads both months' delivery metrics
  5. ResultMerlin posts the results in #marketing
  6. SteeringReplies in its thread follow up

Bring your coding agents into the tools your team already uses.

Let your whole team hand work to Claude Code and Codex today. Connect one machine and add Merlin to Slack, Linear or GitHub. 14-day free trial, no API keys, no card.