Connector library

Implemented source Marketing, Analytics & Revenue APIs

Klaviyo connector.

Read Klaviyo profile and list metadata, search profiles by email and submit deduplicated metric events through the versioned JSON:API.

Connector download

Download Klaviyo

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.1 Choose version
Release
2026-10-03
Package
Implemented source
Schema credentials
Bearer token
Connection settings
API Base URL
Package size
10 KB
SHA-256
f5933e813275e487fea8bd7b20b1db7bf11cd60988ff4e995557cbb420229bdc

Version history

What's new

  1. v0.2.0.1Latest · 2026-10-03 · Implemented source

    Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.

  2. v0.2.0.0Earlier · 2026-10-03 · Implemented source

    Read Klaviyo profile and list metadata, search profiles by email and submit deduplicated metric events through the versioned JSON:API.

  3. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Retained immutable historical scaffold archive.

Included in this version

Included actions

Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.

Get profile

Retrieve selected identity fields and custom profile properties.

Search profiles

Read one bounded profile page, optionally filtered by exact email.

List audience lists

Read one list-metadata page without changing subscription state.

Submit metric event

Submit a deduplicated profile metric event and report acceptance.

Vendor API

API and access

Implementation considerations
  • Confirm consent fields, subscription status, suppression rules, required identifiers, and workspace/account scope.
  • For broad marketing APIs, start with contact CRUD, event tracking, list or segment membership, and reporting reads.
  • Avoid overwriting consent, source, or attribution fields without explicit customer mapping rules.

Support

Need help with Klaviyo?

Tell us what you need to connect or change.