Claude Klaviyo connectorWhat Claude can do in your Klaviyo account.
The Claude Klaviyo connector exposes 27 tools. 19 read campaigns, flows, lists, metrics and profiles, 8 create or change something in your account, and none is left undescribed. Below: which Klaviyo role you need, what asks first, and where Klaviyo's own docs disagree.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug Klaviyo into Claude
Klaviyo already holds the numbers an email marketer needs: campaign reports, flow performance, metrics, segments and profiles. With the connector, Claude pulls them while it answers you, so a question like "which flows convert best?" gets a reply built on your own account instead of a generic guess. Klaviyo marks every one of its tools as read-only or not, which makes this page unusually precise.
A performance recap without the export. get_campaign_report and get_flow_report return performance for your campaigns and flows, and query_metric_aggregates aggregates event data behind a metric. Ask for last month's winners and Claude reads them live.
An audience check before a send. get_segments, get_lists and get_profiles show who sits where, so Claude can describe a segment before you target it.
A draft campaign, ready for your review. create_email_template saves an HTML template, create_campaign sets up the campaign and assign_template_to_campaign_message attaches one to the other. Nothing on the sheet schedules or sends a campaign.
What it does not do: the directory entry carries 27 of the 260-plus tools Klaviyo publishes, so flows, catalogs and most settings are read here, never edited. It also never reacts on its own when a profile subscribes or an order lands. For that kind of background job, Klaviyo has a Klaviyo Make integration that runs scenarios without anyone in the chat.
Five words before you connect
The vocabulary of Claude connectors, explained once.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector hands to Claude. Claude picks the ones it needs as it answers, and the directory sheet lists them all by name.
- Authorization
- The sign-in screen of Klaviyo itself, where you grant the access Claude will use. It is given once per person and can be withdrawn.
- Approval
- The confirmation Claude waits for before it goes ahead with a change to your account, shown in the conversation when it matters.
- MCP
- The open standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Klaviyo.
Connect the Claude Klaviyo connector in three steps
- 01
Find Klaviyo in your connectors
Open Claude's settings, go to Customize, then Connectors, and look for Klaviyo in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch it on for the organization first.
- 02
Start the connection
Click Connect on the Klaviyo line. Klaviyo opens its own sign-in window: log in to the account you want Claude to work in, since the listed connector links one Klaviyo account.
- 03
Read the permission screen
Klaviyo then shows what the access covers. That screen belongs to Klaviyo, not Claude, and it decides what Claude can reach. Accept it, and use Disconnect later if you want the link gone.
The 27 tools of the Klaviyo connector
Klaviyo gives Claude 27 tools: 19 that read your account, 8 that change something in it.
Klaviyo labels each tool read-only or not in its developer docs, so every tool below has a clear side. Names stay exactly as Claude shows them.
- 19 read
- 8 write
What Claude reads (19)
19 toolsAccount, campaigns, catalog, events, metrics, flows, lists, segments, profiles, reports and templates, consulted without changing them.
get_account_details
Returns the details of the Klaviyo account the connector is linked to. It is the quickest way to confirm which account Claude is looking at before it answers anything else.
get_campaigns
Lists the campaigns in your account, so Claude can see what you have sent or prepared before it digs into any single one of them.
get_campaign
Pulls the details of a single campaign once Claude knows which one you mean, giving it the context it needs to talk about that campaign specifically.
get_catalog_items
Lists the items in your Klaviyo catalog. Claude uses it to know which products it can mention when you ask it for campaign ideas or copy around a product line.
get_events
Lists events recorded in your account, the raw activity Klaviyo tracks for your profiles. It gives Claude the detail behind a trend you noticed in a report.
get_metrics
Lists the event metrics available in your account. Claude reads this list to pick the right metric before it queries anything.
get_metric
Gives the details of a single event metric, so Claude knows exactly what it measures before quoting a figure from it back to you.
query_metric_aggregates
Queries and aggregates the event data linked to a metric. This is where totals and breakdowns come from when you ask Claude a question with a period in it.
get_flows
Lists your flows, the automated sequences you built in Klaviyo. Claude reads the list to see which welcome, abandoned cart or winback sequences exist.
get_flow
Zooms into a single flow and its setup, which lets Claude describe how that sequence works rather than guessing from its name.
get_lists
Returns the lists in your account. Claude uses it to know where subscribers are collected before it talks about audience growth or targeting.
get_list
Shows the details of one list, giving Claude what it needs to discuss that audience precisely instead of the whole account at once.
get_segments
Lists your segments. Claude reads them to suggest who a campaign could target.
get_segment
Fetches the details of a single segment, so Claude can explain what defines it and whether it matches the audience you have in mind.
get_profiles
Lists the profiles in your account, the people Klaviyo knows about. Claude reads it when a question is about who is in the account rather than what they did.
get_profile
Fetches one profile with its details, giving Claude the full picture of a customer when you ask about them by name or email.
get_campaign_report
Produces a report of your campaign performance. Claude reads it to answer comparison questions with your real figures rather than benchmarks.
get_flow_report
Returns a report of flow performance, the counterpart of the campaign report for your automated sequences. Claude uses it to rank flows by the outcome you care about.
get_email_template
Retrieves the details of an email template, so Claude can review its content or reuse its structure when drafting something new with you.
What Claude creates or changes (8)
8 toolsCampaigns, templates, images and profiles, including marketing consent. No source describes a confirmation specific to these tools: the general rule below applies.
create_campaign
Approval: see the ruleSets up a new campaign in your account. Klaviyo gives this very request as an example: a campaign promoting a seasonal sale.
assign_template_to_campaign_message
Approval: see the ruleAssigns an email template to a campaign message, linking the design to the send you prepared.
upload_image_from_url
Approval: see the rulePulls an image from a web address into your Klaviyo account, so it can be used in your emails afterwards.
create_profile
Approval: see the ruleAdds a new profile to your account, a person Klaviyo will then know about.
update_profile
Approval: see the ruleChanges the details of an existing profile, such as correcting a property that was wrong.
subscribe_profile_to_marketing
Approval: see the ruleSubscribes a profile to marketing for a given channel and list, which changes whether that person receives your campaigns.
unsubscribe_profile_from_marketing
Approval: see the ruleRemoves a profile's marketing subscription for a given channel and list, so they stop receiving those campaigns.
create_email_template
Approval: see the ruleSaves a new HTML email template in your account, which is how a design Claude drafted with you lands in Klaviyo.
What Claude checks with you first
By default, Claude stops and asks before each action it carries out on an account for someone, right in the conversation.
No source describes a confirmation specific to the eight Klaviyo tools that create or change something, so this default rule is what applies to them. On Team and Enterprise, workspace owners decide whether members may let some actions through without being asked every time, and they can limit what a connector does for the whole organization, for example keeping reads and closing writes. Nobody lifts that from their own account. Claude also works with the rights of the person who connected, nothing more: what your Klaviyo role cannot reach, Claude cannot reach either.
Which Claude plans it runs on
None of the 819 directory sheets states availability by plan, and no official source publishes it connector by connector.
The published rule is general: remote connectors like this one are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns a connector on for the organization before members can connect. For the current state of Klaviyo, open its sheet in the official directory. Klaviyo's docs name plans for another route; see the limits below.
Limits of the Claude Klaviyo connector
A connector is not an automation: Claude calls these tools while it answers you, and nothing fires on its own when a profile subscribes or an order arrives.
Everything here comes from the directory sheet and from Klaviyo's developer documentation: neither Claude's help center nor Anthropic's developer docs have a page on this connector. The verification badge is not a security audit, and Anthropic states on every sheet that it does not control the tools a publisher exposes. If you need something the chat cannot give you, the Integrations hub lists the automation pages for your other apps.
Does the Klaviyo connector need a particular Claude plan?
- Claude help center, general connector rule ↗2026-09-18Web connectors are available to all users on Claude, Cowork, Claude Desktop and Claude Mobile; on Team and Enterprise an Owner or Primary Owner enables them first.
- Klaviyo developer docs, connecting to the server ↗2026-09-29The custom connector route is only available on Claude and Claude Desktop for users on Pro, Max, Team and Enterprise plans.
What this page followsThey do not describe the same thing. Klaviyo's sentence is about the custom connector route, not the directory connector, and Anthropic's rule covers all web connectors. Neither tells you the state of your own account: check the directory sheet on your account.
Need help connecting Klaviyo to Claude?
A person reads every message.
