NewJobs: scheduled actions created from chat, personal or shared.Learn more

Customer.io + Memtro

Campaign metrics and customer journeys from Customer.io.

Connect Customer.io with an App API key for your US or EU workspace. Memtro reads campaigns, newsletters and broadcasts with their delivery, open, click and conversion metrics, segment sizes, and individual profiles with their attributes, segments, events and messages. Read-only.

What you can do with Customer.io in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Customer.io tool, reads what it needs, and answers with the source cited.

01

Daily campaign pulse

Each morning Memtro records yesterday's sent, delivered, opened, clicked and converted counts per running campaign, so you can ask what changed since last week.

02

Support with context

When a customer writes in, ask what Customer.io has sent them: Memtro returns their recent messages, whether they opened them, their attributes and segments.

  • Campaigns with trigger type, state, channels and metric totals
  • Newsletters and broadcasts with metrics
  • Per-period metric series for any campaign or send
  • Segments with live people counts
  • Profile lookup by email or id with attributes and segment membership
  • Per-person activity and message history
  • Daily sync of yesterday's per-campaign performance

Ask it like this

Questions people ask once Customer.io is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.

  • ›How did the onboarding campaign perform over the last 14 days?
  • ›Which segments is sam@fable.dev in and what did we send them?
  • ›How many people are in the Trial expiring soon segment?
  • ›Which newsletters went out this month and what were their open rates?

Where it fits

Teams that get the most from Customer.io in Memtro, with the rest of their stack attached.

Better together

A record in Customer.io is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.

Also in Marketing automation

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

How to connect

  1. 01In Customer.io open Settings → Workspace Settings → API Credentials
  2. 02Create an App API Key (Journeys App API)
  3. 03Enter the key and your region (us or eu) in Memtro and connect
Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Customer.io tools are the same everywhere.

Clients and agents →

Questions

Can Memtro change anything in Customer.io?
No. The Customer.io connector is read-only: every tool reads, searches or lists. Nothing is created, sent, updated or deleted, and the credentials you give it should be read-only too.
Who can use a Customer.io connection?
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my Customer.io data?
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Customer.io records into memory as entities.
How do I connect Customer.io?
API key. In Customer.io open Settings → Workspace Settings → API Credentials.

Connect Customer.io in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.