Agenola is an AI assistant for your website that answers visitors' questions, helps them find products, and takes support requests.
With the Omnisend integration, the agents you build in Agenola add chat visitors to your Omnisend contacts, tag them based on the conversation, and send custom events. You can use this data to build segments, personalize emails, and start automations.
Benefits
Grow your list from conversations: visitors who leave their email in the chat are added to Omnisend and subscribed only when they agree to receive marketing emails.
Segment by interest: tag contacts based on what they asked about, for example, "bulk order" or "vip".
Start automations from the chat: send custom events, such as "asked for a discount", that trigger your Omnisend workflows.
Follow up on support requests: each support request a visitor opens in the chat is recorded on their Omnisend contact as an event.
Work with campaigns from an internal agent: list, replicate and send draft campaigns from an agent your team uses.
How It Works
You connect Agenola to Omnisend from Agenola with your Omnisend account (OAuth). There are no API keys to copy.
After connecting, you add Omnisend steps to an agent's flow in Agenola. When a visitor passes through the flow, the step runs on behalf of your Omnisend account: it adds or updates the contact, adds tags, or sends a custom event. When a visitor opens a support request and leaves their email, Agenola also sends the Agenola Support Request event to Omnisend automatically.
Setup Process
Step 1. In Agenola, go to Integrations → Omnisend → click Connect to Omnisend.
Step 2. Sign in to Omnisend if asked, then complete the OAuth flow by authorizing Agenola to access your Omnisend account. If you have more than one Omnisend store, choose the right one before you authorize.
Step 3. Back in Agenola, check that the Omnisend page shows Connected with your store name.
Step 4. In Agenola, open your agent → go to the Flow tab → click Add step → Integrations → Omnisend. Choose an Action and fill in its fields, for example Email, Status and Tags for Add or update contact.
Step 5. Click Save, then Publish the agent.
Available Omnisend Actions
Action | What it does |
Add or update contact | Adds the contact, or updates the name, phone, and tags of an existing one |
Add contact | Adds a new contact; fails if the contact is already in Omnisend |
Update contact | Changes the contact's status, name, or phone |
Get subscription status | Reads whether the email is subscribed, without returning other contact details |
Get contact / Get contacts | Reads a contact's name, phone, status, and tags, or lists the 100 most recently added contacts |
Unsubscribe | Ends the contact's email subscription; the contact stays in Omnisend |
Add tags / Remove tags | Adds or removes the tags you enter; the contact's other tags stay |
Send event | Sends a custom event with the name and properties you set; adds the contact as not subscribed if they aren't in Omnisend |
Get campaign / Get campaigns | Reads a campaign's name, subject, and status, or lists the latest 100 campaigns |
Replicate campaign | Creates a copy of the campaign as a draft |
Send draft / Delete campaign | Sends the chosen draft campaign now, or permanently deletes a campaign; both can't be undone |
Note: Use Get subscription status in agents open to visitors. Get contact, Get contacts, and the campaign actions are meant for agents your team uses, because a visitor could type someone else's email.
What Data Is Passed
Contact Data
Agenola sends the contact's email, first name, last name, phone, and tags, plus the email subscription status when you choose one in the step. Every new contact Agenola adds gets the source: agenola tag. Phone numbers need the country code and are added without an SMS subscription.
Custom Events
Custom Event Name | When it fires |
| A visitor opens a support request in the chat and leaves their email |
The name you set in the Send event step | A visitor reaches the Send event step in the agent's flow |
Custom Event Fields
The Agenola Support Request event includes these fields:
Field | Description |
| Subject of the support request |
| The agent the request came from |
| Urgency of the request |
| Agenola request number |
For events from the Send event step, the fields are the properties you write in the step's Properties box, one per line as name: value.
Create Automation Workflows with Agenola Events
To use an Agenola event, go to Automation → Create workflow → Create from scratch, then select the custom event in the trigger.
Note: An event must reach Omnisend at least once before you can select it as a trigger. Run the agent once, for example in Agenola's Preview, to send a first event.
Here are example workflows you can build:
Support request follow-up: trigger on
Agenola Support Requestand send an email that confirms the request, using thesubjectandticket_idfields.Discount for interested visitors: add a Send event step named, for example, "asked for a discount", then trigger on that event and send a discount code.
Bulk order outreach: add a Send event step named "bulk order request" with properties such as product and quantity, then trigger on it and send an offer email that uses those properties.
FAQ
How does Agenola connect to Omnisend?
Through OAuth: you click Connect to Omnisend in Agenola and authorize it with your Omnisend account. No API key is needed.
Are contacts added by Agenola subscribed?
Only if you choose Subscribe in the step's Status field. With no status chosen, new contacts are added as not subscribed. Add or update contact never unsubscribes a subscribed contact. Choose Subscribe only when the visitor agreed to receive marketing email, for example after a consent question in the flow.
How do I find the contacts Agenola added?
Every new contact Agenola adds has the source: agenola tag, so you can build a segment on that tag.
Which events does Agenola send?
One automatic event, Agenola Support Request, plus any custom events you set up with the Send event step.
What happens if I disconnect Agenola?
Omnisend steps in your agents stop working, support requests are no longer recorded in Omnisend, and Agenola's access to your Omnisend account is removed. Your contacts stay in Omnisend. To disconnect, go to Integrations → Omnisend in Agenola and click Disconnect.
What should I check if data doesn't appear in Omnisend?
Check that:
The Omnisend page in Agenola shows Connected with the right store.
The agent has an Omnisend step on the path the visitor took, and the agent is saved and published.
The step's Email field gets the visitor's email, for example, from an earlier email question in the flow.
If the issue persists, disconnect Omnisend in Agenola and connect it again.
Didn't find the answer to your question? Reach out to our Support team through the in-app chat or at [email protected] – our team is available 24/7.

