Reference · built on requestConnectorMarketing, reviews & analytics

Klaviyo

Profiles, events, lists, segments, campaigns, and flows from a Klaviyo account, with system webhooks for consent and message events.

Request accessPricing ↗

About

Klaviyo is an email, SMS, and mobile push marketing platform. An account holds profiles, the events recorded against them, lists and segments, campaigns, flows, and a product catalog. Its REST API at a.klaviyo.com/api is versioned with a revision header and paginated by cursor. Rate limits are per account and vary by endpoint.

Through Fibric, an operator reads profiles and events, joins them with orders and support history, and proposes a profile update, a custom event, a subscription change, or a campaign send for your approval. Each approved write is made once and recorded with the reason and how to undo it.

This is a reference listing. It documents what Fibric would read from Klaviyo and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Profiles through Get Profiles and Get Profile, with email, phone number, external_id, and custom properties
  • Events through Get Events, filtered by metric_id, profile_id, or datetime, up to 200 per page
  • Lists and segments, and the profiles that belong to them
  • Campaigns and campaign send jobs across the email, sms, and mobile_push channels
  • Flows, metrics, and catalogs as the API reference lists them
  • System webhooks for email, SMS, push, review, and consent topics, signed with HMAC-SHA256

Proposed actions

  • Target capability: propose a profile property update through Create or Update Profile or Update Profile
  • Target capability: propose a custom event through Create Event, with unique_id set so a retry never records it twice
  • Target capability: propose an email or SMS subscription change through Subscribe Profiles
  • Target capability: propose a campaign send, or its cancellation, through Create Campaign Send Job and Update Campaign Send Job

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Stop a campaign before it sends into a backorder

    The operator reads stock from your store and the scheduled campaign send job. If the featured item cannot ship, it proposes cancelling the send job for your approval.

    With Backorder Notice, Holiday Cutoff

  • Flag churn from engagement events

    Get Events shows who stopped opening and clicking. The operator joins that with order history and proposes a win-back event that triggers your flow.

    With Churn Watch

  • Time the review request after delivery

    When the carrier confirms delivery, the operator proposes a Create Event call that starts your review-request flow, once per order.

    With Survey Timing

  • Reach affected customers during an incident

    The operator drafts the audience from a segment and proposes a campaign send job to the affected profiles. You approve before anything goes out.

    With Outage Notice

Requirements

  • A Klaviyo account and a private API key with the read and write scopes the operator needs, such as profiles:read and events:write
  • The revision header on every request, for example revision: 2026-07-15
  • For webhooks, an account on Advanced KDP or a Klaviyo app, plus an HTTPS endpoint and a secret key of at least 16 characters
Authentication
A private API key sent as Authorization: Klaviyo-API-Key with the scopes chosen when the key is created, or OAuth 2.0 for an app, with a revision header on every request.

Limits

  • Limits are per account and per endpoint, in tiers from XS (1 per second, 15 per minute) to XL (350 per second, 3,500 per minute)
  • Requests that use additional-fields or include carry stricter limits, and the limits stack
  • Scopes cannot be added to an existing private key; a new key is needed
  • At most 10 webhooks per account, with a delay of about 3 minutes before a new webhook forwards events

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Klaviyo ↗

Questions and answers

Does Klaviyo send webhooks?
Yes, with conditions. System webhooks are created through Create Webhook with a name, an endpoint URL, topics, and a secret key of at least 16 characters. Klaviyo signs requests with HMAC-SHA256. Access is limited to Advanced KDP accounts and Klaviyo apps, and each account can have at most 10 webhooks.
What does the revision header do?
It pins the API version. Every request to a.klaviyo.com/api must carry a revision header such as revision: 2026-07-15. Klaviyo's versioning and deprecation policy explains how long a revision stays supported.
Can a retried event be recorded twice?
Not if unique_id is set. Create Event accepts a unique_id to prevent duplicate processing and a backfill flag that suppresses flow triggers for historical loads. The endpoint returns 202, which means the payload was accepted, not yet processed.
Ask about Klaviyo

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Klaviyo through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy