- Integrations
- Omnisend
Omnisend integration: the visitor in the chat is saved as a contact in Omnisend
Agenola's Omnisend integration connects your agent to your Omnisend account: the agent adds visitors who ask for your newsletter to your contacts and subscribes them, tags them based on the conversation and sends events that start your Omnisend automations. It connects in one click with your Omnisend account.
How it works
Omnisend steps are added to the flow or turned on in the Integrations tab of the AI Assistant step. In each step the contact is found by email address; the email the visitor gives is enough.
Each Omnisend account has one contact list, so you don't choose a list in the step. You'll find the contacts the agent adds in Omnisend by the “source: agenola” tag.
- A new contact is added without being subscribed unless the step says “Subscribe”. Choose “Subscribe” only if the visitor agreed to receive marketing email.
- When a visitor opens a support request and leaves an email, it is also recorded on their contact in Omnisend as an event; you can build an automation on it.
- In agents open to visitors, use “Get subscription status”: it only tells whether they're subscribed and doesn't return the contact's name or phone.
- The steps that send a draft campaign, delete a campaign or unsubscribe a contact don't run until the confirmation box in the step is ticked.
What it does
This list is generated from the same source as the Omnisend page in the dashboard: if it isn't listed here, we don't do it with Omnisend. Flow steps live in the flow editor under Add step → Integrations → Omnisend.
ContactAction · Flow step7
Add or update contact
Adds the contact if they aren't in Omnisend, otherwise updates their name, phone and tags. With no status chosen, a new contact is added without being subscribed; a subscribed contact is never unsubscribed. A new contact also gets the “source: agenola” tag.
Add contact
Adds the contact to Omnisend; with no status chosen, they're added without being subscribed. If the contact is already in Omnisend, the step fails.
Update contact
Changes the contact's status, name or phone.
Get subscription status
Reads whether the email is subscribed; doesn't return the contact's name or any other detail. Use this in agents open to visitors.
Get contact
Reads the contact's name, phone, status and tags. For agents your team uses; a visitor could type someone else's email.
Get contacts
Returns the 100 most recently added contacts as a list. For agents your team uses.
Unsubscribe
Ends the contact's email subscription; they get no marketing email. The contact stays in Omnisend.
Contact tagAction · Flow step2
Add tags
Adds tags to the contact; their other tags stay.
Remove tags
Removes tags from the contact; their other tags stay.
Contact eventAction · Flow step1
Send event
Writes an event on the contact's profile; you can start an Omnisend automation from it. If the contact isn't in Omnisend, they're added without being subscribed.
CampaignAction · Flow step5
Get campaign
Reads the campaign's name, subject and status.
Get campaigns
Returns the latest 100 campaigns as a list.
Replicate campaign
Creates a copy of the campaign as a draft.
Send draft
Sends the chosen draft campaign to its recipients now.
Delete campaign
Permanently deletes the campaign.
Example conversations
Visitor: I'd like to hear about your discounts. Can I sign up for the newsletter? My email is deniz@example.com.
Agent: Of course, I've signed deniz@example.com up for our newsletter; we'll send our campaigns to that address.
Behind the scenes: The “Add or update contact” step adds Deniz to Omnisend as a subscriber with the “Subscribe” status. If your welcome automation in Omnisend is on, it sends Deniz the first email.
Visitor: I'm on your newsletter. Is there a discount if my team places a bulk order? We're 20 people. My email is can@example.com.
Agent: Our team will prepare a custom offer for bulk orders; I've passed on your details.
Behind the scenes: “Add tags” gives Can the “bulk order” tag. “Send event” writes a “bulk order request” event on Can's profile; your Omnisend automation that starts with this event sends Can the offer email.
Visitor: My order arrived damaged and I'd like an exchange. My email is ece@example.com.
Agent: I'm sorry about that. I've passed your request to our team; they'll get back to you by email.
Behind the scenes: The agent opens a support request. It is also recorded on Ece's contact in Omnisend as an event; with an automation that starts with this event, you can send Ece a follow-up email.
Setup
- 1In Agenola, go to Integrations → Omnisend, press “Connect to Omnisend” and approve with your Omnisend account.
- 2In the agent editor, add Omnisend steps and put the variable that holds the visitor's email in the email field.
Detailed setup: How do I connect Omnisend?
Permissions and where your data goes
- Sent to Omnisend: the fields you fill in the step (the visitor's email, first name, last name and phone), the subscription status, tags, event properties, and the subject of a support request the visitor opens with their email.
- Read from Omnisend: the account's name and website, campaigns and the contact details a step asks for.
- Agenola asks Omnisend only for permissions for your account, contacts, events and campaigns; it doesn't ask for products, segments or automations.
- Connection details are stored encrypted on the server. Only the workspace owner and admins can connect or remove the connection. Removing it also removes Agenola's access in Omnisend; your contacts stay in Omnisend.
Related integrations
See all integrations
Klaviyo
Your agents save visitors as Klaviyo profiles, add them to your list or subscribe them, and record events on their profile.
Mailchimp
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.
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 in Omnisend without their consent?
No. A new contact is added without being subscribed unless the step says “Subscribe”, and gets no marketing email. Choose “Subscribe” only if the visitor agreed to the newsletter; when a contact is subscribed, Omnisend records that the consent came from Agenola.
Can a visitor see someone else's details through Omnisend steps?
The visitor's identity isn't verified; they can type someone else's email. In an agent open to visitors, use “Get subscription status”, which only tells the subscription. “Get contact” and “Get contacts” return names and phones; turn them on in agents your team uses.
How do support requests reach Omnisend?
When a visitor opens a support request and leaves their email, the request is recorded on their contact in Omnisend as an event; its subject and the agent it came from are in the event's properties. If the contact isn't in Omnisend, they're added without being subscribed. You can build an automation or a segment on this event.
Can the agent send my Omnisend campaigns?
Yes, in an agent your team uses. “Send draft” sends a draft campaign you prepared in Omnisend to its recipients now; “Replicate campaign” creates a draft copy of a campaign that was already sent. The send and delete steps don't run until the confirmation box is ticked.