Skip to main content
Egentify’s AI agent handles customer support across chat, voice, and email. Connecting Omnisend puts the signals from those conversations into your automations: when a customer adds to cart from chat, escalates a conversation, or has a ticket resolved, Omnisend hears about it. Omnisend is one-way. Egentify writes events to it and reads nothing back. For the full list of events and how consent is handled, see the marketing overview.

Connect Omnisend

There is no API key to paste. Omnisend uses a one-click approval flow.
1

Turn Omnisend on

In your Egentify dashboard, go to Store Settings > Integrations and toggle Omnisend on.
2

Click Connect with Omnisend

You are sent to Omnisend to approve the connection.
3

Approve the permissions

Omnisend asks for access to contacts, events, and segments. Approve to return to Egentify.
Omnisend’s approval screen lists read permissions for contacts and segments. Egentify only uses contact access once, to confirm the connection works. It does not read your contacts or segments during conversations.

Signed-in customers only

Omnisend receives nothing for anonymous visitors. Every Omnisend event requires a verified email from a signed-in storefront session, so guest add-to-cart signals from chat never reach it.
If you want chat signals for logged-out shoppers, Klaviyo is the integration that supports it. Omnisend also receives a smaller set of events than Klaviyo. Ticket updates and reopenings are not sent, and neither are product-shown or customer-identified events. The event table shows exactly which events reach which platform.

Disconnecting and reconnecting

Toggling off pauses the integration and keeps the connection. Events stop. Disconnect removes the connection from Egentify’s side.
Disconnecting inside Egentify does not revoke Egentify’s access at Omnisend, because Omnisend provides no way to do that. To revoke access fully, also remove the app inside Omnisend.
The connection does not expire on its own, so it only breaks if you remove the app inside Omnisend. If that happens, the card reads Connection lost with a Reconnect link, and an amber dot appears on the Integrations tab. Nothing emails you, so check settings if events stop arriving.

Reliability

Events that fail for a temporary reason are retried up to five times.
Omnisend does not guarantee deduplication for real-time automation events, so a retried delivery could in principle trigger an automation more than once. Keep that in mind for automations that do something irreversible, like issuing a discount code.