Bring support signals into Klaviyo

01

Connect and verify

1. Sign into the SuperBot workspace you want to connect. You need edit access and a Klaviyo account with permission to install apps.
2. Open Dashboard → Integrations and choose Klaviyo. When OAuth is available, select Connect Klaviyo. If you still see a private-key form, OAuth has not been enabled for this deployment; existing key connections remain supported.
3. Select the intended Klaviyo account and review account-read and event-write permissions. SuperBot does not request campaign, list, or subscription management.
4. Return to SuperBot and confirm the Klaviyo account shown on the connection card. New OAuth connections enable lead-captured and form-submitted events. Choose additional events only if needed.
5. Use Send test. It creates a clearly labeled synthetic profile/event, not a real customer or an opt-in. Check the event in Klaviyo before activating any flow.

02

Events and data

• New lead captured
• Form submitted
• New conversation started
• Conversation escalated to a human

Events require a valid visitor email. Anonymous conversations are skipped. Profile email and name accompany selected events; source, company, conversation ID and form ID may be included when present. Full transcripts and arbitrary form fields are not exported. Existing metric names are retained so configured Klaviyo flows can keep using them.

A successful API response means Klaviyo accepted the event for processing, not that a campaign ran. OAuth events are stored in an encrypted delivery queue. Retries reuse the same event ID, respect rate limits and resume after server restarts. Failed events remain available for investigation for up to seven days; successful payloads are removed immediately. Legacy API-key connections use shorter inline retries.

03

Pause, reconnect, or disconnect

Disable pauses new delivery. Reconnect renews authorization for the same Klaviyo account. To switch accounts, disconnect first. Disconnect revokes OAuth access before removing stored credentials. Events already accepted by Klaviyo remain there and must be managed in Klaviyo.

Tokens are stored encrypted. Access-token refreshes are serialized per connection. Expired links, declined consent and account mismatches return an actionable notice. If permission errors persist, reconnect with the required account-read and event-write permissions.

Questions? [email protected]. See privacy and terms.