How to Connect Customer.io to Claude (No-Code MCP Guide)

To connect Customer.io to Claude, link your account at onboard.windsor.ai/app/customer_io, then add the Windsor.ai connector in Claude. That’s it. Open a new chat and ask about your broadcasts, campaigns, and newsletters.

Here’s the problem it solves: Customer.io’s own dashboard shows broadcast and campaign performance one screen at a time, and lining that up against your other marketing channels usually means exporting data by hand and stitching it together in a spreadsheet.

Once Customer.io is connected through Windsor.ai, you can ask Claude about delivery, open rates, or campaign status in plain language and get an answer in seconds, alongside data from any other connected source.

🚀 Connect Customer.io to Claude with Windsor MCP. Free forever plan, no credit card. onboard.windsor.ai/app/customer_io

2 steps to connect Customer.io to Claude

Connecting Customer.io to Claude via Windsor.ai takes two steps, no code or manual CSV work required.

📖 For the full walkthrough, see Windsor’s documentation on integrating data into Claude.

Prerequisites

• A Customer.io account with at least one active broadcast or campaign
• A Windsor.ai account (free forever plan, no credit card, or a paid plan from $19/month)
• A Claude account with access to connectors

Step 1. Connect Customer.io to Windsor.ai

Go to onboard.windsor.ai/app/customer_io and select Customer.io as your data source.

Authorize Windsor.ai to access your Customer.io account. Connect additional Customer.io accounts too if you manage more than one.

Step 2. Add the Windsor.ai connector in Claude

Open Claude and go to Customize, then Connectors. Search for “Windsor” and click Add, this installs the native connector in one click, no URL to paste.

Sign in to Windsor.ai when prompted, then pick your Customer.io connector to finish.

💡 Pro tip: set permissions to “Always allow” so Claude can query your Customer.io data without asking for confirmation on every prompt.

Confirm the connection works before moving on:

List the data sources connected to my Windsor account. Do you see Customer.io there?

If Customer.io shows up in the list, you’re ready to query it in natural language.

The metrics that matter for Customer.io

Metric	What it tells you
Broadcasts Delivered	How many one-off broadcast messages actually landed in an inbox, the real reach of a send after bounces and blocks are subtracted out.
Broadcasts Opened	How many delivered broadcasts a recipient opened, a first read on whether your subject line and send time are working.
Broadcasts Clicked	How many recipients clicked a link inside a broadcast, the strongest signal that the message content itself held their interest.
Broadcasts Converted	How many recipients completed the goal event tied to a broadcast, the closest thing to a revenue signal for a one-off send.
Broadcasts Bounced	Messages a recipient’s mail server rejected outright, a direct read on list health and deliverability risk.
Broadcasts Unsubscribed	How many people opted out after a specific broadcast, an early warning that a send was off-target or too frequent.
Campaigns Delivered	Messages from automated, trigger-based campaigns that reached an inbox, the volume flowing through your always-on journeys.
Campaigns Opened	Open volume for automated campaign messages, showing whether a triggered flow stays relevant well after it was built.
Campaigns Converted	Completed goal events attributed to an automated campaign, the bottom-line payoff of a journey rather than just its send volume.
Newsletters Opened	Open volume for recurring newsletter sends, useful for tracking subscriber engagement separately from one-off broadcasts and triggered campaigns.

What to ask Claude about your Customer.io data: prompt ideas

Broadcast performance

Show delivered, opened, and clicked counts for my last 5 Customer.io broadcasts.

Which of my Customer.io broadcasts converted the most subscribers last month?

Deliverability and list health

Compare bounce and unsubscribe rates across my Customer.io broadcasts for this quarter.

Campaign and newsletter performance

Summarize delivered versus converted counts for my active Customer.io campaigns this month.

How does my Customer.io newsletter open volume this month compare to last month?

The Customer.io connection through Windsor is read-only. Claude can analyze broadcast, campaign, and newsletter performance, but it can’t create, edit, or send anything back to Customer.io.

Bonus: analyze Customer.io alongside your full stack

Windsor connects 350+ sources, so Customer.io doesn’t have to live in its own silo. A few practical blends:

• Customer.io + Meta Ads and Google Ads: blend broadcast and campaign engagement with paid spend to see cost per engaged customer instead of judging messaging performance in isolation.
• Customer.io + GA4: pair broadcast and campaign clicks with session and conversion data to see what subscribers actually do on your site after they click through.
• Customer.io + HubSpot: blend campaign conversions with CRM deal data for a single view of how messaging contributes to revenue alongside every other channel you run.

Other ways to connect Customer.io to Claude

Manual CSV export

You can export broadcast or campaign reports from Customer.io as a CSV and upload the file into a Claude conversation. It works, but it’s a static snapshot, every time you want fresh numbers, you have to re-export and re-upload by hand.

Zapier or Make

Zapier or Make can move Customer.io events into another tool as part of an automation workflow. That’s useful for triggering actions elsewhere, but it isn’t built for asking Claude ad hoc questions about your data.

Neither a CSV export nor a Zapier/Make workflow gives you the live, queryable view that the native Windsor.ai connector does.

Conclusion

Customer.io’s dashboard tells you what happened, one broadcast or campaign at a time. Connecting it to Claude through Windsor.ai turns that data into a live source you can question in plain language, blended with any of the 350+ other sources Windsor connects.

🚀 Ready to connect Customer.io to Claude? Connect Customer.io to Windsor.ai and start asking questions today.