--- title: "Omnisend Integration" description: "Feed your Omnisend ecommerce marketing from any workflow: agents sync contacts with tags and subscription status, trigger custom events that launch automations, add products to the catalog, and read campaigns and abandoned carts." url: https://flowrunner.ai/integrations/omnisend date_modified: 2026-08-04T10:04:16-07:00 --- # Omnisend [Email Marketing](https://flowrunner.ai/integrations/category/email-marketing) Feed your Omnisend ecommerce marketing from any workflow: agents sync contacts with tags and subscription status, trigger custom events that launch automations, add products to the catalog, and read campaigns and abandoned carts. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 9 actions · API key · available [Omnisend website](https://omnisend.com/) · [Platform Documentation](https://api-docs.omnisend.com/) · Capability data verified 2026-07-28 1. The morning recovery sweep starts on schedule 2. List Carts pulls the abandoned carts Omnisend has tracked, with contact email, total value, and line items 3. The agent matches each cart to a subscriber via List Contacts and separates high-value carts from the rest 4. Update Contact tags each matched contact with the abandoned product category for segmentation 5. The lifecycle marketer reviews the high-value list, because the event fired next launches a send sequence into real inboxes and phones 6. Trigger Event fires the recovery event for each approved contact, carrying cart value and items as custom fields 7. The recovery log posts to the team channel and appends to the tracking sheet ## What This Integration Enables Omnisend's automations are event-driven, which means the platform is only as smart as the event stream feeding it. Out of the box, that stream is whatever the store connector reports. FlowRunner widens it to your whole stack: agents sync contacts with tags and subscription status from any system, push products into the catalog that powers recommendations, and fire custom events that launch Omnisend automations, with a person approving the fires that trigger real sends. - Sync new customers and leads from stores, forms, and CRMs into Omnisend as subscribed contacts - Keep names, tags, and subscription status current so segmentation runs on facts - Fire custom events from any workflow to launch Omnisend automations, gated by [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) review where sequences reach customers - Load store products into the catalog behind recommendations and automations - Read campaigns and abandoned carts for reporting and revenue recovery ### Without FlowRunner **Automations starved of events**: Omnisend can only react to what it sees, so anything that happens outside the store, in the CRM, the billing system, the support desk, never starts a sequence **Contacts synced in batches**: Subscribers arrive by periodic import, tagged with whatever was true at export time **Abandoned carts noticed in reports**: Cart data piles up and gets reviewed when someone remembers, long after the shopper stopped caring ### With FlowRunner **Any system can start a sequence**: Custom events flow into Omnisend from the whole stack, so automations key on what customers actually did, wherever they did it **Contacts current at the moment of the event**: Subscribers are created and retagged as behavior happens, with subscription status handled explicitly **Recovery runs every morning with a reviewer**: High-value carts reach a person while they are still warm, and sequences fire only on approval ## Use Case Scenarios ### The welcome sequence that starts the moment they exist A new customer fires from [Shopify](https://flowrunner.ai/integrations/shopify). The agent checks List Contacts by email, calls Create Contact to add the shopper with Subscribed status and a source tag, then fires Trigger Event with the welcome event name and the first order's details as custom fields. The Omnisend welcome automation starts within the same minute the customer was created, keyed to data the sequence can actually personalize on. ### A catalog that matches the store Product recommendations are only as good as the catalog behind them. On a schedule, the agent pulls the store's products from Shopify and calls Create Product for each new item, with ID, title, status, URL, and price in minor units. When merchandising adds a product line, Omnisend's automations can recommend it that day instead of after the next manual sync. ### Abandoned carts triaged by value, chased with approval Each morning, List Carts returns the tracked carts with totals and line items. The agent logs everything to [Google Sheets](https://flowrunner.ai/integrations/google-sheets), then splits the list: standard carts feed the automated recovery event directly, while carts above the review threshold post to [Slack](https://flowrunner.ai/integrations/slack) with contact history attached. The marketer decides which high-value shoppers get the sequence and which get a personal note from sales instead. Recovery becomes a daily rhythm rather than a monthly regret. ## Human-in-Loop Highlight Trigger Event looks harmless in a flow diagram, one small write, but it is the ignition switch for every automation wired to that event name in Omnisend. Fire it and sequences start sending email and SMS to a real person, on a schedule you no longer control from the workflow. Fire it against the wrong segment and you have launched campaigns you cannot recall, to people who will read them as your brand's judgment. So FlowRunner treats event fires that lead to customer-facing sends as gated operations: the agent assembles the audience, attaches the evidence, and shows the marketer what will launch and for whom. The sequence runs at Omnisend's speed. The decision to light it runs at a person's. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 9 actions ### Contacts 4 - **List Contacts** Retrieves a paginated list of subscribers with filtering by email address and subscription status. Returns each contact's identifiers, name, tags, and channel statuses. The matching step behind every sync and recovery sweep. - **Get Contact** Retrieves a single contact by Omnisend contact ID, with identifiers, name, tags, custom properties, and channel subscription statuses. - **Create Contact** Creates a new subscriber from an email address with an initial email subscription status, plus optional first name, last name, and tags. The write that brings customers from the rest of the stack into the audience. - **Update Contact** Updates an existing contact by ID, changing only the provided fields. Used to retag, rename, or adjust subscription status without recreating the record. ### Events 1 - **Trigger Event** Triggers a custom event for a contact identified by email, carrying optional custom fields into the automations it starts. The event name must match one configured in Omnisend. The operation this page's human gate exists for. ### Products 2 - **List Products** Retrieves a paginated list of products from the Omnisend catalog with ID, title, status, price, and URLs. - **Create Product** Adds a product to the catalog with a unique ID, title, status, and URL, plus optional currency and price in minor units. Cataloged products power recommendations and automations. ### Campaigns 1 - **List Campaigns** Retrieves a paginated list of email and SMS campaigns with ID, name, type, status, and send date. The read behind campaign reporting. ### Carts 1 - **List Carts** Retrieves a paginated list of tracked shopping carts, including abandoned ones, with cart ID, contact email, currency, total value, and line items. The raw material of every recovery workflow. ## Frequently Asked Questions ### What can FlowRunner do with Omnisend? FlowRunner agents can run List Contacts, Get Contact, and Create Contact in Omnisend, plus 6 more actions. ### Does connecting Omnisend to FlowRunner require OAuth? No. Omnisend connects to FlowRunner with an API key, no OAuth flow required. ### Can Omnisend trigger a FlowRunner workflow automatically? Omnisend doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Omnisend?** This integration exposes Omnisend to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/omnisend. Site index: https://flowrunner.ai/llms.txt