A Klaviyo MCP that sits on the same canvas as everything else you run
Connect one private API key and 49 Klaviyo operations become workflow steps that chain with every other connector, so a ticket in your helpdesk, a deal in your CRM, and a profile in Klaviyo can move together without glue code. Flat typed fields go in, the connector assembles Klaviyo's JSON:API bodies, and the nodes that send real email or change someone's consent say so on the label.
What the Klaviyo MCP connector does
The Klaviyo connector for Mattering Automations is 49 nodes, 28 reads and 21 writes, covering metrics and account details, raw events, profiles, consent and suppression, lists, segments, campaigns, flows, templates, tags, the product catalog, and the campaign, flow, and segment performance reports. Klaviyo's stable surface is roughly 200 operations, so this is a curated set rather than a dump: three families were cut by shape, not importance. The JSON:API relationships accessors return bare ids the full read nodes already give you, the bulk job lifecycles need a submit, poll, and read errors pattern this connector does not have yet, and the sub resource CRUD that exists to support the Klaviyo UI does not carry an automation loop.
Klaviyo's real request bodies are nested envelopes, and the connector hides them. A write body in Klaviyo looks like a data object wrapping a type, an id, an attributes block, and a relationships block; here you fill flat fields such as name, subject, from address, and included audiences, and the connector assembles that structure. You never type a resource type string into a config panel. Responses are still JSON:API shaped, which the sample outputs show honestly: the real drag path is data.data[0].attributes.name, not data.data[0].name, so the paths you wire are right before you ever run the node.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP capable assistant can use them, alongside Matter, the AI assistant built into the platform. Klaviyo also runs its own official remote MCP server, and it is good at what it does. The difference here is placement rather than coverage: these nodes live next to every other connector on one canvas, so an agent or a scheduled workflow can read a support ticket, look up the profile, record an event, and open a task in Mattering Productivity in a single flow instead of stitching two systems together.
The risk model is stated plainly rather than hidden. Exactly one node in the connector destroys data: Klaviyo: Merge Profiles (Permanently Deletes the Source), which Klaviyo documents as deleting the source profile, with no unmerge. Everything else is reversible, or is an outbound and consent caution: Klaviyo: Send Campaign (Sends Real Email or SMS) and Klaviyo: Update Flow Status (Live Sends Real Messages) start real messaging at scale, and Klaviyo: Subscribe Profiles (Grants Marketing Consent) and Klaviyo: Unsubscribe Profiles (Revokes Marketing Consent) write consent records. Suppression is genuinely reversible and ships as a pair. Those five nodes carry the warning in the label so a person reading the canvas sees it without opening anything.
One connection, three surfaces
- Visual automations. Drag Klaviyo nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Klaviyo node, ready to drop on the canvas
49 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 28
Klaviyo: Campaign Performance Report
Campaign analytics that match Klaviyo's own dashboard: opens, clicks, conversions, revenue, unsubscribes and rates, over a timeframe, grouped however you like. A POST because the query rides in the body; it reads and changes nothing. Results come back as one row per grouping, each with a groupings object and a statistics object. Rate limited hard by Klaviyo (about 1 per second, 2 per minute and 225 per day across the reporting endpoints), so treat it as a scheduled report, not a per record lookup.
Klaviyo: Flow Performance Report
Flow analytics that match Klaviyo's own dashboard: how the welcome series, abandoned cart and win back flows are actually performing, with opens, clicks, conversions and revenue over a timeframe. Reads and changes nothing. Group by flow_id or flow_message_id to see which step in a series is carrying the results. Rate limited hard by Klaviyo (about 1 per second, 2 per minute and 225 per day across the reporting endpoints), so treat it as a scheduled report, not a per record lookup.
Klaviyo: Get Account Details
Read the account the connected private key belongs to: organization name, default sender name and email, website, industry, timezone, preferred currency and locale. Klaviyo returns exactly one account object in the array. Useful for stamping currency or timezone onto downstream records, and for confirming an automation is pointed at the right Klaviyo account before it does anything. Note that Klaviyo also returns attributes.public_api_key here, which is the public site id embedded in your onsite tracking script, not the private key; even so, avoid piping this node's raw output into logs or third party systems. Needs the accounts:read scope, and is rate limited to about 1 per second and 15 per minute, so call it once and reuse the result.
Klaviyo: Get Campaign
Fetch one campaign by id: its status, included and excluded audiences, send strategy, send options and timestamps. Always run this immediately before Klaviyo: Send Campaign and check attributes.audiences against what you expect. The audiences array is the list of people who will actually receive the email, and it is the field most likely to be wrong.
Klaviyo: Get Campaign Recipient Estimate
Read the estimated number of recipients for a campaign: data.data.attributes.estimated_recipient_count. This is the number you gate a send on. Wire it into a condition before Klaviyo: Send Campaign so an automation refuses to fire when the count is zero (broken audience) or wildly larger than expected (a segment rule change). Refresh it first with Klaviyo: Refresh Campaign Recipient Estimate if the audience has changed recently.
Klaviyo: Get Event
Fetch a single event by id, including its full event_properties payload and its links to the profile and metric. Use it to expand one row returned by Klaviyo: List Events, or to resolve an event id received from an upstream node.
Klaviyo: Get Flow
Fetch one flow by id, with its current status and trigger type. The check to run before and after Klaviyo: Update Flow Status, and the way an automation can assert that a critical welcome or abandoned cart flow is still live.
Klaviyo: Get List
Fetch one list by id: name, timestamps, and its opt in process (single or double). Set additional_fields_list to profile_count to also get the number of people on it, which is the cheapest way to answer "how many humans am I about to email" before a send. Note that asking for profile_count drops the call into a much lower rate limit bucket (about 1 per second, 15 per minute), so read it once per run rather than in a loop.
Klaviyo: Get Lists for Profile
List the list memberships of one profile. The safety check in front of Klaviyo: Unsubscribe Profiles, which globally unsubscribes anyone who is not on the list you name, so confirming membership first is the difference between removing someone from a newsletter and cutting them off from all your marketing. Rate limited to about 3 per second and 60 per minute.
Klaviyo: Get Messages for Campaign
List the messages that belong to a campaign, with their definition (channel, label, subject, from address) and the template attached to each. Use it to read back what a draft will actually say, or to get a campaign message id for further work. Include the template to inspect the rendered content source in the same call.
Klaviyo: Get Profile
Fetch one profile by its Klaviyo id, including identifiers, name, location, and custom properties. Set additional_fields_profile to subscriptions when you need the person's current consent state per channel, which is the honest way to check whether you may email them before an automation does. Output contains personal data and is stored in the execution record.
Klaviyo: Get Profiles for List
Page through the profiles on a list. Use it to export members into another system, to check whether a specific address is on the list before unsubscribing it, or to size an audience before a send. Output is personal data and is stored in the execution record, so page deliberately rather than dumping a large list into an automation run. Returns at most 100 profiles per page.
Klaviyo: Get Profiles for Segment
Page through the profiles currently matching a segment. Segments are dynamic, so this is a snapshot, not a stable list. Useful for syncing a computed audience into another system or for spot checking who a campaign would reach. Output is personal data and is stored in the execution record. Returns at most 100 profiles per page.
Klaviyo: Get Segment
Fetch one segment by id, including its condition definition and whether it is currently processing. Set additional_fields_segment to profile_count to get the current member count, which is the pre send sanity check for any campaign targeting this segment: a rule change can quietly turn a 200 person segment into a 200,000 person one. Asking for profile_count lowers the rate limit to about 1 per second, so read it once per run.
Klaviyo: Get Template
Fetch one template by id, including its HTML and plain text source. Useful for archiving a template into version control or diffing it before a change. The html attribute is a full email document, so this node's output can be a large text value in the execution record.
Klaviyo: List Campaigns
List campaigns with their status, audiences, send strategy and timestamps. Klaviyo REQUIRES a channel filter on this endpoint, so the filter field is pre-filled with the email channel; swap it for sms or mobile_push, or combine it with a status filter to find, say, every draft. Returns at most 100 campaigns per page.
Klaviyo: List Catalog Categories
List the catalog's categories, the groupings used to filter products in recommendation and product feed blocks. Returns each category's external id, name and composite Klaviyo id. Use a category id with Klaviyo: List Catalog Items to pull everything in one department. Returns at most 100 categories per page.
Klaviyo: List Catalog Items
List products in the Klaviyo catalog, the data behind product blocks, back in stock alerts and abandoned browse content. Returns title, description, price, URLs, images, custom metadata and published state. Filter by category or title to find the item id (a composite such as $custom:::$default:::SKU-1) that other catalog features need. Returns at most 100 items per page.
Klaviyo: List Events
List raw events recorded in the account: orders, product views, email opens, custom activity. Filter by metric, by profile, or by a datetime window to pull a feed of recent activity into an automation. Each event carries its event_properties payload, its timestamp, and links to the metric and profile behind it. Event bodies contain personal and order data and are stored in the execution record, so filter tightly and keep page_size small rather than pulling the whole history. Returns at most 200 events per page.
Klaviyo: List Flows
List the account's automated flows with their name, status (draft, manual or live), trigger type and timestamps. This is the node that tells you which automations are armed: filter on equals(status,"live") before pushing events or list additions in bulk, because a live flow turns those writes into real outbound messages. Rate limited to about 3 per second and 60 per minute; returns at most 50 flows per page.
Klaviyo: List Lists
List the account's lists (Klaviyo's static, consent bearing audiences) with their names, creation dates and opt in process. This is how you turn a human readable list name into the list id that every other list node, the subscribe nodes and campaign audiences require. Returns at most 10 lists per page, so paginate with page_cursor on accounts with many lists.
Klaviyo: List Metrics
List every metric in the Klaviyo account: the event types Klaviyo knows about, such as Placed Order, Viewed Product, Opened Email, or any custom event your integrations send. Returns each metric's id, name, created and updated timestamps, and the integration that owns it. Metric ids are the input to Query Metric Aggregates and to the conversion_metric_id on the reporting nodes, so this is usually the first call in a Klaviyo automation. It is also the connector's credential health check: it needs no configuration, only the metrics:read scope, and its response contains no key or account secret of any kind. Returns at most 200 metrics per page.
Klaviyo: List Profiles
List profiles in the account, or look one up by email, phone number or external id using a filter. The everyday use is resolving an address to a Klaviyo profile id: filter on equals(email,"jane@example.com") and read data.data[0].id. Output contains personal data (names, addresses, custom properties) and is stored in the execution record, so filter to the profiles you need instead of paging the whole account. Returns at most 100 profiles per page.
Klaviyo: List Segments
List the account's segments: the dynamic, rule based audiences that recompute as profile data changes. Returns each segment's name, definition summary, and whether it is active or still processing. Use it to resolve a segment name to the id that campaign audiences and the suppression nodes need. Returns at most 10 segments per page.
Klaviyo: List Tags
List the account's tags, the labels used to organize campaigns, flows, lists and segments. Include the tag group to see how they are categorized, or the related resources to see what each tag is applied to. Handy for reporting: pull every campaign carrying a given tag and roll up its performance. Returns at most 50 tags per page; an account can hold at most 500 tags.
Klaviyo: List Templates
List the account's email templates with their names, editor type and timestamps. Use it to resolve a template name to the id that Klaviyo: Render Template needs. Note that template HTML can be large, so leave additional_fields_template blank unless you actually need the drag and drop definition.
Klaviyo: Query Metric Aggregates
Aggregate the events behind one metric into counts, sums or unique profile counts over time, optionally grouped by dimensions such as message, flow, campaign name or email domain. This is the raw event analytics endpoint: revenue by week from Placed Order, opens by message, signups by day. It is a POST because the query rides in the body, but it reads and changes nothing. For numbers that match the campaign and flow dashboards in Klaviyo's own UI, use the reporting nodes instead. Results are returned as parallel arrays: data.data.attributes.dates lines up with each row's measurement arrays.
Klaviyo: Segment Growth Report
Segment membership analytics: total members, members added, members removed and net change over a timeframe. Reads and changes nothing. This is the audience health report: a segment shrinking week over week, or a suppression heavy list, shows up here before it shows up in campaign performance. Note that this endpoint takes no conversion_metric_id, unlike the campaign and flow reports. Rate limited hard by Klaviyo (about 1 per second, 2 per minute and 225 per day across the reporting endpoints), so treat it as a scheduled report, not a per record lookup.
Action nodes 21
Klaviyo: Add Profiles to List
Add existing profiles to a list by profile id. This is membership only: Klaviyo is explicit that it does NOT grant marketing consent, so use Klaviyo: Subscribe Profiles when you need consent as well. Reversible with Klaviyo: Remove Profiles from List. One caution: if a live flow is triggered by "Added to List" on this list, adding profiles will make that flow send real messages, so check List Flows before pointing a bulk import at a list with a welcome series on it. Maximum 1000 profiles per call. Returns 204 with an empty body.
Klaviyo: Cancel or Revert Campaign Send
The emergency stop for a sending or scheduled campaign. Action `cancel` permanently cancels it (status becomes Cancelled); action `revert` puts it back to Draft so it can be fixed and sent again. This node ships as a Reversible Write on purpose: it is the safety control, and blocking it behind a warning would be backwards. Understand its limit though: it stops what has not gone out yet. Messages already delivered stay delivered.
Klaviyo: Create Back in Stock Subscription
Register one person to be notified when a specific product variant is back in stock. Nothing is sent right now: the message goes out later, once, when Klaviyo sees the variant restocked, so this is a single opt in request rather than a broadcast. Still a real future message to a real person, so only register people who asked. This is the server side endpoint; a public storefront widget should use Klaviyo's client side variant instead of exposing a private key. Returns 202 when accepted.
Klaviyo: Create Campaign (Draft)
Create a campaign as a DRAFT. Nothing is emailed by this node. You give it a name, the audiences to include and exclude, and the message basics (subject, preview text, from address and label), and Klaviyo returns a campaign you can inspect, attach a template to, and only then send. Klaviyo's real request body nests a campaign-messages array inside attributes, with the definition, channel and content objects several levels down; you fill flat fields here and the connector assembles that envelope. Anything exotic (SMS definitions, smart send time, throttled sends, tracking options) goes through extra_attributes.
Klaviyo: Create List
Create a new, empty list. Nothing is emailed by this node. The opt in process you choose here is consequential later: a double opt in list makes Klaviyo: Subscribe Profiles send a confirmation email to every address, while a single opt in list subscribes them outright. Klaviyo caps list creation at about 150 per day, so this is not a per record node. The connector builds the JSON:API envelope from the flat fields below.
Klaviyo: Create Tag
Create a tag so campaigns, flows, lists and segments can be grouped and reported on consistently. Nothing is emailed by this node. If you do not name a tag group, Klaviyo puts the tag in the account's default group. Accounts are capped at 500 unique tags, so generate them from a controlled vocabulary rather than per record. Needs both tags:read and tags:write on the key.
Klaviyo: Create Template
Create a new email template from HTML. Nothing is emailed by this node; a template is content, not a send. Useful for generating templates from a CMS, a design system or an AI step and pushing them into Klaviyo for a human to review. Klaviyo caps templates created through the API at 1,000 per account, so this is not a per record node. Klaviyo template syntax is Django like, so {{ first_name }} style variables in your HTML survive intact; preview the result with Klaviyo: Render Template before attaching it to anything that sends.
Klaviyo: Create or Update Profile (Upsert)
The profile sync workhorse: create a profile if it does not exist, update it if it does, matched on the identifier you pass. Returns 201 when a profile was created and 200 when an existing one was updated. Nothing is emailed by this node, and it does NOT grant marketing consent: a profile created here is a contact record, not a subscriber. Use Klaviyo: Subscribe Profiles for consent. Careful with clearing: omitting a field leaves it unchanged, but sending it explicitly empty clears it. Maximum payload 100KB. You supply flat fields; the connector builds the JSON:API profile envelope.
Klaviyo: Merge Profiles (Permanently Deletes the Source)
DESTRUCTIVE AND IRREVERSIBLE. Merges a source profile into a destination profile and, in Klaviyo's own words, DELETES the source profile in the process. Event history, list memberships and properties are consolidated onto the destination according to Klaviyo's merge rules, and there is no unmerge. Use it only for genuine duplicate cleanup, where you have already read BOTH profiles with Klaviyo: Get Profile, confirmed they are the same human, and decided which one survives. The merge runs as an asynchronous job, so a 201 means accepted, not finished. Accepts exactly one source profile per call.
Klaviyo: Refresh Campaign Recipient Estimate
Kick off an asynchronous job that recalculates how many people a campaign would reach. Nothing is emailed by this node and nothing about the campaign changes. Run it, wait a moment, then read the number with Klaviyo: Get Campaign Recipient Estimate. This pair is the documented safe path before a send: know the audience size before you commit. Returns 202 when the job is accepted.
Klaviyo: Remove Profiles from List
Remove profiles from a list. Nothing is deleted: the profiles keep existing, keep their event history, and Klaviyo documents that their consent and subscription status are unchanged. They simply stop receiving marketing sent to this particular list. This is the correct node when you want to take someone off one audience without touching their global consent, and it is reversible with Klaviyo: Add Profiles to List. Maximum 1000 profiles per call. Returns 204 with an empty body.
Klaviyo: Render Template (Preview, Sends Nothing)
Render a template with sample data and get back the HTML, plain text and AMP versions. NOTHING IS SENT and nothing is changed: this is the preview step in the safe send path. Pass the variables your template expects in `context` and check that merge tags resolve, that no placeholder leaks through, and that the copy reads correctly, all before a campaign goes near a real audience. Klaviyo renders with Django like syntax, and variables with no matching context value are treated as false rather than erroring, which is exactly how a broken personalization ships silently. Output includes full email HTML, so it is a large text value.
Klaviyo: Send Campaign (Sends Real Email or SMS)
SENDS THE CAMPAIGN TO ITS ENTIRE AUDIENCE FOR REAL, AND THERE IS NO UNDO ONCE MESSAGES LEAVE. Every profile in the campaign's included audiences, minus the excluded ones, receives the email or SMS. Delivered mail cannot be recalled; the only stop is Klaviyo: Cancel Campaign Send, and it only helps while the job is still queued or in flight. Run the safe path first, every time: (1) Klaviyo: Get Campaign and read attributes.audiences, (2) Klaviyo: Refresh Campaign Recipient Estimate then Klaviyo: Get Campaign Recipient Estimate and check the count is what you expect, (3) Klaviyo: Get Messages for Campaign and confirm the subject and from address, (4) preview the rendered body with Klaviyo: Render Template, (5) send a real proof to yourself by pointing a copy of the campaign at a one person list you own. Only then run this node. Because there is no per node dry run, an automation that reaches this node on a bad trigger has already mailed everyone. Returns 202 with a send job you can poll.
Klaviyo: Subscribe Profiles (Grants Marketing Consent)
RECORDS MARKETING CONSENT FOR REAL PEOPLE, AND CAN SEND REAL EMAIL. This node writes an opt in record: if the target list uses double opt in, Klaviyo immediately emails every address you pass asking them to confirm; if it uses single opt in, they are subscribed outright and your next campaign reaches them. Consent you did not actually collect is a legal problem, not just a data problem, and there is no clean undo: unsubscribing does not restore the previous state, it records a second consent event. Only feed this node addresses that opted in through a form or checkout you control, and put the provenance in custom_source so the record is auditable. Use historical_import only for consent already collected outside Klaviyo, with its original timestamp. To add someone to a list WITHOUT changing consent, use Klaviyo: Add Profiles to List instead. Runs as an asynchronous job; 202 means accepted. Maximum 1000 profiles per call.
Klaviyo: Suppress Profiles
Stop email marketing reaching specific addresses, independent of their consent status: a suppressed profile receives no email marketing even if it is subscribed. Use it for complaint handling, competitor addresses, or role accounts you never want mailed. This is the REVERSIBLE half of a documented pair: Klaviyo: Unsuppress Profiles clears suppressions created here (reason USER_SUPPRESSED). It does not delete anything and it does not change consent records. Suppress either an explicit list of email addresses, or everyone currently in a list or segment. Maximum 100 email addresses per call; runs as an asynchronous job, so 202 means accepted.
Klaviyo: Track Event
Record activity against a profile: a purchase, a signup, a support ticket, any custom event you want Klaviyo to segment and trigger on. Klaviyo creates the metric on first use if it does not exist yet, and creates or updates the profile from the identifiers you pass, so this one node covers the whole tracking path. Two things to know before wiring it into a loop. First, if a LIVE flow is triggered by this metric, sending the event will make Klaviyo send real email or SMS to that profile: check List Flows for a live flow on the metric before pointing a high volume automation at it. Second, events cannot be deleted through the API, so a mistaken backfill stays in the account's history; set unique_id when replaying so retries deduplicate. You supply flat fields and the connector builds Klaviyo's nested JSON:API event envelope for you. Returns 202 with an empty body when accepted for processing.
Klaviyo: Unsubscribe Profiles (Revokes Marketing Consent)
REVOKES MARKETING CONSENT, AND CAN DO IT GLOBALLY. Klaviyo documents the trap plainly: any profile you pass that is NOT a member of the list you name is unsubscribed from ALL of your marketing on that channel, not just from that list. Check membership first with Klaviyo: Get Lists for Profile. Consent cannot be restored programmatically once revoked; re subscribing requires a fresh, genuine opt in. If you only want to take someone off a list while leaving their consent intact, use Klaviyo: Remove Profiles from List instead, which the docs confirm does not touch subscription status. Runs as an asynchronous job; 202 means accepted. Maximum 1000 profiles per call.
Klaviyo: Unsuppress Profiles
Lift manual suppressions so email marketing can reach these addresses again. The documented undo for Klaviyo: Suppress Profiles. Important limit: it only clears suppressions with reason USER_SUPPRESSED. Profiles that unsubscribed themselves, or that Klaviyo suppressed for INVALID_EMAIL or HARD_BOUNCE, are deliberately left alone, so this node cannot be used to mail someone who opted out or whose address is dead. Maximum 100 email addresses per call; runs as an asynchronous job, so 202 means accepted.
Klaviyo: Update Campaign
Update a draft campaign: rename it, change who it targets, or change its send strategy. Nothing is emailed by this node. Be aware that the audience arrays REPLACE the existing ones rather than adding to them, so send the complete list you want, and re-read the campaign afterwards with Klaviyo: Get Campaign to confirm the audience is what you intended before any send.
Klaviyo: Update Flow Status (Live Sends Real Messages)
SETTING A FLOW LIVE ARMS AUTOMATED OUTBOUND MESSAGING. From that moment every profile that meets the trigger receives real email or SMS, with no further human step, for as long as the flow stays live. Klaviyo applies the status to the flow AND to all of its actions. Messages already sent cannot be recalled, which is why this is not a routine write, even though flipping the status back to draft or manual does stop future sends. Before setting a flow live: read it with Klaviyo: Get Flow, confirm the trigger is what you think it is, and confirm the content has been reviewed. Setting a flow to draft or manual is the safe direction and is what you should automate if you automate anything here (for example, pausing a promotional flow during an incident). Rate limited to about 3 per second and 60 per minute.
Klaviyo: Update Profile
Update an existing profile by id. Only the fields you fill are sent, so untouched attributes keep their current values. Sends no email and grants no consent. Use Klaviyo: Create or Update Profile (Upsert) when you are not sure the profile exists yet, or when you want to match on email rather than id. Custom properties in `properties` are merged key by key, not replaced wholesale.
Connecting Klaviyo takes one credential
Klaviyo issues private API keys from the account settings in the Klaviyo app, under API keys. A private key starts with pk_ and is one opaque value. The header Klaviyo actually wants is Authorization: Klaviyo-API-Key followed by the key, which is neither Bearer nor Basic, and the connector builds that header itself, so the credential form is a single field holding the key. Keys are scoped when they are created and cannot be re-scoped afterwards, so pick Read Only, Full Access, or a custom per resource set that matches what your automations will actually do.
In Klaviyo, open account settings, go to API keys, and create a private key. Read Only is enough for all 28 read nodes, and the metrics read that the connection test uses needs only the metrics:read scope. Write nodes need the matching write scopes.
In Mattering Automations, open Connectors, click Add Connector, choose Klaviyo, and paste the pk_ value into the single credential field. Do not paste a header name or a prefix; the connector adds the Klaviyo-API-Key scheme for you.
Click Test Connection. Mattering calls Klaviyo's metrics endpoint with the pinned API revision and confirms the key authenticates. That endpoint was chosen partly for safety: it returns event type definitions and no key material of any kind.
All 49 Klaviyo nodes appear in the canvas palette. Run Klaviyo: List Metrics first, because metric ids are the input to Klaviyo: Query Metric Aggregates and to the conversion metric on the reporting nodes.
Common uses for the Klaviyo MCP
Profile sync without hand building JSON:API
Klaviyo: Create or Update Profile (Upsert) creates a profile if it does not exist and updates it if it does, matched on the identifier you pass, and Klaviyo: Update Profile edits one by id. Both take flat fields, and the connector builds the nested profile envelope. Klaviyo: List Profiles resolves an email address to a profile id, which is the lookup most workflows start with. None of these grant marketing consent: a profile created here is a contact record, not a subscriber.
Events that feed segmentation and triggers
Klaviyo: Track Event records a purchase, a signup, a support escalation, or any custom activity against a profile, creating the metric on first use and creating or updating the profile from the identifiers you pass. Klaviyo: List Events and Klaviyo: Get Event read activity back out. One thing to check first: if a live flow is triggered by that metric, the event makes Klaviyo send real messages, so read Klaviyo: List Flows before pointing a high volume automation at it.
List membership without touching consent
These are two different actions and Klaviyo treats them as such. Klaviyo: Add Profiles to List is membership only and grants no consent, and Klaviyo: Remove Profiles from List takes someone off one audience while leaving their subscription status untouched. Klaviyo: Subscribe Profiles (Grants Marketing Consent) is the one that writes an opt in record, and on a double opt in list it emails every address you pass. Use the membership nodes unless you actually collected consent.
A campaign send with a real pre flight
Klaviyo: Create Campaign (Draft) builds the campaign and emails nobody. Klaviyo: Get Campaign reads back attributes.audiences, the field most likely to be wrong, Klaviyo: Get Messages for Campaign confirms the subject and from address, and Klaviyo: Refresh Campaign Recipient Estimate followed by Klaviyo: Get Campaign Recipient Estimate gives you the audience size to gate on. Only then does Klaviyo: Send Campaign (Sends Real Email or SMS) run.
Scheduled reporting that matches the Klaviyo dashboard
Klaviyo: Campaign Performance Report, Klaviyo: Flow Performance Report, and Klaviyo: Segment Growth Report return opens, clicks, conversions, revenue, and membership change over a timeframe, grouped how you like, and Klaviyo: Query Metric Aggregates does the raw event math underneath. Klaviyo rate limits the reporting endpoints hard, roughly 2 per minute and 225 per day across them, so wire these to a schedule and write the rows into a Mattering database, not into a per record lookup.
Klaviyo next to the helpdesk, the CRM, and the store
This is the part a standalone Klaviyo server cannot do. A resolved ticket can record an event on the profile, a churned CRM deal can trigger Klaviyo: Suppress Profiles, a restock can drive Klaviyo: Create Back in Stock Subscription, and an incident can flip a promotional flow off with Klaviyo: Update Flow Status (Live Sends Real Messages) set back to draft. All of it on one canvas, with the same run history and the same approval steps as the rest of your work.
Example: A weekly campaign that refuses to send when the audience looks wrong
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a weekly schedule, or an approval task moving to Ready in Mattering Productivity.
Klaviyo: Create Campaign (Draft) builds the campaign from flat fields (name, included and excluded audiences, subject, preview text, from address). Nothing is emailed by this step.
Klaviyo: Get Messages for Campaign reads back the subject and from address that will actually go out, and the Render Template (Preview, Sends Nothing) node renders the body with sample data so a broken merge tag is caught before a person sees it.
Klaviyo: Refresh Campaign Recipient Estimate kicks off the recalculation and Klaviyo: Get Campaign Recipient Estimate reads the number back.
A condition stops the workflow when the estimate is zero, which usually means a broken audience, or far above the expected range, which usually means a segment rule changed. Instead of sending, it opens a task with the numbers attached.
Klaviyo: Send Campaign (Sends Real Email or SMS) runs only past that gate. Klaviyo: Cancel or Revert Campaign Send stays wired to a manual stop, which cancels what has not left yet and can put a scheduled campaign back to draft.
Klaviyo MCP questions, answered
What Klaviyo operations are supported?
49 nodes on the JSON:API surface: metrics and account details, raw events (list, get, track), profiles (list, get, upsert, update, list memberships, merge), consent and suppression (subscribe, unsubscribe, suppress, unsuppress), lists (list, get, create, read members, add, remove), segments (list, get, read members), campaigns (list, get, create draft, update, read messages, refresh and read the recipient estimate, send, cancel or revert), flows (list, get, update status), templates (list, get, create, render), tags (list, create), catalog items and categories plus back in stock subscriptions, and the campaign, flow, and segment performance reports. Deliberately not shipped: asset deletion, the GDPR profile deletion job, the bulk import and bulk catalog job lifecycles, multipart image upload, coupons, webhook registration, and the JSON:API relationships id accessors.
Klaviyo runs its own official MCP server. Why use this one?
Both are real, and we are not going to pretend otherwise. Klaviyo operates a first party remote MCP server, and if all you want is an assistant talking to Klaviyo on its own, that is a perfectly good answer. This connector solves a different problem: it puts Klaviyo nodes on the same canvas as every other connector in Mattering, so one workflow can move between Klaviyo and a helpdesk, a CRM, a store, or a Mattering database without glue code, run on a schedule, keep a shared run history, and pause for a human approval in the middle. Coverage here is a curated 49 operations with the JSON:API envelope hidden behind typed fields; placement is the reason to pick it.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. The read nodes are the safest surface to hand an agent, since the reporting, catalog, and lookup nodes change nothing; keep the send and consent nodes behind an approval step rather than free agent access.
What credential does it need, and what scopes?
One Klaviyo private API key, the value starting with pk_. The wire format is Authorization: Klaviyo-API-Key followed by the key, which is not Bearer and not Basic, and the connector builds that header itself, so the form is a single field and you paste only the key. Scopes are chosen when the key is created and cannot be changed afterwards. A Read Only key drives all 28 read nodes, and the connection test needs only metrics:read. Scope the key to what the automation actually does, and mint a second key rather than upgrading an existing one.
Do I have to build Klaviyo's JSON:API request bodies?
No, and that is most of the point. Klaviyo's write bodies nest a resource type, an id, an attributes object, and a relationships object, and a campaign create goes five levels deep before you reach the subject line. Here you fill flat typed fields and the connector assembles the envelope, so a resource type string never appears in a config panel. Responses are still JSON:API shaped, so real fields sit one level down under attributes; every node's sample output shows that nesting, which means the drag paths you wire (for example data.data[0].attributes.name) are correct before the first run.
Can this connector email real people by accident?
It can, which is why the loud nodes are labelled rather than quietly mixed in with the rest. Klaviyo: Send Campaign (Sends Real Email or SMS) mails the entire audience with no undo once messages leave. Klaviyo: Update Flow Status (Live Sends Real Messages) arms automated sending indefinitely for everyone who meets the trigger. Klaviyo: Subscribe Profiles (Grants Marketing Consent) emails a confirmation to every address on a double opt in list. Two quieter nodes can also cause sends: Klaviyo: Track Event fires a live flow triggered on that metric, and Klaviyo: Add Profiles to List fires an Added to List welcome series. Check Klaviyo: List Flows for live flows before pointing bulk work at either.
What is the risk with unsubscribing, and what is actually destructive?
Unsubscribing has a genuinely nasty edge that Klaviyo documents itself: any profile you pass to Klaviyo: Unsubscribe Profiles (Revokes Marketing Consent) that is NOT a member of the list you named gets unsubscribed from ALL of your marketing on that channel, not just that list. Consent cannot be restored programmatically, so this is a real, irreversible, customer affecting outcome. That is why the connector ships Klaviyo: Get Lists for Profile as the safety check: look up the profile's memberships first, and use Klaviyo: Remove Profiles from List when you only want someone off one audience. Separately, suppression is reversible: Klaviyo: Suppress Profiles and Klaviyo: Unsuppress Profiles are a documented pair, though the undo only clears suppressions this connector created and deliberately leaves self service unsubscribes and dead addresses alone. Only one node destroys data: Klaviyo: Merge Profiles (Permanently Deletes the Source).
What happens when Klaviyo changes its API, and what about rate limits?
Klaviyo versions by a dated revision header rather than a URL path, and unrecognized revisions fall forward, which means an unpinned client drifts silently on the next breaking release. This connector sends a single pinned revision, 2026-07-15, on every request, so the fields and sample outputs describe the API the request is actually talking to, and a version bump is a deliberate re-researched change instead of a surprise. Rate limits are per endpoint and Klaviyo returns a Retry-After on a 429. The reporting endpoints are the tight ones, roughly 2 per minute and 225 per day across them; asking a list or segment read for a profile count also drops it into a much lower bucket, so read those once per run rather than in a loop.
Put Klaviyo to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Klaviyo is a product of its respective owner; Mattering is an independent platform.