Connect Klaviyo to Claude

Automatically sync your Klaviyo data to Claude using the Windsor.ai connector.

Klaviyo’s own Claude connector covers campaigns, flows and profiles inside Klaviyo. Windsor.ai puts Klaviyo next to Meta Ads, Google Ads, GA4 and Shopify, so Claude can show what email and SMS earn against what you spend, and it can build and switch on flows from the same chat.

Forget CSVs. Stop copy/paste. Connect data in minutes. No code required.

Try It Free View documentation

Free forever plan No credit card needed

Join over 6,000 businesses that trust Windsor.ai to connect Klaviyo to Claude

Which one do I need?

All four methods below get your Klaviyo data in front of Claude. They differ in what Claude can see beyond Klaviyo, what it can change, and whether the numbers line up with your Klaviyo dashboard.

“Best for” leads so you can jump straight to the row that matches your situation.

	Klaviyo’s connector	Windsor.ai	CSV export	Klaviyo API / custom MCP
Best for	Working inside Klaviyo: reports, campaigns, templates, profiles	Email and SMS results next to ad spend, GA4 and store orders, plus flow building	One question about a fixed period	Bespoke workflows the others don’t cover
Cross-channel analysis	No	Yes, 350+ sources	Only what you upload	Only if you build it
Write access	Yes: campaigns, templates, profiles, lists, flows and more	Flows: create as draft, set draft, manual or live	No	Yes, if you build it
Numbers match the Klaviyo dashboard?	Yes if you ask for attributed metric aggregates, not raw events	Yes, campaign and flow report fields are Klaviyo’s reported aggregates	Yes, at export time	Depends on what you query
Claude plan needed	Paid Claude plan	Any plan that supports connectors	Any	Any
Setup effort	Low (Owner, Admin or Manager role in Klaviyo)	Low (no code)	None, but repeated every report	High (developer task)

The custom MCP route is last on purpose. It is the heaviest option, a developer task, so it belongs at the end as the fallback for cases the other three do not cover.

Method 1

Klaviyo's official Claude connector

Klaviyo listed its connector in Claude’s directory in January 2026 and expanded it in May 2026 to Claude Chat and Cowork. It runs on Klaviyo’s own MCP server and covers most of what you can do in the Klaviyo UI: pull campaign and flow reports, query metric aggregates and events, look up and update profiles, inspect lists and segments, create campaigns and templates. Details in Klaviyo’s FAQ for the Claude app.

Setup steps

Open Connectors in Claude

In Claude on the web or desktop, go to Settings, then Connectors, and click Browse connectors.

Find Klaviyo and connect

Search for Klaviyo, click Connect and approve the OAuth prompt. You can also start from the Klaviyo App Marketplace: search for Claude and click Install.

Check your role

The Klaviyo user authorizing the connection needs an Owner, Admin or Manager role, and you need a paid Claude plan.

Turn it on in chat

In a conversation, enable Klaviyo under Search and tools and ask for a report, an audit or a draft campaign.

What it can do

Pull campaign and flow reports, metric aggregates and event history without leaving Claude
Create campaigns, assign templates, build templates and translations
Look up, search and update profiles, subscribe or unsubscribe people, inspect lists and segments
Work in Claude Chat and Claude Cowork, so a brief or audit can come back as finished work

What it can't do

See anything outside Klaviyo, no ad spend, no GA4 sessions, no store orders beyond Klaviyo's own events
Restrict which AI clients can connect, Klaviyo's MCP server is client-agnostic
Show in the Klaviyo UI which user authorized the app (use API Analytics for tool calls)
Guarantee dashboard-matching numbers unless you ask for attributed metric aggregates rather than raw events

Example prompts

Summarize last month's campaign performance: recipients, open rate, click rate and attributed revenue per campaign.

Audit my abandoned cart flow step by step and tell me where recipients drop off.

Draft a win-back campaign for subscribers who have not opened in 90 days and assign our standard template.

One known pitfall, discussed in Klaviyo’s community and on Reddit: totals in Claude can differ from the Klaviyo dashboard when Claude sums raw events instead of Klaviyo’s attributed metric aggregates. Say “use the campaign report metrics” or “attributed revenue as shown in Klaviyo” in the prompt.

Method 2

Windsor.ai for cross-channel analysis and flow building

Windsor.ai’s connector answers the question Klaviyo’s own connector cannot: what email and SMS earn against everything else you run. Among teams that query Klaviyo through Windsor’s Claude connector, 8 in 10 also query Meta Ads in the same period, 7 in 10 Google Ads, about 2 in 3 GA4 and 4 in 10 Shopify. The data Claude reads is Klaviyo’s campaign and flow report aggregates, so totals match the dashboard, and Claude can also build a flow and set it live from the same chat.

Setup takes a few minutes

Connect Klaviyo to Windsor

Go to onboard.windsor.ai/app/klaviyo and authorize your Klaviyo account. Windsor pulls campaigns, flows, lists, segments, profiles, events and revenue.

Add the Windsor.ai connector to Claude

Open the Windsor.ai connector in Claude's directory and click Connect. It works in the Claude web app and Claude Desktop, and in any other MCP-compatible client, including Claude Code, following the setup guide.

Ask questions, or build a flow

Start a new chat and ask about campaigns, flows or list growth in plain language, or describe a flow and approve it before it goes live.

No code, API keys or custom pipelines required. Runs on Windsor MCP for Claude. Screenshots for each step are in the setup guide.

See the 60-second setup

Connecting Klaviyo to Claude through Windsor.ai, step by step.

Skip exports and dashboard building, get clean, ready-to-use answers straight in Claude

Puts Klaviyo next to Meta Ads, Google Ads, GA4 and Shopify so Claude can weigh email revenue against ad spend in one conversation

Reads Klaviyo's campaign and flow report aggregates so totals match your dashboard

Builds flows as drafts and switches them to manual or live, with your approval before every change

What it can do

Query campaign reports, flow reports, lists, segments, profiles, events and revenue across one or several Klaviyo accounts
Blend Klaviyo with Meta Ads, Google Ads, GA4, Shopify, Google Search Console and billing data in the same conversation
Create a flow from a trigger and a sequence of delays, emails, SMS and conditional splits, saved as a draft
Set a flow to draft, manual or live, after you confirm

What it can't do

Create campaigns, edit templates or update profiles from Claude, that is the official connector's territory (see Method 1)
Bypass Klaviyo's limits, flow creation is capped at about 100 per day by Klaviyo

See it in your own Klaviyo data

Free forever plan, no credit card required.

Try It Free

What data is available

Ordered by how many teams query each object through Claude. Campaign reports and flow reports lead, then revenue over time, lists and segments.

Klaviyo object	Key fields	What Claude can do with it
Campaign reports	campaign, campaign_channel, sent_at, subject, campaign_report_recipients, campaign_report_open_rate, campaign_report_click_rate, campaign_report_conversions, campaign_report_conversion_value, campaign_report_revenue_per_recipient, campaign_report_unsubscribe_rate	Campaign rankings, subject line comparisons, email versus SMS
Flow reports	flow_name, flow_status, flow_trigger_type, flow_message_name, flow_recipients, flow_open_rate, flow_click_rate, flow_conversions, flow_conversion_value, flow_revenue_per_recipient	Flow audits, step-level drop-off, revenue per flow
Revenue and engagement over time	date, revenue, sent_emails, opens, clicks, unsubscribed, subscribed, total_conversions	Daily and weekly trends, spike detection
Lists and segments	list_name, list_profile_count, segment_name, segment_profile_count, members_count	List growth, segment sizes, engaged versus total
Store events	shopify_placed_order, klaviyo_subscribed_to_email_marketing	Orders and signups as Klaviyo records them
Write actions	create_flow, update_flow_status	Building and switching on flows without leaving Claude

Queried live against Klaviyo’s API, so there is no fixed sync schedule. Full list in the Klaviyo field reference.

Example prompts

Campaign performance

Rank my campaigns from the last 30 days by campaign_report_conversion_value. Show sent_at, campaign_report_recipients, campaign_report_open_rate, campaign_report_click_rate and campaign_report_revenue_per_recipient for the top 10, and tell me which subject lines converted best.

Compare email and SMS campaigns (campaign_channel) for the last 30 days on click rate, conversions and revenue per recipient. Which channel is cheaper per conversion?

Flows

For every live flow (flow_status), show flow_recipients, flow_conversions and flow_conversion_value for the last 30 days. Rank by flow_revenue_per_recipient and flag flows with high volume and low revenue.

Break my abandoned cart flow down by flow_message_name with open rate and click rate per step. Where does the drop-off happen?

Revenue trend

Show campaign_report_conversion_value and flow_conversion_value by date for the last 7 days against the 7 days before. Which days moved, and what was sent?

Lists and segments

List my lists and segments with list_profile_count and segment_profile_count. Which grew or shrank most in the last 30 days?

Cross-channel

Put Klaviyo revenue (campaign and flow conversion value) next to Meta Ads and Google Ads spend by day for the last 30 days. What share of revenue came from email and SMS versus paid?

Compare Klaviyo attributed orders with Shopify orders for the last 30 days. Where is the gap, and which flows or campaigns explain it?

Using GA4, show sessions and purchases from the email channel next to Klaviyo click rates per campaign for the last 30 days. Which campaigns click well but do not convert on site?

Flow building (write actions)

Build a Klaviyo flow triggered by the Placed Order metric: wait 3 days, send the post-purchase-thanks template, wait 4 days, send the leave-a-review template. Save it as a draft.

Set the Black Friday flow to live.

Cross-channel questions to ask next

Whether email revenue is growing faster or slower than Meta Ads and Google Ads spend
Which acquisition channel produces subscribers who open, click and buy
Where Klaviyo attributed revenue and Shopify orders disagree, and why
Which campaigns click well in Klaviyo but convert poorly in GA4

Ready to weigh email against the rest of your channels?

Start for free, or book a demo to see it with your own data.

Start for Free Book a Demo

Method 3

CSV export from Klaviyo

The zero-setup route: export a campaign or flow report from Klaviyo Analytics as a CSV and upload it into a Claude conversation. For a single question about a fixed period, this works on any Claude plan.

What it can do

One-off analysis with no account connection or new tools
Works on any Claude plan, including free
Good enough for a fixed-period question you will not repeat

What it can't do

Stay current, the export is a snapshot that goes stale the moment you download it
Avoid repeat work, every follow-up period means another export and upload
Combine campaigns, flows, lists and revenue in one file, each is a separate export
See other channels unless you export and upload each of them too

How: in Klaviyo, open Analytics, pick the campaign or flow report and date range, export as CSV, then drag the file into Claude and ask your question.

Method 4

Klaviyo API with a custom MCP server

If none of the above cover your workflow (a custom object, an internal approval step, a report shape neither connector produces), you can build your own MCP server against the Klaviyo API and expose it to Claude. Klaviyo also documents its own MCP server for developers who want to self-host or extend it.

This is the heaviest route here: you handle API keys, rate limits and Klaviyo’s API revisions yourself rather than doing a no-code setup.

What it can do

Whatever you build, full flexibility over endpoints, objects and actions
Cover workflows that neither the official connector nor Windsor.ai support

What it can't do

Work without developer effort, there is no no-code path here
Avoid ongoing maintenance, Klaviyo API revisions and keys rotate

Reach for this only when Methods 1 to 3 do not cover your case. It carries build and maintenance cost that the other three do not.

Conclusions: which method wins for your use case

Your situation	Recommended	Why
“I want to know what email and SMS earn against ad spend and store orders”	Windsor.ai	Only method here that spans 350+ sources beyond Klaviyo
“I want Claude to build a flow and switch it on when I approve”	Windsor.ai	Flow creation and status changes with your confirmation
“I want to create campaigns, edit templates and update profiles from chat”	Klaviyo’s official connector	Broadest write access inside Klaviyo
“I just want to ask about my campaigns and flows, no dev work”	Klaviyo’s official connector	Native, no code, on a paid Claude plan
“I have one quick question about last month’s numbers”	CSV export	Fastest path for a true one-off, no account connection needed
“None of the above cover what I need, and I have dev resources”	Custom MCP	Full flexibility, at the cost of build and maintenance effort

FAQs

What are the main ways to connect Klaviyo to Claude?

Four: Klaviyo’s official Claude connector (native, broad read and write inside Klaviyo, paid Claude plan), Windsor.ai (no code, Klaviyo next to 350+ other sources, flow building), a CSV export for a one-off question, and a custom MCP server on the Klaviyo API for developers. The comparison above shows which fits your case.

How is Windsor.ai different from Klaviyo's own Claude connector?

Scope and direction. Klaviyo’s connector works inside Klaviyo: reports, campaigns, templates, profiles, lists, with wide write access. Windsor.ai reads Klaviyo’s report aggregates and puts them next to Meta Ads, Google Ads, GA4, Shopify and your other sources, so Claude can answer what email earns against what you spend. On the write side, Windsor covers flows (create as draft, set draft, manual or live), while Klaviyo’s connector covers campaigns, templates and profiles too. Many teams use both.

Why don't my Klaviyo numbers in Claude match the Klaviyo dashboard?

Usually because Claude summed raw events instead of Klaviyo’s attributed metric aggregates. Klaviyo’s dashboard reports attributed conversions and revenue per campaign and flow. Through Windsor, the campaign_report_* and flow_* fields are those aggregates, so they match. With Klaviyo’s own connector, ask for the campaign report metrics or attributed revenue explicitly rather than order events.

Can Claude create flows in Klaviyo, or only analyze them?

Both, through Windsor.ai. Claude can build a flow from a trigger (a metric event such as Placed Order, or being added to a list) plus a sequence of time delays, emails from existing templates, SMS and conditional splits. The flow is created as a draft and nothing sends until you set it to manual or live. Klaviyo caps flow creation at about 100 per day. The Available actions list above is pulled live from the Windsor.ai API.

What can I do with Klaviyo data in Claude?

The most common uses, in the order teams query them through Claude:

Campaign performance. Recipients, open rate, click rate, conversions and revenue per campaign, email versus SMS.
Flow audits. Revenue per flow, step-level drop-off, live versus draft flows.
Revenue trend. Campaign and flow revenue by day, week over week.
List and segment growth. Profile counts over time.
Cross-channel analysis. Klaviyo revenue against Meta Ads and Google Ads spend, Shopify orders and GA4 conversions.
Flow building. Describe a flow, review the draft, set it live.

What prompts can I use when analyzing Klaviyo data in Claude?

Name the object, the fields and the date range. These follow the shapes teams query most through Claude:

Rank my campaigns from the last 30 days by campaign_report_conversion_value. Show campaign_report_recipients, campaign_report_open_rate, campaign_report_click_rate and campaign_report_revenue_per_recipient for the top 10.

For every live flow, show flow_recipients, flow_conversions and flow_conversion_value for the last 30 days, ranked by flow_revenue_per_recipient.

Put Klaviyo campaign and flow conversion value next to Meta Ads and Google Ads spend by day for the last 30 days. What share of revenue came from email and SMS?

How much does it cost to integrate Klaviyo into Claude using Windsor.ai?

Windsor.ai has a free forever plan, no credit card needed, and the Claude connector is included. Paid plans depend on how many accounts and data sources you connect. See the pricing page for details.

Can I analyze data from multiple Klaviyo accounts at once?

Yes. If you manage several brands, connect each Klaviyo account to Windsor.ai and ask Claude to compare performance across stores or regions in one table.

Can Claude help with RFM (recency, frequency, monetary) analysis?

Yes. With Klaviyo profile and event data, and Shopify orders if connected, Claude can group customers into segments such as champions, loyal, at risk and lapsed, and suggest which flow or campaign should reach each group.

How often does the Klaviyo data refresh in Claude?

Data is fetched from Klaviyo’s API each time you ask, so every answer reflects the latest reported campaign, flow and revenue figures rather than a scheduled snapshot.

Do you have helpful links to get started with integrating Klaviyo and Claude using Windsor.ai?

Yes. You can explore our documentation and available data fields:

Tired of manual Klaviyo data exports? Try Windsor.ai today to automate your reporting

Access your data from various sources in one place. Get started for free.

Start for Free Book a Demo