Integration
Run Klaviyo from inside Claude.
Connect your Klaviyo account and Claude stops describing your email program and starts working on it — reading your campaigns, flows, and segments, and pushing templates back. Here's exactly what that covers, and the two places where Klaviyo's API draws a line.
You ask Claude to tidy up your Klaviyo welcome flow. Without a connection, it gives you the same clean, generic advice it would give any brand — ladder the emails, segment by engagement, add a nudge on day three. It has never seen your flows, your lists, or the template you actually send. An MCP for Klaviyo — a way to hand Claude Klaviyo's real API instead of generic knowledge — closes that gap. It reads what's live in your account and builds against it. The honest part is knowing where Klaviyo's API lets Orbit act and where it only lets Orbit look. That's the whole page below.
What Orbit does with Klaviyo today.
Every row is a real job, mapped to a real Klaviyo API endpoint. Where there's a limit, the limit is in the cell — not buried in a footnote. There are two kinds of honest here, and they're different: rate-capped means the API allows it with a ceiling; not possible via Klaviyo's APImeans the endpoint doesn't exist, and no amount of building on our side invents one.
| The job | Status | What it means |
|---|---|---|
| Connect & auth check | Works | Klaviyo has no ping endpoint, so Orbit probes with a one-item list read to confirm the key is live. |
| List email templates | Works | Full inventory of your Klaviyo email templates, read natively. |
| Read a template's HTML | Works | Pull any single template's body so Claude can see what you actually send, not a description of it. |
| Create & update templates | Works | Native template CRUD — Orbit can write a template into your account, not just draft one in chat. A server-side render is available too, though best-effort (Klaviyo has been revising that endpoint). |
| Read campaigns & flows | Works | Campaigns come back filtered to the email channel; flows are read on their own endpoint. Both native. |
| Read segments & lists | Works | Both your Klaviyo segments and static lists, read natively. |
| Pull performance metrics | Rate-capped | Klaviyo's Reporting API works, but the ceiling is real: 225 report queries per day (one per second in a burst, two per minute sustained), and it needs a conversion metric. Orbit caches results and paces its reads to live under the cap — so it won't drive a dashboard that refreshes on every glance. |
| Test send | Not possible via Klaviyo's API | Klaviyo exposes no public test-send endpoint for a template or campaign. Instead, Orbit runs its own local QA gate on the template's HTML, and can additionally request a server-side render from Klaviyo (an endpoint Klaviyo has been revising, so best-effort). You review a real check on the HTML — you just don't get a live send from the API. |
How to connect Klaviyo.
One credential. Orbit authenticates to Klaviyo with a private API key — the key type that starts with pk_ and carries read-write scope.
The one field
klaviyo_api_key — your Klaviyo private key. Generate it in Klaviyo under Settings → Account → API Keys, create a private key with the scopes you want Orbit to use, and paste the pk_value into Orbit's config.
That's the whole setup. If the key is missing or wrong, Orbit tells you exactly which field to fix and where to find it — it never fails silently or crashes mid-task.
What stays Braze-only.
Orbit works with every major ESP, and its deepest integration is Braze. Some of what Orbit does is genuinely Braze-specific — not because we haven't got to Klaviyo, but because the concepts don't port. Canvas building, Content Blocks, and the Braze media-library tools all target objects that only exist in Braze's model. There's no honest Klaviyo equivalent to map them onto, so we don't fake one.
For Klaviyo, the portable operations are the ones in the table above: templates, campaigns, flows, segments, lists, and rate-capped metrics. Everything Klaviyo's API exposes, Orbit reaches through the same generic tool family it uses for every ESP.
Beyond the Klaviyo API.
The API connection is half of it. The other half is the portable layer that works the same whichever ESP you're on: 66 skills that encode real lifecycle methodology, 99 tools, and a production email pipeline — MJML that compiles to clean HTML, a render preview, and a QA gate that checks dark mode, clip length, and accessibility before anything goes near a send.
That's the piece that covers Klaviyo's missing test-send. You don't get a live API send, but you do get the HTML QA'd locally — dark mode, clip length, accessibility — before you push the template into your account and send it from Klaviyo's own UI. Orbit can also ask Klaviyo to render the template server-side, though that endpoint is in flux, so the local QA is the part to lean on. The calculators — sample size, holdout maths, LTV — are ESP-neutral too. None of that depends on which platform you connected.
Try it with your Klaviyo account.
Orbit is a one-off purchase — $124.50 during the launch window, $249 after. One payment, every skill and tool included, no seats and no subscription. Paste your Klaviyo private key and it goes from advisor to operations layer the same afternoon.
Run a different ESP?
The same honest treatment, per platform:
Frequently asked.
Can Orbit push email templates into Klaviyo?
Yes. Klaviyo's API has native template CRUD, so Orbit can create, read, and update email templates in your account. It can also ask Klaviyo to render one server-side, though that's best-effort — Klaviyo has been revising that endpoint. Template CRUD is the part Customer.io can't do; Klaviyo is one of the ESPs where the full write path exists.
Can Orbit send a test email through Klaviyo?
No — Klaviyo's public API has no test-send endpoint for a template or campaign. Instead of pretending otherwise, Orbit runs its own local QA gate on the template's HTML: dark-mode check, clip-length check, accessibility lint. It can also request a server-side render from Klaviyo, but Klaviyo has been moving that endpoint, so that step is best-effort and the local QA is the dependable proof. You review a real check on the HTML; you just don't get a live inbox send from the API.
Why are Klaviyo performance metrics limited?
Klaviyo's Reporting API caps campaign-values queries hard: one per second in a burst, two per minute sustained, and 225 per day. It also requires a conversion metric ID. Orbit reads the numbers, but caches them and paces its calls to stay under the daily ceiling — so it won't power a live cross-ESP dashboard that refreshes on every glance.
Do I need to be technical to connect Klaviyo?
No. You paste one private API key (it starts with pk_) into Orbit's config. You generate it in Klaviyo under Settings → Account → API Keys. Once it's in, you talk to Claude the way you already do and Orbit reaches for Klaviyo when the job needs it.
Is Klaviyo the right ESP to run through an MCP?
If you're a Shopify-heavy ecommerce brand already living in Klaviyo, yes — the template CRUD and flow reads mean Orbit works as a real build hand, not just an advisor. Orbit's deepest integration is Braze, so a lifecycle-heavy program at scale gets more from the Braze path. But for the DTC operator whose whole stack is Klaviyo, this is a genuine operations layer, with the metrics rate-cap the one honest asterisk.