Sign inStart free trial
User guide

Connect and use Klaviyo with Chirply

Connect your own Klaviyo account, bring its customer and lifecycle-marketing data into Chirply, respond to real-time activity, and run supported Klaviyo operations from one controlled workspace.

Before you begin

You need an active Chirply workspace where you are an owner or administrator. Your Klaviyo user must be permitted to authorize applications. Keep both accounts open in the same browser while connecting.

Install and connect

Install Klaviyo in Chirply

Open Chirply's App Marketplace, select Klaviyo, and choose Install. If you started from Klaviyo's Marketplace, its Install button will send you into the same Chirply connection flow after you sign in.

Authorize your Klaviyo account

Select Connect with OAuth. Klaviyo displays the permissions Chirply needs for its supported stable API operations. Review them, choose the correct Klaviyo account, and approve access. You are then returned to Chirply.

Chirply stores OAuth credentials encrypted and refreshes access automatically. It never asks you to expose your Klaviyo password.

Verify the connected account

Open Apps > Klaviyo. The page shows the connected account and its status. Choose Verify account now to confirm that Chirply can read the account identity with the granted permissions.

Start the first synchronization

In the Synchronization center, choose Sync everythingto mirror the supported resource groups. Chirply processes large accounts as resumable jobs, so a job can continue safely across multiple batches.

Historical data is mirrored into Chirply without replaying old events through live journeys or automations. Progress, completion, and any actionable error appear in the synchronization center.

What Chirply can access

Chirply's catalog is generated from Klaviyo's stable API revision and covers the customer-data and lifecycle-marketing graph rather than a small set of canned actions. Supported areas include:

  • Accounts, profiles, consent, subscriptions, events, and metrics
  • Lists, segments, campaigns, flows, forms, templates, and images
  • Catalogs, coupons, coupon codes, reviews, and custom objects
  • Reporting, conversations, tags, tracking settings, and web feeds
  • Signed system webhooks and real-time Chirply automation triggers

Access remains limited to the Klaviyo account that authorized Chirply and to the scopes shown during installation. Klaviyo's rate limits still apply.

Use the synchronization center

The synchronization center keeps a local operational view of selected Klaviyo resources. It records job progress, the last successful sync, and errors that require attention. Use Continue queued jobs when a queued job has more batches to process.

Profile records are matched carefully so that synchronization does not blindly overwrite existing Chirply contacts. Klaviyo identifiers and source properties remain available for reconciliation and automation.

Run an official API operation

  1. Open Apps > Klaviyo and find the Official API catalog.
  2. Search by operation name or filter by resource category.
  3. Select the operation and provide any required path parameters, query values, or JSON body.
  4. Review the selected account and request before choosing Run against live Klaviyo.
  5. Inspect the returned status, response data, or validation error in Chirply.

Read operations retrieve live Klaviyo data. Write and delete operations can change live campaigns, audiences, profiles, catalogs, consent, or account configuration, so only an authorized owner or administrator should run them.

Enable real-time events

In the Klaviyo synchronization center, choose Enable all topics. Chirply retrieves the webhook topics available to the connected account, creates a Klaviyo webhook, and verifies every delivery signature before accepting it.

Accepted events can trigger Chirply automations using the Klaviyo topic, event type, profile identifier, and payload. Deliveries are persisted before processing so temporary failures can be retried. Choose Disable to remove the registered webhook.

Manual private-key connection

OAuth is the recommended installation method and is required for a Klaviyo Marketplace installation. For a direct, non-Marketplace connection, an administrator may instead add a scoped Klaviyo private API key from Settings > Integrations. The key must contain every permission needed for the operations you intend to use. Chirply encrypts the key and sends it only to Klaviyo's API host.

Disconnect or uninstall

  1. Open Settings > Integrations in Chirply.
  2. Find Klaviyo and choose Disconnect.
  3. If you installed through Klaviyo, you may also remove Chirply from Klaviyo's installed-app settings.

Disconnecting removes Chirply's stored connection credentials and stops new API calls, synchronization, and webhook processing. It does not delete data from your Klaviyo account. Records already imported into your Chirply workspace remain your business data until you delete them or close the workspace.

Troubleshooting

Authorization failed: Confirm you are signed into the intended Klaviyo account and that your Klaviyo role can authorize applications, then restart the connection.

Permission or 403 error: The installed grant or private key does not include the scope required by that operation. Reauthorize the app or replace the private key with one containing the necessary permission.

Rate-limit or 429 error: Wait for the retry window. Chirply honors Klaviyo's retry guidance for transient rate limits, but sustained request volume may still need to be reduced.

Sync stopped: Open the synchronization center, read the job error, verify the connection, and continue or restart the job after correcting the cause.

Security, privacy, and support

Credentials and tokens are encrypted at rest, requests are restricted to Klaviyo's API host, and customer workspaces are isolated through authorization and database controls. See Chirply's Privacy Policy and Terms of Service for additional details.

For help, email support@chirply.io and include your Chirply workspace name, the affected Klaviyo account, the operation or sync job, and the exact error message. Do not email private API keys, access tokens, or passwords.