Marketing Automation · Integration
Omnisend
Add Omnisend to your product for your customers, and give your AI agents governed access to it.
Omnisend is ecommerce marketing automation and its API at api.omnisend.com/v3 authenticates with an X-API-KEY header. Contacts carry separate opt-in status per channel, so an address can be subscribed for email and non-subscribed for SMS on the same record, and writing a contact without stating the channel status leaves consent unchanged rather than defaulting to subscribed. Beyond contacts, the API covers products, carts and orders, and it is these ecommerce objects that drive the abandoned cart and browse abandonment automations rather than any campaign call. Custom events are how you start a workflow from your own application: you post an event with a name and properties and the matching automation triggers, which is more reliable than trying to add contacts to a campaign directly. Campaigns themselves are largely built in the interface, so treat the API as the data and trigger layer. fastn stores each customer's Omnisend key separately and keeps the connection working as keys rotate.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Omnisend account so their contacts and segments sync with your product
Push order, cart and product data so abandoned cart automations fire with accurate content
Send custom events from your app to start an Omnisend workflow at the right moment
Keep per-channel email and SMS consent in step between your product and Omnisend
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent update contact tags and custom properties while consent changes need human approval
Have an agent report which automations a contact has entered, audited per tenant
Let an agent look up campaign and automation performance without being able to send anything
Example prompt
Which Omnisend automation is bringing in the most revenue for my store this month?
Set up Omnisend in 4 steps
- 01Enable the Omnisend connector from your fastn dashboard.
- 02Have each customer authorise their own Omnisend account, so calls run under their credentials rather than a shared key.
- 03Decide which campaigns, segments and subscribers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Omnisend integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Omnisend integration without building it. Your customers connect their own Omnisend account inside your product and work their campaigns, segments and subscribers there, with no per-customer code on your side.
- Handle the part that actually costs time: engagement data arrives as a high-volume event stream, so ordering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Omnisend update is not your on-call problem.
- One integration serves your product and your agents. The same governed Omnisend connection powers in-product features and gives AI agents scoped, audited access, so you trigger and measure campaigns from inside your product without wiring it twice.
Used by these teams
Compare with
Mailchimp
Marketo
Google AdsOften used alongside
Tools the same teams tend to run next to Omnisend, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMOmnisend integration FAQ
How do I add an Omnisend integration to my product?
Enable the Omnisend connector in your fastn dashboard, then let each customer authenticate their own Omnisend account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Omnisend client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Omnisend account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Omnisend account and only ever sees their own campaigns, segments and subscribers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Omnisend integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent update contact tags and custom properties while consent changes need human approval
Who maintains the Omnisend integration?
fastn does. When Omnisend changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I trigger an Omnisend campaign from an event in my product?
Yes. Product events can start a campaign, add a contact to a segment, or enrol someone in a journey, so lifecycle messaging follows what a user actually did rather than a nightly export.
Can I read engagement results back from Omnisend?
Yes. Results come back scoped per tenant, so your product can act on them without one customer's data mixing with another's. What you get depends on the channel: opens, clicks, bounces and unsubscribes where there are sends, and impressions, spend and conversions where there are campaigns.
What can I build with the Omnisend integration?
A common starting point: let a customer connect their own Omnisend account so their contacts and segments sync with your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Omnisend integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Omnisend does not change your per-connector cost. You can start free with 3 connected accounts.
Add Omnisend to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.