Klaviyo

The Klaviyo app connects Klaviyo email and SMS marketing to Sprigr Team. Agents can look up profiles and their consent, read lists and segments, report on campaigns and flows, create and send campaigns, manage catalogs, coupons, templates and forms, and record custom events. Every call goes live to Klaviyo with your own credentials, so the agent always sees current data; nothing is mirrored locally.

Note

Klaviyo ships as a marketplace app with per-user connections and an install-wide fallback. Each person can connect their own Klaviyo account by OAuth; where nobody has, the app can use a private API key set on the install. Klaviyo enforces what the connected credential can reach.

Prerequisites

• A Klaviyo account. For the per-user route, a Klaviyo login with access to the account. For the fallback, a private API key created in Klaviyo under Settings > API keys with the scopes you want agents to have.
• Admin or Owner role in your Sprigr Team organisation to install the app. Any member can connect their own Klaviyo account once it is installed.

Installing and connecting

1. Install the app

   Sign in to team.sprigr.com, open Apps in the sidebar, find Klaviyo under Available, and install it. KLAVIYO_PRIVATE_API_KEY is optional at install; leave it blank if everyone will connect by OAuth. See Installing Apps.

2. Connect your Klaviyo account

   Open the app’s settings page from Apps > Installed and click Connect Klaviyo. Sign in to Klaviyo and approve the requested access. Each person does this once; the page then lists the connected accounts and offers Connect another account.

3. Or set the fallback key

   If nobody has connected by OAuth, the app uses the install’s private API key for every call, and the settings page says so. Private keys share one rate-limit pool across your whole Klaviyo account, where each OAuth connection gets its own, so OAuth is preferred.

4. Check the connection

   Ask your agent “How is Klaviyo connected?” It calls klaviyo_connection_status and reports who has connected, the Klaviyo account each is bound to, the granted scopes, and whether the fallback key is configured.

Try asking your agent

“Look up jo@example.com in Klaviyo: what lists are they on and have they consented to SMS?”

“How did last week’s campaigns perform on open, click and revenue?”

“Which flows are triggered when someone joins the VIP segment?”

Confirmation before sending, spending or deleting

Forty-seven actions pause for your confirmation in the chat before they run: sending or cancelling a campaign, subscribing, suppressing or unsuppressing profiles, adding or removing profiles from lists, merging profiles, requesting a profile deletion, bulk imports and bulk events, every delete (campaigns, flows, lists, segments, templates, forms, catalog items, coupons, tags, webhooks and more), updating flows and segments, and the raw write escape hatch. Thirty-eight of those are irreversible. Reads never pause.

What agents can do

The app exposes a single klaviyo tool that takes an action, with 220 actions. At a category level:

• Profiles and consent: get and create profiles, list a profile’s lists and segments, subscribe and unsubscribe, suppress and unsuppress, merge, request deletion, bulk import.
• Lists and segments: list, get, create and delete; add and remove profiles; segment membership.
• Metrics and events: metrics, aggregates and properties; create single and bulk events.
• Campaigns: list and get campaigns and messages, create and clone, assign templates, estimate recipients, send and cancel, campaign reports.
• Flows: list and get flows, actions and messages; flows triggered by a list, segment or metric; flow reporting; update and delete.
• Catalogs: items, variants and categories, bulk create, update and delete, back-in-stock subscriptions.
• Content: templates (including server-side rendering and cloning), universal content, images, forms and form versions, web feeds.
• Coupons: coupons and coupon codes, bulk code generation.
• Data and account: account details, custom metrics, data sources, custom objects and schemas, tags and tag groups, webhooks, tracking settings.
• Escape hatches: a raw GET for anything not yet typed, and a gated raw write.

Ask the agent what it can do with Klaviyo, or have it call list_actions, to see each action’s parameters.

Common use cases

• Support lookups. “Is this customer subscribed to email and SMS?” answers from the profile and its consent records.
• Weekly performance. A scheduled workflow summarises campaign and flow results for the marketing channel.
• List hygiene. The agent finds profiles matching a rule and, after confirmation, moves them between lists or suppresses them.
• Event-driven personalisation. A workflow records a custom event on a profile when something happens in another system, so a Klaviyo flow can pick it up.
• Campaign drafting. The agent creates a campaign from a template and estimates recipients; sending waits for your confirmation.

Troubleshooting

Calls use the fallback key when I expected my own account You have not connected by OAuth. Click Connect Klaviyo on the settings page. The settings page says whether calls are currently using the install-wide private API key.

Missing scope errors The connected credential does not carry the scope the action needs. For OAuth, reconnect; for a private key, create a key in Klaviyo with the required scopes and update the app’s secret.

Rate limits Klaviyo rate-limits per credential. OAuth connections each get their own quota; a private key shares one across the account. If you hit limits on the fallback key, connect by OAuth.

An action is waiting for confirmation Sends, consent changes and deletes pause until you confirm in the chat.

Next steps

• Integrations Overview: See all available integrations.
• Shopify: Join marketing data to orders.
• Workflows: Record Klaviyo events from other systems.