Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Klaviyo

Synchronize Klaviyo lists, campaigns and customer data across the application stack.

CategoryMarketing
Authenticationcustom, OAuth 2.0
Version0.2.0
Published scopes11 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Klaviyo with Flows360

Synchronize Klaviyo lists, campaigns and customer data across the application stack.

Use the Klaviyo connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 11 actions and 2 triggers.

Available actions

  • Create Profile
  • Update Profile
  • Add Profile to List
  • Create List
  • Find List by Name
  • Find Profile by Email/Phone
  • Find Tag by Name
  • Remove Profile from List
  • Plus 3 additional declared actions.

Available triggers

  • New Profile
  • Profile Added to List/Segment

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Klaviyo
  • Package: @activepieces/piece-klaviyo@0.2.0
  • Exact artifact digest: sha256:9cfc7b1ad0166306e073a1f7855bd4def2c69d97ef8f329711ed2e8ab7180ce1
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT, OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Profile (createProfile), Add new user profile with email/SMS subscription options Classification: read.
  • Update Profile (updateProfile), Update existing profile data and preferences. Classification: read.
  • Add Profile to List (addProfileToList), Add profiles to a specific list without changing subscription status. Classification: read.
  • Create List (createList), Create a new subscriber list. Classification: read.
  • Find List by Name (findListByName), Find lists by name with optional additional data Classification: read.
  • Find Profile by Email/Phone (findProfileByEmailPhone), Find a profile using email or phone number. Classification: read.
  • Find Tag by Name (findTagByName), Find tags whose name contains the search query. Classification: read.
  • Remove Profile from List (removeProfileFromList), Remove profiles from a specific list. Classification: read.
  • Subscribe Profile (subscribeProfile), Subscribe profiles to email or SMS marketing on a list. Classification: read.
  • Unsubscribe Profile (unsubscribeProfile), Unsubscribe profiles from email or SMS marketing on a list. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Profile, polling.
  • Profile Added to List/Segment, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom, OAuth 2.0
Supported objects13
Supported actionsNot published
Triggers2

Authentication

Authentication method: custom, OAuth 2.0

Required scopes

profiles:readprofiles:writelists:readlists:writetags:readsegments:readevents:readevents:writesubscriptions:readsubscriptions:writeaccounts:read

Authentication profiles

connection · custom
  • Private API Key Required · protected credential
connection_2 · oauth2

OAuth scopes: profiles:read, profiles:write, lists:read, lists:write, tags:read, segments:read, events:read, events:write, subscriptions:read, subscriptions:write, accounts:read

Supported objects

ObjectReadWriteNotes
Create Profile Yes No Add new user profile with email/SMS subscription options
Update Profile Yes No Update existing profile data and preferences.
Add Profile to List Yes No Add profiles to a specific list without changing subscription status.
Create List Yes No Create a new subscriber list.
Find List by Name Yes No Find lists by name with optional additional data
Find Profile by Email/Phone Yes No Find a profile using email or phone number.
Find Tag by Name Yes No Find tags whose name contains the search query.
Remove Profile from List Yes No Remove profiles from a specific list.
Subscribe Profile Yes No Subscribe profiles to email or SMS marketing on a list.
Unsubscribe Profile Yes No Unsubscribe profiles from email or SMS marketing on a list.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Profile Yes No polling trigger declared by the pinned package.
Profile Added to List/Segment Yes No polling trigger declared by the pinned package.

Triggers

New Profile · Poll

Triggers when a new profile is created in Klaviyo.

Profile Added to List/Segment · Poll

Triggers when a profile is added to a specific list or segment.

Inputs

  • targetType · string
  • listId · string
  • segmentId · string

Setup

Setup

  1. Add the Klaviyo connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • profiles:read
  • profiles:write
  • lists:read
  • lists:write
  • tags:read
  • segments:read
  • events:read
  • events:write
  • subscriptions:read
  • subscriptions:write
  • accounts:read
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-klaviyo@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 11 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Klaviyo connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-klaviyo@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com