To connect Klaviyo to Claude, authorize your account at onboard.windsor.ai/app/klaviyo and add the Windsor.ai connector in Claude. From there, start a new chat and ask about your campaigns and flows.
Here’s what that limits:
Klaviyo knows more about your subscribers than almost any other tool in your stack: every campaign sent, every flow trigger, every purchase, every subscriber who opened once and vanished.
But Klaviyo’s dashboard shows you one report at a time. It won’t tell you whether email revenue is growing faster or slower than your paid spend, which flows are earning their keep versus running on autopilot, or what your real engaged list size is once you strip out the dead weight. Getting those answers means exporting CSVs and rebuilding the same spreadsheet every time someone asks a different question.
Here’s the fix: connect Klaviyo to Claude with Windsor.ai, and analyze all of it in plain language: campaigns, flows, lists, and subscriber behavior across your entire sending history, not one report at a time.
π Connect Klaviyo to Claude with Windsor MCP. Free forever plan, no credit card β onboard.windsor.ai/app/klaviyo
Connecting Klaviyo to Claude with Windsor: 2 steps
No code, no exports. The whole setup runs through the native Windsor.ai connector for Claude.
π Full documentation: How to integrate data into Claude with Windsor MCP.
Before you start
- A Klaviyo account with Owner, Admin, or Manager role (needed to authorize API access)
- A Windsor.ai account: free forever plan or paid plan
- A Claude account
Step 1 β Connect Klaviyo to Windsor
Go to onboard.windsor.ai/app/klaviyo and select Klaviyo as your data source. Authenticate with your Klaviyo account and authorize the connection. Windsor confirms it and starts pulling your campaign, flow, list, and subscriber data.
Step 2 β Add the Windsor.ai connector in Claude
In Claude, go to Settings β Connectors, search for Windsor.ai, and add it from the Claude directory β one click, no URL to paste. Set permission to “Always allow” so your Klaviyo data is live in every conversation automatically.
Confirm the connection with a quick test prompt:
List the data sources connected to my Windsor account. Do you see Klaviyo there?
New: build and launch Klaviyo flows without leaving the chat
Windsor’s Klaviyo connector isn’t read-only anymore. From the same Claude conversation, you can now ask it to build a real flow: pick a trigger (a metric event, like a purchase, or being added to a list), then chain the steps β wait a set amount of time, send an email from one of your existing templates, send an SMS, or branch profiles down different paths based on a condition.
Every flow Windsor creates lands in Klaviyo as a draft β nothing sends until you say so. When you’re ready, ask Claude to turn it on (live), or set it to manual so messages wait for a human to review before going out. You stay in control of every send.
Build a Klaviyo flow triggered by the "Placed Order" metric. Step 1: wait 3 days. Step 2: send the "post-purchase-thanks" email template. Step 3: wait 4 more days. Step 4: send the "leave-a-review" email template. Create it as a draft so I can review it before it goes live.
Worth knowing: Klaviyo rate-limits flow creation to about 100 per day, and this covers flow building and activation specifically β not campaign sends, profile edits, or list management. Everything else about the Klaviyo connection stays read-and-analyze.
The metrics that matter
| Klaviyo data | What Claude can answer with it |
| Campaigns | Cross-campaign performance trends, revenue per campaign, send-time patterns, campaign type comparison |
| Campaign metrics | Delivered, opened, clicked, bounced, unsubscribed β per send and rolled up across any date range |
| Flows & automations | Flow- and step-level performance, drop-off rates, revenue per flow, welcome vs. abandoned-cart vs. win-back comparison |
| Lists & segments | List size trends, segment engagement rates, subscriber count over time |
| Subscribers & profiles | Engagement recency, activity decay, list health scoring |
| Revenue per recipient (RPR) | Revenue tied to each campaign and flow, normalized for list size β the cleanest effectiveness measure Klaviyo has |
| Unsubscribes & bounces | Unsubscribe trends by campaign type, bounce patterns, list quality signals |
| A/B test results | Subject line and send-time test outcomes, content variant performance |
What to ask Claude: prompt ideas
π€ More prompt ideas across all data sources: windsor.ai/prompt-library/
Campaign performance
Using Klaviyo campaign data for the last 6 months, rank all campaigns by revenue per recipient (RPR). Show campaign name, send date, open rate, click rate, RPR, and unsubscribe rate for the top 10. Which campaigns convert efficiently regardless of list size? Which had strong open rates but low revenue β high engagement, low purchase intent?
Flow diagnostics
For all active Klaviyo flows, show total emails sent, attributed revenue, and revenue per recipient over the last 90 days. Rank by revenue per recipient descending. Which flow is the strongest revenue driver? Which has high volume but negligible revenue β a candidate for a rethink?
List health
Segment my full Klaviyo list by engagement recency: Active (engaged in 90 days), Cooling (90-180), Cold (180-365), Dormant (12+ months). Show subscriber count and % of total for each segment. If I removed Cold and Dormant subscribers, how would my list-level open rate change?
Bonus: analyze Klaviyo alongside your full stack
| Integration | Core objective | Key question for Claude |
| Klaviyo + Shopify/WooCommerce | Reconcile email revenue against real orders | “Compare Klaviyo’s revenue per recipient against actual Shopify order data by email address. Where’s the gap?” |
| Klaviyo + Google Ads/Meta Ads | Find which channels bring subscribers who buy | “Which acquisition channel produces subscribers with the highest open rate and 180-day LTV?” |
| Klaviyo + GA4 | See what happens after the click | “Which campaigns have strong click rates but poor post-click conversion in GA4?” |
Conclusion
Klaviyo’s dashboard tells you what happened, one send at a time. Windsor MCP turns your full sending history into a live dataset you can question in plain language β and now, with flow creation and activation built in, you can act on what you find without switching tools.
π Connect Klaviyo to Claude with Windsor MCP. Free forever plan, no credit card β onboard.windsor.ai/app/klaviyo
FAQs
What is the easiest way to connect Klaviyo to Claude?
Go to onboard.windsor.ai/app/klaviyo, connect your Klaviyo account, then add Windsor.ai from Claude’s connector directory. Both steps are one click each β no code, no CSVs.
Is Windsor's Klaviyo connection read-only, or can it make changes in Klaviyo?
Both. Windsor reads and analyzes all of your Klaviyo campaign, flow, list, and subscriber data. It can also build new Klaviyo flows (trigger plus a sequence of wait/email/SMS/branch steps) and change a flow’s status between draft, manual, and live β directly from a Claude conversation. Every flow starts in draft, so nothing sends until you say so.
Does Windsor need Klaviyo Admin access?
Windsor recommends connecting with an Owner, Admin, or Manager role, consistent with Klaviyo’s own requirement for API access. A Viewer role may have restricted API access depending on your plan.
Can Windsor blend Klaviyo data with Shopify or my ad platforms in Claude?
Yes. Connect Klaviyo alongside Shopify, Google Ads, Meta Ads, GA4, or any of Windsor’s 350+ sources, and ask Claude to analyze them together in one conversation β no manual joins required.
Windsor vs Coupler.io

