Skip to main content

Klaviyo

Manage profiles, lists, events and campaigns in your Klaviyo account.

Connect it with: API key. Klaviyo's own documentation: https://developers.klaviyo.com/en/reference/get_accounts.

What agents can do​

Connect Klaviyo so the agents working your tasks can reach it. With it connected, they can:

  • Create or update profiles and subscribe them to lists.
  • Track a custom event that triggers a Klaviyo flow.
  • Read campaign and flow performance for a report.
  • List segments and their members.

Before you start​

  • A Klaviyo account and a user with the Owner, Admin or Manager role, which can create private API keys.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Klaviyo​

Jaah connects to Klaviyo with an API key, not with a sign-in button.

Connect with an API key​

Find each value first:

  • Private API key: Klaviyo > your account name (bottom left) > Settings > Account > API keys > Create Private API Key. Give Accounts read access (accounts:read) plus what agents need, then copy the key, which starts with pk_.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Klaviyo card.
  2. Name the secret and choose who can use it.
  3. Fill in Private API key.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Klaviyo with an API key, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah calls Klaviyo's API once (GET https://a.klaviyo.com/api/accounts) with the stored values, and shows who it answered as, or which value Klaviyo refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: private_api_key.

Tell the agent in your task description which secret to use, for example “use the Klaviyo secret org/klaviyo”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Klaviyo once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Klaviyo's side too, revoke or delete the key at Klaviyo.

Limitations​

  • Agents can use only the scopes chosen when the key was created; a missing scope answers 403 for that call.
  • Klaviyo's public keys (site IDs) cannot be used here: only a private key starting with pk_.
  • Agents can do only what the connected Klaviyo account allows.

Troubleshooting​

Test says Klaviyo rejected the private API key (401)

The key was deleted or mistyped. Create a new private key under Settings > Account > API keys and select Replace on the secret.

Test says Klaviyo rejected the private API key (403)

The key lacks Accounts read access. Edit the key's scopes in Settings > Account > API keys, or create a key with accounts:read.

An agent's call fails with 403 on another endpoint

Add the scope that endpoint needs (for example profiles:write) to the key, then rerun the task.

Still stuck? Select Test and read the result: it names the value Klaviyo refused and the status it answered.

FAQ​

Which key type should I pick: Full, Read-only or Custom?

Custom, with only the scopes agents need plus accounts:read for Test. Full access works too but grants more than most tasks need.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Klaviyo account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.