How do I connect Omnisend?

What it gives you

The Omnisend integration adds Omnisend steps to your agents: they add and update contacts, subscribe them, read the subscription status, unsubscribe, tag, send events; and get, replicate, send and delete campaigns.

When a visitor opens a support request and leaves an email, it is recorded on their contact in Omnisend as an event automatically. Other records are created only by a step you add to the flow or an action you turn on in the “Integrations” tab of the AI Assistant step.

Connecting requires the Owner or Admin role.

Connecting

1. On Integrations → Omnisend, press “Connect to Omnisend”.
2. Sign in with your Omnisend account and press “Authorize access”. If you have more than one Omnisend store, choose the store to connect with “Switch store” on the approval screen.

Steps run on behalf of your Omnisend account. Each Omnisend account has one contact list, so you don't choose a list in the steps.

Contacts

“Add or update contact” adds the contact if they aren't in Omnisend, otherwise updates their name, phone and tags.

A new contact is added without being subscribed unless “Subscribe” is chosen in the “Status” field; Omnisend sends no confirmation email to contacts added this way. Choose “Subscribe” only if the visitor agreed to receive marketing email. This step never unsubscribes a subscribed contact.

A new contact gets the “source: agenola” tag, so you can find the contacts the agent adds in Omnisend. If your welcome automation is on, Omnisend sends a new subscriber the first email.

Write the phone with the country code (+1 415 555 0123); the step doesn't accept a number without it. The phone is added without an SMS subscription.

“Add contact” goes to the error branch if the contact is already in Omnisend. “Update contact” can set the status to “Subscribed” or “Unsubscribed”; Omnisend doesn't move a subscribed contact back to “not subscribed”.

In agents open to visitors, use “Get subscription status”; it only tells whether they're subscribed. “Get contact” and “Get contacts” return names, phones and tags. A visitor could type someone else's email, so turn these on in agents your team uses.

Tags and events

Write tags separated by commas; Omnisend saves tags in lowercase. “Remove tags” removes only the tags you write; the others stay.

“Send event” writes an event on the contact's profile. You write the event name yourself and build the automation in Omnisend with that name. Write properties one per line as “name: value”. If the contact isn't in Omnisend, they're added without being subscribed.

Support requests

When a visitor opens a support request and leaves their email, the “Agenola Support Request” event goes to Omnisend; the request's subject, the agent's name, its urgency and the request number are in the event's properties. You can build an automation or a segment on this event.

Campaigns

“Get campaigns” reads the latest 100 campaigns, “Get campaign” a campaign's name, subject and status.

“Replicate campaign” creates a draft copy of the campaign. “Send draft” sends a draft campaign you prepared in Omnisend to its recipients now; Omnisend doesn't send a campaign that isn't a draft. To send a sent campaign again, replicate it first.

Steps that can't be undone

The steps that send a draft, delete a campaign or unsubscribe a contact don't run until the confirmation box is ticked, and they have an hourly limit.

In these steps the email can't be a value the visitor typed. It has to be a fixed value, the result of an earlier step, or a record the visitor picked from a list.

Removing

Press “Disconnect”: Omnisend steps in your agents stop, support requests are no longer recorded in Omnisend, and Agenola's access in Omnisend is removed too. Your contacts stay in Omnisend.