- Integrations
- Klaviyo

Klaviyo integration: visitors from the chat become Klaviyo profiles and join your list
Agenola's Klaviyo integration connects your agent to your Klaviyo account: the agent saves the visitor as a profile, adds them to your list or subscribes them with marketing consent, and records events on their profile. When a visitor leaves an email and opens a support request, that is recorded on their profile as an event too. It connects in one click with your Klaviyo account.
How it works
Klaviyo steps are added to a flow or turned on in the Integrations tab of the AI Assistant step. Steps work with the email the visitor gives.
Each step chooses which list to use: one agent can write to your newsletter list, another to a different list.
- “Subscribe to list” subscribes the email with marketing consent. If the list uses double opt-in, Klaviyo sends a confirmation email first. Use this step after the step where the visitor explicitly agrees.
- “Add profile to list” adds the profile to the list but doesn't give marketing consent.
- “Send event” records an event on the profile; in Klaviyo you can build an automation (Flow) or a segment that starts from this event.
- When a visitor opens a support request and leaves an email, an “Agenola Support Request” event is recorded in Klaviyo; the subject, agent and urgency are its properties.
- Steps run on behalf of your Klaviyo account; the connection keeps working even if the person who connected leaves the account.
What it does
This list is generated from the same source as the Klaviyo page in the dashboard: if it isn't listed here, we don't do it with Klaviyo. Flow steps live in the flow editor under Add step → Integrations → Klaviyo.
ProfileAction · Flow step4
Create or update profile
Finds the profile by email: creates it if it doesn't exist, otherwise updates the fields you fill in.
Get profile
Reads the profile's name and email.
Get profiles
Returns the first 100 profiles as a list.
Update profile
Changes the email, name or phone.
ListAction · Flow step4
Get lists
Returns the account's lists as a list.
Add profile to list
Adds the profile to the list; it doesn't grant marketing consent.
Remove profile from list
Removes the profile from the list.
Subscribe to list
Subscribes the email to the list with marketing consent. Use it after the step where the visitor explicitly agrees.
EventAction · Flow step1
Send event
Records a custom event (metric) for the profile.
Example conversations
Visitor: I'd like to hear about your offers. My email is deniz@example.com.
Agent: You're on our newsletter list; our offers will come to deniz@example.com.
Behind the scenes: “Subscribe to list” subscribes Deniz to your newsletter list with marketing consent. If the list uses double opt-in, Klaviyo sends a confirmation email first.
Visitor: Do you have wholesale prices? I'll buy 200 kilos of coffee for my café. My email is can@example.com.
Agent: Our sales team will prepare a wholesale price for you; I've passed on your details.
Behind the scenes: “Send event” records a “Wholesale request” event with the quantity on Can's profile; if there's no profile, Klaviyo creates one. If you've built an automation that starts from this event, Can gets an email from there.
Visitor: My order arrived damaged. My email is ece@example.com.
Agent: I'm sorry. I've passed your request to our team; they'll get back to you by email.
Behind the scenes: When the agent opens the request, an “Agenola Support Request” event is recorded on Ece's Klaviyo profile. If you've built an automation that starts from this event (for example, a satisfaction email two days later), Klaviyo sends it.
Setup
- 1In Agenola, on Integrations → Klaviyo, press “Connect to Klaviyo” and approve with your Klaviyo account.
- 2In the agent editor, add Klaviyo steps, choose the list, and in the email field write the variable that holds the visitor's email.
Detailed setup: How do I connect Klaviyo?
Permissions and where your data goes
- Sent to Klaviyo: the fields you fill in the step (the visitor's email, first name, last name, phone), list memberships, event names, properties and value. When a visitor leaves an email and opens a support request: the request's subject, the agent's name, its urgency and the request number.
- Read from Klaviyo: the account's name, your lists and the profile details the step asks for (name, email).
- Permissions: viewing account details; reading and writing profiles, lists and subscriptions; writing events. No access to campaigns, automations, segments or templates is requested.
- Connection details are stored encrypted on the server. Only the workspace owner and admins can connect or remove it. When it's removed, Agenola is also removed from your Klaviyo account's integrations; your profiles and events stay in Klaviyo.
Related integrations
See all integrationsMailchimp
Your agents add the visitor to your Mailchimp audience, tag them and leave notes and events on the contact.
Brevo
Your agents add visitors to your Brevo list and leave notes on the contact's card.

GetResponse
Your agents add the visitor to your GetResponse list, tag them and send events that start your automations.

Omnisend
Your agents add visitors to your Omnisend contacts, subscribe and tag them, and send events that start your automations.
HubSpot
Your agents find or add the visitor in your HubSpot contacts, update deals, and leave notes and tasks for your team.

Pipedrive
Your agents find or add the visitor in your Pipedrive persons, open leads, and leave notes and activities for your team.
Frequently asked questions
Is a visitor subscribed to a Klaviyo list without consent?
Only the “Subscribe to list” step subscribes; use it after the step where the visitor explicitly agrees. If the list uses double opt-in, Klaviyo sends a confirmation email first. “Create or update profile” and “Add profile to list” don't give marketing consent.
Can a visitor see other profiles in Klaviyo?
The visitor's identity isn't verified. “Get profile” and “Get profiles” return names and emails; “Get profiles” lists the first 100 profiles in the account. Turn these on in agents your team uses, not in agents open to visitors.
Why does the Klaviyo connection close?
If you remove Agenola in Klaviyo, or your agents don't write to Klaviyo for 90 days, Klaviyo closes the connection. The integration page shows it; connecting again is enough.