Resources · Zapier integration

Omnisend Zapier integrationAutomate Omnisend with Zapier.

The Omnisend Zapier integration gives you 2 triggers, 72 actions and 8 searches to wire Omnisend contacts, campaigns, segments, products and automation workflows into a Zap, the automation you build on Zapier. Here is what each one does, what it costs and where it trips.

See the 82 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Omnisend Zapier integration actually does

It links your Omnisend account to Zapier so a change in one tool sets off work in Omnisend, or the other way round. On the Omnisend side the menu is wide: 82 visible operations, almost all of them actions that create, replace, send or remove something in your marketing account. The start of a Zap is narrower, since only contacts can set one off.

Three results come back again and again. First, a tidy contact base: New Contact starts the Zap, Batch Add Tags labels the person, and your segments pick them up without anyone touching a spreadsheet. Second, a campaign pipeline you can drive from outside: Create Campaign builds a draft, Send Campaign Test Email puts a preview in front of up to 5 reviewers, and Send Campaign releases it once someone signs off. Third, a catalog that stays in line with your shop: Create Product and Replace Product keep titles, product links and stock status matching what customers can actually buy.

Now the limits. Both triggers are polling ones, so nothing in Omnisend reaches Zapier the instant it happens: on the free plan, the gap can be up to 15 minutes. Nothing starts a Zap from a campaign, an order or a segment either; the only doors in are a new contact and an updated contact. And the free plan builds two-step Zaps only, so the campaign pipeline above, with its three actions, needs a paid plan.

If you are weighing other tools for the same job, the Omnisend Make integration covers the same app on Make.

Vocabulary

Zapier vocabulary in plain words

Eight words carry the whole page. Each one is used below exactly as defined here.

Zap
Your automation on Zapier: one trigger, then one or more actions that run every time that trigger event comes up.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something in an app for you.
Task
The unit Zapier bills. One task is one action your Zap completed successfully; your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, with no wait.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the following steps can reuse what it found.
Connection
Your Omnisend account linked to Zapier once, then reused by every step that talks to Omnisend.
Cost

What Omnisend on Zapier really costs

Omnisend is not reserved for paid plans: it works from the free plan. The bill is counted in tasks, and only a completed action is billed.

  • Trigger check0 tasks
  • Successful action1 task each
  • Free plan100 tasks a month, two steps per Zap
  • Paid plan needed?No, works on Free

The trigger never costs a task, however often Zapier checks for new contacts. Each action that goes through counts once, so a three-action Zap uses three times what a one-action Zap uses, and an action that fails is not counted. A few actions take more than one task. The free plan gives 100 tasks a month and two-step Zaps only: add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan.

Connect

Connect Omnisend to Zapier in 3 steps

  1. 01

    Open the connections page

    In your Zapier account, go to Apps and click + Add connection. You need an Omnisend account, plus read or write access to anything you do not own and want the Zap to touch.

  2. 02

    Pick Omnisend

    Type Omnisend in the search box of the dialog, select it from the results, then click Add connection. A new tab opens where Omnisend asks you to sign in to your account.

  3. 03

    Sign in and grant access

    Log in to Omnisend in that tab and allow Zapier to reach the account. The connection then shows up in every Omnisend step you add, so you never repeat this.

First Zap

Your first Omnisend Zap

GoalTag every new contact and log a matching customer event in Omnisend.

  1. 01

    Build the trigger

    Create a Zap, choose Omnisend as the app and New Contact as the event, then pick the connection you just added. This is the event that starts every run.

  2. 02

    Test it on real data

    Run the trigger test. Zapier brings back the three most recent contacts of the account, so you map the next steps on a real person rather than a blank sample.

  3. 03

    Add the tagging action

    Add Batch Add Tags, point it at the contact from the trigger, and type at least one tag; the field takes up to 100 of them.

  4. 04

    Log the event

    Add Send Customer Event and give it an Event Name. With three steps this is a multi-step Zap, so it needs a paid plan; on Free, keep the first action only.

  5. 05

    Test, then publish

    Test each step once and read what came back. When it looks right, publish the Zap to switch it on. Stuck on a step? The Zapier training walks through the editor.

Triggers

Omnisend triggers on Zapier

2 events start a Zap when something happens in Omnisend. Zapier checks for them at the interval your plan allows.

1

New Contact

Polling trigger

In Zapier“Triggers when a new contact is added.”

Starts your Zap each time a person lands in your Omnisend audience, whether they came from a signup form, an import or another tool. Everything you know about that contact at that point is handed to the next steps.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
welcome flows that live outside Omnisend, such as alerting a sales rep or adding the lead to a CRM.
Watch out
contacts that existed before you published the Zap are never picked up, so a backlog needs a separate import.
2

Updated Contacts

Polling trigger

In Zapier“Triggers when a contact is is last updated or created.”

Wakes up when a contact changes, and also when one is created, so it catches both new and edited profiles in a single trigger. Use it to keep a second system in step with Omnisend.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
syncing tag or consent changes back into a CRM or a reporting sheet.
Watch out
since creation counts too, running it beside New Contact on the same flow handles fresh contacts twice; and a Zap that edits contacts in Omnisend will set it off again.
Actions

Omnisend actions on Zapier

Omnisend gives you 72 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Batch Add Tags

Action

In Zapier“Adds the specified tags to contacts selected by contact IDs, emails, phone numbers or a segment.”

Puts one or more tags on contacts chosen by ID, email, phone number or segment.

When to use it
marking buyers of a product, webinar attendees or leads from a partner so segments sort them.
Watch out
the tag list needs at least 1 entry and holds up to 100.
2

Batch Remove Tags

Action

In Zapier“Removes the specified tags from contacts selected by contact IDs, emails, phone numbers or a segment.”

Takes tags off a set of contacts, picked the same ways as for adding them.

When to use it
clearing a "trial" tag when someone pays, or an event tag once the event is over.
Watch out
paired with Updated Contacts as trigger, removing tags edits the contact and can restart the same Zap.
3

Cancel Campaign

Action

In Zapier“Cancels a scheduled, sending, or paused campaign. Note: for campaigns that are already sending, cancellation is best-effort — messages already in flight may still be delivered.”

Stops a campaign that is scheduled, sending or paused.

When to use it
an emergency brake wired to a chat command when a mistake slips into a scheduled send.
Watch out
on a campaign already sending, messages in flight may still be delivered.
4

Copy Automation Workflow

Action

In Zapier“Create a copy of an existing automation workflow.”

Clones a workflow you already built, keeping its structure, so you start from something proven instead of a blank canvas.

When to use it
launching a seasonal variant of an abandoned-cart or welcome series.
Watch out
the step asks for the workflow ID, a 24-character code; List Automation Workflows is the quickest way to find it.
5

Copy Campaign

Action

In Zapier“Creates a draft copy of an existing campaign, including its content, audience, and settings. The copied campaign name will be prefixed with "Copy of: ".”

Duplicates an existing campaign into a fresh draft with the same content, audience and settings. Omnisend puts "Copy of: " in front of the name.

When to use it
rerunning a promotion that worked, then tweaking the draft before it goes out.
Watch out
you need the source campaign ID; the Find Campaigns search gets it for you.
6

Create Automation Workflow

Action

In Zapier“Create a new automation workflow.”

Sets up a brand-new Omnisend automation, with a name, the event that starts it and at least one block (a send, a delay, a split or an A/B test).

When to use it
agencies or multi-brand teams who stamp out the same flow across accounts.
Watch out
name, trigger and blocks are all required, so this step is easier to fill from a template than by hand.
7

Create Batch

Action

In Zapier“Batch operations allow for multiple actions of a similar type to be executed in a single request. Utilizing the batch endpoint is recommended to avoid hitting rate limits and to enhance overall performance.”

Bundles many similar writes into one go: up to 100 products, contacts, events or categories, created or replaced together.

When to use it
bulk syncs, where one Zap run carries a list rather than a single record.
Watch out
you pick the kind of record and whether items are created or replaced; mixing kinds in one batch is not possible.
8

Create Campaign

Action

In Zapier“Creates a new email campaign in Omnisend. The campaign will be created as a draft and can be scheduled or sent immediately.”

Builds a new campaign as a draft, ready to be scheduled or sent. You choose its channel and type when you set the step up.

When to use it
preparing a recurring newsletter shell from a content calendar so the team only fills in the copy.
Watch out
the booster type follows its own order of steps, with a parent campaign first, so try it by hand before automating it.
9

Send Customer Event

Action

In Zapier“Send new customer event”

Records something a customer did, under the Event Name you give, so Omnisend workflows can react to it.

When to use it
feeding actions from outside the shop, such as a demo booked or a support ticket closed, into your automations.
Watch out
a custom event works best once its shape is declared with Create Custom Event Metadata.
10

Create Custom Event Metadata

Action

In Zapier“Declares a new brand-custom event schema.”

Declares a new custom event type for your brand, so Omnisend knows its shape before any event arrives.

When to use it
before sending events like a quote request or a booking that Omnisend does not know out of the box.
Watch out
it needs a machine-readable name and a single origin; keep the name stable, other steps refer to it.
11

Create Email Template

Action

In Zapier“With this endpoint you can create a new email template.”

Saves a new reusable email template in the account, ready for campaigns and workflows to pick up.

When to use it
a design team that produces templates elsewhere and wants them filed in Omnisend automatically.
Watch out
if what you have is raw HTML, Import Email Template is the better fit.
12

Create Product

Action

In Zapier“Creates a new product”

Registers a product in your Omnisend catalog with its ID, title, currency, product page link and stock status.

When to use it
shops whose catalog lives in a tool Omnisend does not sync natively.
Watch out
status takes inStock, outOfStock or notAvailable; keep it aligned with the shop so out-of-stock items stay out of your emails. Title stops at 255 characters.
13

Create Product Category

Action

In Zapier“Creates a new product category”

Adds a category to the catalog, with its own identifier and a display title.

When to use it
mirroring a new collection from your store before products are attached to it.
Watch out
the identifier is yours to choose and must stay unique, between 1 and 100 characters; the title stops at 255.
14

Create Segment

Action

In Zapier“Creates a new segment.”

Opens a new segment in Omnisend, defined by a name and its groups of conditions.

When to use it
spinning up a segment for each new product line or event without clicking through the segment builder.
Watch out
the condition groups are required and must be well formed; test with a simple rule before trying anything clever.
15

Create or Replace Existing Contact

Action

In Zapier“Creates or updates a subscriber with all provided values, i.e. name, phone number, tag, etc. Use tag to be able to add subscribers to segment in Omnisend.”

Adds a subscriber to Omnisend, or overwrites the one already there, with name, phone number and tags in one go. Tags are what later drop the person into a segment.

When to use it
pushing leads from a form, a webinar tool or a checkout into your list.
Watch out
a welcome email goes out by default when your welcome workflow is on; switch Send Welcome Email off for imports.
16

Create Universal Layout

Action

In Zapier“With this endpoint you can create a new universal layout.”

Adds a new universal layout to your Omnisend account, which Find Universal Layouts can then list and Replace Universal Layout can rework.

When to use it
filing a layout prepared in another tool, so the team finds it in Omnisend instead of rebuilding it.
Watch out
keep the ID it returns; every later layout step, including deletion, asks for that 24-character code.
17

Delete Automation Workflow

Action

In Zapier“Delete a single automation workflow by ID. This operation is idempotent — deleting a non-existent automation returns a success response.”

Erases a workflow by its ID.

When to use it
tidying up copies made for a one-off campaign.
Watch out
deleting a workflow that no longer exists still reports success, so a green step does not prove anything was removed.
18

Delete Campaign

Action

In Zapier“Permanently deletes a campaign from your Omnisend account by its ID. Warning: this action cannot be undone.”

Removes a campaign from the account for good. You point it at the campaign through its ID.

When to use it
cleaning out test drafts created by another Zap.
Watch out
there is no undo; put a filter in front so only the right campaigns reach this step.
19

Delete Email Template

Action

In Zapier“Permanently deletes an email template from your Omnisend account by its ID. Warning: this action cannot be undone.”

Deletes an email template for good. It targets the template by ID, the same one an Import Email Template step returns.

When to use it
clearing out templates imported for a test run.
Watch out
permanent; Render Email Template first if you want an archived copy.
20

Delete Image

Action

In Zapier“Deletes an image from your Omnisend image library by its ID.”

Takes an image out of the Omnisend library. The picture leaves the library your templates draw on.

When to use it
removing a banner once its promotion has ended.
Watch out
permanent; get the ID from the Find Images search rather than guessing it.
21

Delete Product

Action

In Zapier“Delete product by ID”

Drops a product from the Omnisend catalog by its ID.

When to use it
a product discontinued in the shop that should stop showing up in recommendations.
Watch out
marking it outOfStock with Replace Product is gentler if it may come back.
22

Delete Product Category

Action

In Zapier“With this endpoint you can delete product category.”

Removes a category from the catalog. It works from the identifier you chose when the category was created.

When to use it
closing a collection that no longer exists in the store.
Watch out
the step only needs the category identifier, so double check it is the right one.
23

Delete Segment

Action

In Zapier“Permanently deletes a segment from your Omnisend account by its ID. Note: segments that are currently being built cannot be deleted.”

Removes a segment permanently. It works from the segment ID, which Find Segments returns.

When to use it
retiring segments created per event once the event is over.
Watch out
a segment still being built cannot be deleted, and a deleted one cannot be restored.
24

Delete Universal Layout

Action

In Zapier“With this endpoint you can delete a universal layout by ID.”

Removes a universal layout by its ID. The ID it asks for is a 24-character code.

When to use it
retiring the frame of a brand you no longer run.
Watch out
check no email still relies on it; Find Universal Layout helps you keep a copy first.
25

Disable Automation Workflow

Action

In Zapier“Disable an automation workflow. Once disabled, the workflow stops accepting new trigger events.”

Turns a workflow off; it stops accepting new events.

When to use it
closing a promotion flow the moment the offer ends in your shop.
Watch out
you must decide what happens to contacts already inside the workflow; that choice is required.
26

Enable Automation Workflow

Action

In Zapier“Enable an automation workflow. Once enabled, the workflow starts processing trigger events in real time.”

Switches a workflow on, so it begins handling the events that start it.

When to use it
turning on a seasonal flow on launch day from a project tool.
Watch out
by default only future events count; tick Enroll Existing if contacts who already qualify should enter too.
27

Find Image

Action

In Zapier“Returns a single image from your Omnisend image library by its ID.”

Returns one image of the library from its ID, sitting in the action list.

When to use it
retrieving the details of an image you just uploaded, to pass along to a template step.
Watch out
not the same as the Find Images search, which returns a list and is where you get the ID.
28

Find Aggregated UTM Tags for All Blocks

Action

In Zapier“Retrieve UTM tracking tags for all send-action blocks in an automation. Each block's tags include default-value synthesis for missing fields.”

Gathers the tracking tags of every send block in a workflow in one read, defaults included.

When to use it
auditing a long flow without opening each email.
Watch out
missing tags come back filled with default values, so an empty field in Omnisend may still show something here.
29

Find Automation Workflow

Action

In Zapier“Get a single automation workflow by ID.”

Returns one workflow with its settings, from its ID.

When to use it
before Patch or Replace, to read what is there and decide what to change.
Watch out
it needs the exact ID; List Automation Workflows gives you the list to pick from.
30

Find Batches

Action

In Zapier“Get batches. This endpoint is rate limited to 400 requests per minute.”

Lists the batches you sent for one kind of record: products, contacts or events.

When to use it
a follow-up Zap that checks recent bulk jobs.
Watch out
the record kind is required, so one step covers one kind only.
31

Find Batch Information

Action

In Zapier“Get batch information”

Tells you where a single batch stands, from its ID.

When to use it
after Create Batch, to know whether the bulk job went through before reporting it done.
Watch out
the ID comes from the Create Batch step; map it rather than retyping it.
32

Find Batch Items

Action

In Zapier“Get batch items by batch id”

Returns the individual items inside a batch. It looks past the batch as a whole and at each record inside it.

When to use it
finding which records of a bulk import failed, so only those are retried.
Watch out
needs the batch ID, the same one Find Batch Information uses.
33

Find Campaign UTM Settings

Action

In Zapier“Campaign ID (24 character hexadecimal)”

Reads the tracking tags currently set on a campaign.

When to use it
checking drafts against your naming rules before they go out, then flagging any that drift.
Watch out
the campaign ID is a 24-character code, so feed it from an earlier step rather than typing it.
34

Find Contact

Action

In Zapier“Returns the contact with the specified ID.”

Fetches one contact from its Omnisend ID and hands its details to the next step.

When to use it
enriching a message to sales with what Omnisend knows about the person.
Watch out
despite its name it sits among the actions, not under SEARCH, so a successful run counts as a task.
35

Find Email Content

Action

In Zapier“With this endpoint you can get email content by ID.”

Reads a piece of email content by its ID.

When to use it
right before Replace Email Content, so you edit the current version instead of starting cold.
Watch out
the ID is a 24-character code; map it from an earlier step.
36

Find Information About Brand

Action

In Zapier“With this endpoint you can get brand's information.”

Reads the brand details of the connected Omnisend account.

When to use it
agencies with several connections who want each Zap to confirm which brand it is writing to.
Watch out
it takes no input, so it always describes the account behind the current connection.
37

Find Product

Action

In Zapier“Get product by it's ID”

Looks up one catalog product from its ID and returns its details.

When to use it
checking stock status before sending an alert about a product.
Watch out
the ID is the one you gave the product at creation, not its title.
38

Find Product Category

Action

In Zapier“Get product category by ID.”

Returns one product category from its identifier. Nothing in the catalog changes while it reads.

When to use it
confirming a category exists before attaching new products to it.
Watch out
the identifier is the one chosen at creation; a typo returns nothing useful.
39

Find Segment

Action

In Zapier“Returns a segment by its unique identifier.”

Pulls a single segment by its 24-character ID, from the action list.

When to use it
when the ID already travels through the Zap and you want the segment's details.
Watch out
a search called Find Segment also exists under SEARCH; the search version carries the settings for empty results.
40

Find Universal Layout

Action

In Zapier“With this endpoint you can get a universal layout by ID.”

Returns one universal layout from its ID. Whatever it returns can feed any later step of the Zap.

When to use it
backing up a layout before a Replace Universal Layout step overwrites it.
Watch out
you need the exact ID; Find Universal Layouts lists them.
41

Find Universal Layouts

Action

In Zapier“With this endpoint you can get a paginated list of universal layouts.”

Lists your universal layouts, page by page. Each layout returned can then feed a later step.

When to use it
picking which layout a later step should copy or update.
Watch out
paginated results mean a long list may not arrive in one run.
42

Find UTM Tags for an Automation Block

Action

In Zapier“Retrieve UTM tracking tags for a specific send-action block. Missing or cleared tags are returned with their default values.”

Pulls up the tracking tags of one send block, by workflow ID and block identifier.

When to use it
just before Replace UTM Tags for an Automation Block, to keep the values you are not changing.
Watch out
cleared tags return their defaults, not blanks.
43

Import Email Template

Action

In Zapier“Imports an email template from raw HTML content into Omnisend. The HTML will be parsed and structured into a reusable template.”

Turns raw HTML into a structured Omnisend template you can reuse.

When to use it
moving templates out of another email tool, or publishing HTML that a designer drops in a shared folder.
Watch out
the template name stops at 255 characters and the whole request at 1MB, so heavy inline images will push you over.
44

List Automation Workflows

Action

In Zapier“List automation workflows with filtering, sorting, and cursor-based pagination.”

Brings back your workflows, with the option to keep only enabled or only disabled ones.

When to use it
an audit sheet of what is live, kept for the team.
Watch out
results are paginated, so a large account may need several runs.
45

List Campaigns With Filtering, Sorting, and Cursor Pagination

Action

In Zapier“List campaigns with filtering, sorting, and cursor-based pagination.”

Lists campaigns with filters and sorting, one page at a time.

When to use it
building a calendar of what went out, for a team that does not log in to Omnisend.
Watch out
to locate a single campaign for a later step, the Find Campaigns search is simpler.
46

List Contacts

Action

In Zapier“Returns a paginated list of contacts filtered by the provided query parameters.”

Returns a page of contacts that match the filters you set.

When to use it
a snapshot of a slice of your audience sent to a sheet for a one-off review.
Watch out
results come page by page, so one run will not always carry the whole list.
47

List Products

Action

In Zapier“List products of store”

Lists the products in your Omnisend store catalog.

When to use it
comparing the Omnisend catalog with the shop to spot products that never synced.
Watch out
a big catalog comes back in pages, so plan for more than one run.
48

List Product Categories

Action

In Zapier“List products categories”

Brings back all the categories of your catalog. The catalog itself stays untouched while it reads.

When to use it
keeping a reference sheet so the team uses the same category identifiers everywhere.
Watch out
it reads only; renaming happens with Replace Product Category.
49

Patch Automation Workflow

Action

In Zapier“Partially update an automation workflow. Only the fields provided in the request body are updated.”

Changes only the parts of a workflow you provide and leaves the rest alone.

When to use it
renaming a workflow or adjusting one setting without rebuilding its blocks.
Watch out
to change the blocks themselves, Replace Automation Workflow Blocks is the step to use.
50

Query Events Metadata

Action

In Zapier“Returns event metadata entries for the given category, optionally filtered by event names and/or origins.”

Lists the event types Omnisend knows for a category, optionally narrowed by name or origin.

When to use it
checking that a custom event is declared before Send Customer Event uses it.
Watch out
excluding custom events keeps the answer shorter and more predictable; include properties only when you need them.
51

Render Email Content

Action

In Zapier“With this endpoint you can render email content to HTML by ID. The content is rendered with an empty data context (no contact, no marketing activity).”

Turns a piece of email content into HTML, with no contact and no campaign data filled in.

When to use it
a visual check of the bare content before it is merged into a send.
Watch out
personalisation stays empty, so a preview with merge tags will look blank in places.
52

Render Email Template

Action

In Zapier“Renders an email template by ID and returns the full HTML output. Useful for previewing template content or passing rendered HTML to other steps in your Zap.”

Produces the full HTML of a template so the next step in the Zap can use it.

When to use it
archiving a copy of each template in a document tool, or showing it to a client for approval.
Watch out
you need the template ID; Find Email Templates returns it.
53

Replace Automation Workflow Blocks

Action

In Zapier“Replace the full block tree for an automation workflow.”

Rebuilds the whole block tree of a workflow from the list you send.

When to use it
deploying an updated version of a flow across several accounts.
Watch out
any existing block missing from your list is removed, and at least one block is required.
54

Replace Product

Action

In Zapier“Replace product by ID”

Overwrites a catalog product with fresh details: title, currency, link and stock status.

When to use it
a price or stock change in your inventory tool that Omnisend must reflect.
Watch out
it replaces the whole product, so send every required field each time, not just the one that moved.
55

Resume A/B Test

Action

In Zapier“Resume a stopped A/B test. Automatic winner selection becomes eligible to pick this campaign again. Available only while the campaign is in stopped status.”

Restarts a stopped A/B test, so automatic winner selection can pick again.

When to use it
the second half of a review loop that began with Stop A/B Test.
Watch out
available only while the campaign is in stopped status.
56

Select A/B Test Winner

Action

In Zapier“Manually pick a variant as the winner. The chosen variant is routed into the send pipeline immediately.”

Crowns a variant by hand and sends it on its way to the rest of the audience.

When to use it
when a decision comes from outside Omnisend, such as sales figures in another tool.
Watch out
the winner goes into sending at once, so there is no second chance.
57

Send Campaign

Action

In Zapier“Starts the sending process for a campaign. Immediate campaigns are sent right away; scheduled campaigns are queued for their scheduled send time.”

Launches a campaign: an immediate one leaves straight away, a scheduled one joins the queue for its slot.

When to use it
releasing a campaign after an approval in a project tool or a chat app.
Watch out
the campaign has to be in draft status, or the step refuses it.
58

Send Campaign Test Email

Action

In Zapier“Render the campaign draft and email it to up to 5 recipients so the merchant (or their AI tool) can preview it without leaving the API. The test uses the campaign's saved subject, sender, and content; only email campaigns are supported.”

Mails a preview of a draft campaign, with its saved subject, sender and content, to up to 5 people.

When to use it
sending every new draft to the reviewers before anyone clicks send.
Watch out
email campaigns only; SMS and other channels are not covered.
59

Send Test Automation Email

Action

In Zapier“Send the saved email content of a specific email block as a test email to up to 5 recipients. The email is rendered and delivered asynchronously.”

Fires a test of one email block inside a workflow to between 1 and 5 recipients.

When to use it
checking each email of a freshly copied workflow before you enable it.
Watch out
delivery happens in the background, so a passing Zap step does not mean the email has landed yet.
60

Stop A/B Test

Action

In Zapier“Halt the A/B test winner-selection phase. While stopped, automatic winner selection no longer considers this campaign until it is resumed. Available only while the campaign is in started status.”

Pauses the winner-picking phase of an A/B test, so no variant is chosen automatically meanwhile. Resume A/B Test undoes it later on.

When to use it
freezing a test while someone reviews early results.
Watch out
only works while the campaign is in started status.
61

Replace Campaign

Action

In Zapier“Updates an existing draft campaign in Omnisend. Only campaigns in draft status can be updated. Note: sending settings use full object replacement — if updating any sending setting, all sending fields must be provided.”

Rewrites a draft campaign in place.

When to use it
filling a draft built by Create Campaign with copy approved in a document tool.
Watch out
only drafts can be changed, and sending settings are replaced as a whole: touch one of them and you must provide all of them again.
62

Replace Campaign UTM Settings

Action

In Zapier“Replace UTM tag settings for a campaign. For regular campaigns send a tags object. For A/B test campaigns send a variants object. The campaign must be in draft status.”

Swaps the tracking tags attached to a campaign's links for new ones.

When to use it
enforcing your analytics naming rules on every draft the team prepares.
Watch out
the campaign must still be a draft, and A/B test campaigns take tags per variant rather than one set.
63

Replace Contact by ID

Action

In Zapier“Updates the contact with the specified ID.”

Updates a contact you identify by its Omnisend ID.

When to use it
when an earlier step, such as New Contact or Find Contact, already handed you the ID.
Watch out
run from an Updated Contacts Zap, this edit is itself an update and sets the trigger off again.
64

Replace Contact by Email

Action

In Zapier“Updates the contact matching the provided email address.”

Edits the contact that matches an email address, which is often the only key another tool shares with Omnisend.

When to use it
a CRM or a helpdesk pushes a change and only knows the customer's email.
Watch out
the address must match an existing contact; to create when missing, Create or Replace Existing Contact fits better.
65

Replace Custom Event Metadata

Action

In Zapier“Merges changes into an existing brand-custom event, identified by name and origin”

Merges changes into a custom event type you declared earlier, found by its name and origin.

When to use it
adding a new property to an event your site already sends.
Watch out
name and origin must match the original exactly, or Omnisend will not find the event.
66

Replace Email Content

Action

In Zapier“With this endpoint you can update (fully replace) email content by ID. The full content structure must be provided in the request body.”

Swaps out a piece of email content by its ID with a complete new structure.

When to use it
rare, mostly for teams generating email content from another system.
Watch out
you must send the full structure each time; a partial update will not merge.
67

Replace Email Template

Action

In Zapier“With this endpoint you can update (fully replace) an email template by ID.”

Puts a new version of an email template in place of the old one.

When to use it
pushing the latest approved design into Omnisend from wherever the team edits it.
Watch out
it is a full replacement, so anything you leave out of the new version is gone.
68

Replace Product Category

Action

In Zapier“Update product category by ID.”

Renames or refreshes an existing product category.

When to use it
a collection renamed in the store that should read the same in Omnisend.
Watch out
both the category identifier and the title are required, and the title stops at 255 characters.
69

Replace Segment

Action

In Zapier“Updates an existing segment by ID. The segment must not be in a building state to be updated. If the segment is currently being built, a 409 Conflict error is returned.”

Changes the name and conditions of an existing segment.

When to use it
moving a date threshold or a tag rule from a planning sheet.
Watch out
a segment that Omnisend is still building cannot be changed; the step fails until the build ends.
70

Replace Universal Layout

Action

In Zapier“With this endpoint you can update (fully replace) a universal layout by ID.”

Overwrites an existing universal layout, picked by its ID, with the version you send.

When to use it
pushing the approved version of a layout into Omnisend once it has been signed off elsewhere.
Watch out
it is a full replacement, so save the current version with Find Universal Layout first.
71

Replace UTM Tags for an Automation Block

Action

In Zapier“Set UTM tracking tags for a specific send-action block. All three tag fields are replaced atomically. Send an empty string to clear a field — the next read will return its default value.”

Sets the tracking tags of one send block inside a workflow, all three at once.

When to use it
aligning workflow emails with the tagging rules of your analytics.
Watch out
an empty value clears that tag, and the next read shows its default instead.
72

Upload Image

Action

In Zapier“Uploads an image to your Omnisend image library, making it available for use in email templates.”

Pulls an image from a public link into your Omnisend image library, where email templates can use it.

When to use it
filing product shots or banners produced in a design tool.
Watch out
the link must be publicly reachable, and only JPEG, PNG, GIF and WebP up to 5MB go through.
Searches

Omnisend searches on Zapier

8 search steps look for data that already exists in Omnisend, so a later step can use it.

A search step finds something already in Omnisend and passes it on. In the editor, these eight sit at the bottom of the Action event list, under SEARCH. Like a filter, a search makes the Zap multi-step. Whether a search wants an exact value or a close one is up to Omnisend, not Zapier.

1

Find Campaign

Search

In Zapier“Returns a single campaign from your Omnisend account by its ID.”

Retrieves one campaign from its ID and makes its details available downstream.

When to use it
when an earlier step carries the campaign ID and you need its status before sending or cancelling.
Watch out
it looks up by ID only; to locate a campaign by name, use Find Campaigns.
2

Find Campaigns

Search

In Zapier“Returns a list of campaigns from your Omnisend account. Supports filtering by status, channel, name, and date ranges.”

Returns campaigns filtered by status, channel, name or date range.

When to use it
getting the ID that Send Campaign, Copy Campaign or Delete Campaign ask for.
Watch out
with several matches the Zap keeps the first by default; tighten the filters or change that setting.
3

Find Email Template

Search

In Zapier“Returns a single email template from your Omnisend account by its ID.”

Fetches a single template from its ID. What it finds then feeds the steps after it.

When to use it
before Render Email Template, to confirm the template is still there.
Watch out
the ID comes from Find Email Templates or from an Import Email Template step.
4

Find Email Templates

Search

In Zapier“Returns a list of email templates from your Omnisend account. Supports filtering by name and sorting by creation date or name.”

Lists templates, with filtering by name and sorting by creation date or name.

When to use it
picking the most recent template whose name follows your convention.
Watch out
sort order decides which one comes first, and the first is what the Zap keeps by default.
5

Find Images

Search

In Zapier“Returns a list of images from your Omnisend image library. Optionally filter by name or other parameters.”

Searches the image library, optionally by name. What comes back is a list of the matching images.

When to use it
finding a banner's ID before Delete Image or Find Image.
Watch out
Max Results is required; left unset it defaults to 100 images.
6

Find Segment

Search

In Zapier“Returns a single segment from your Omnisend account by its ID.”

Checks for one segment by ID as a proper search step, with the no-result setting available.

When to use it
a Zap that should go on quietly when the segment has been removed.
Watch out
there is also an action with the same name; pick the one under SEARCH if you want that setting.
7

Find Segments

Search

In Zapier“Returns a list of segments from your Omnisend account. Supports filtering by name and sorting by creation date or name.”

Lists segments, filtered by name and sorted by creation date or name.

When to use it
getting the ID that Replace Segment, Delete Segment or Find Segment Statistics require.
Watch out
similar names can match together; keep segment names distinct.
8

Find Segment Statistics

Search

In Zapier“Returns statistics for a segment, including the total number of matching contacts.”

Returns figures on a segment, including how many contacts match it. Nothing about the segment itself changes along the way.

When to use it
posting a segment's size to a team channel before a campaign goes out.
Watch out
needs the segment ID, which Find Segments provides.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty search stops the Zap and skips the steps that relied on it. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Omnisend offers no find-or-create variant on its searches, so it does not come into play here.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or hand all of them on.
When it breaks

When the Omnisend Zap breaks

Zapier attaches no help article of its own to Omnisend. What breaks comes from Zapier's general limits and from the conditions the operations set.

Zapier remembers which contacts it has already seen on a polling trigger, so one contact does not start the Zap twice. The rest needs watching. For a broader method, see Zapier troubleshooting.

  • The past is never picked up

    A Zap reacts only to what happens after you switch it on. Contacts already in Omnisend stay out; moving that backlog is a separate job.

  • The Zap that sets itself off

    Updated Contacts plus a step that edits contacts in Omnisend (tags, Replace Contact) makes a loop that runs again and again and eats through your tasks.

  • A bulk import held back

    Import a large list into Omnisend and the trigger suddenly returns a huge batch. Zapier's flood protection can hold those runs back.

  • Campaign in the wrong status

    Send Campaign and Replace Campaign want a draft, Stop A/B Test a started campaign, Resume A/B Test a stopped one. Any other status and the step fails.

  • Segment still being built

    Replace Segment and Delete Segment refuse a segment Omnisend is still building. Retry once the build is done.

  • Deletions with no way back

    Delete Campaign, Delete Email Template, Delete Segment and Delete Image are permanent. Put a filter before them so a wrong match never gets there.
Need help

Need help automating Omnisend with Zapier?

A person reads every message.

FAQ

Omnisend Zapier integration: questions

01Is the Omnisend Zapier integration free?
Yes, Omnisend is not reserved for paid plans, so it works on the free Zapier plan. That plan gives you 100 tasks a month and an unlimited number of Zaps, with Zapier checking for new contacts every 15 minutes. The catch is the shape of the Zap: on Free, a Zap holds two steps only, one trigger and one action. Add a second action, a filter or a search, and it becomes a multi-step Zap that needs a paid plan. For a simple flow, such as tagging each new contact, the free plan is enough.
02How many tasks does an Omnisend Zap use?
One task per action that completes successfully, and nothing for the trigger. Zapier can check Omnisend for new contacts as often as your plan allows without charging anything for those checks. A Zap with New Contact and Batch Add Tags uses one task per new contact; add Send Customer Event and it uses two. An action that fails is not billed. Note that the operations named Find or List in the action list are actions too, so each successful run of one counts. A few actions on Zapier can take more than one task.
03Is Omnisend on Zapier real time?
No. Both Omnisend triggers, New Contact and Updated Contacts, are polling triggers: Zapier goes to check Omnisend at a fixed interval. That interval depends on the plan: 15 minutes on Free, 2 minutes on Professional, 1 minute on Team and Enterprise. On paid plans you can also change how often a polling trigger checks, and run a check by hand from the editor. The type is set by Omnisend's side and cannot be switched in the editor, so a faster plan is the only way to shorten the wait.
04What does it take to connect Omnisend to Zapier?
An Omnisend account, plus read or write access to anything you do not own and want the Zap to touch. In Zapier, open Apps, click + Add connection, search for Omnisend and click Add connection. A tab opens where you sign in to Omnisend and grant Zapier access. The connection is saved once and reused by every Omnisend step afterwards. Most actions that work on an existing item also ask for its ID, so have the campaign, segment or workflow ready in Omnisend before you build.
05Why does Updated Contacts also fire on new contacts?
Because Omnisend defines it that way: the trigger reacts when a contact is updated or created. A Zap built on it therefore sees fresh signups as well as edits. Two consequences follow. Running it alongside a New Contact Zap on the same flow processes new people twice. And any step in the same Zap that edits contacts, such as Batch Add Tags or Replace Contact by Email, counts as an update, which starts the Zap again in a loop that burns tasks. Use a filter, or keep tagging Zaps on New Contact.
06What if the Omnisend operation you want is not listed?
Then the Zapier integration does not offer it today. The 72 actions and 8 searches on this page are everything visible in the editor for Omnisend. Before giving up, check two places. Several reading operations are filed as actions, not searches, under names starting with Find or List. And Create Batch handles bulk work on products, contacts, events and categories, up to 100 items at a time. If the job still is not covered, it has to be done inside Omnisend itself or with a different automation tool.
07Zapier, Make or n8n for Omnisend?
Decide on criteria rather than on a ranking. On Zapier, Omnisend gives 82 visible operations, both triggers are polling ones checked every 15 minutes on Free, and the free plan stops at two-step Zaps. If waiting for the next check is fine and your flows are short, that covers a lot. If you need many steps, filters and searches in one flow, compare what each tool charges for that volume. And if a start point other than a contact matters to you, check whether the other tool exposes it for Omnisend.
Same platform

Other docs you might need on this stack.

Browse all integrations