Adds the specified tags to contacts selected by contact IDs, emails, phone numbers or a segment. At least one of contactIDs, emails, phones or segmentID is required. Selectors can be combined and are applied additively — the union of all matched contacts is tagged: every contact in contactIDs, every contact matched by an address in emails, every contact matched by a number in phones and every member of segmentID. A contact matched by more than one selector is tagged once. Emails and phones with no matching contact are silently ignored. Tagging is performed asynchronously, so the tags may not be visible immediately.

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.

Removes the specified tags from contacts selected by contact IDs, emails, phone numbers or a segment. At least one of contactIDs, emails, phones or segmentID is required. Selectors can be combined and are applied additively — the tags are removed from the union of all matched contacts: every contact in contactIDs, every contact matched by an address in emails, every contact matched by a number in phones and every member of segmentID. A contact matched by more than one selector is processed once. Emails and phones with no matching contact are silently ignored. Untagging is performed asynchronously, so the tags may not disappear immediately.

Cancels a campaign that is currently scheduled or in progress in Omnisend.

Creates a copy of an existing campaign in Omnisend.

Creates a new email, SMS or push campaign in Omnisend.

[v3 Legacy] Creates a custom event definition in Omnisend using the v3 API. For new scenarios, use the Send a Custom Event module which uses the 2026-03-15 API.

Declares a new brand-custom event schema. The event identity is the combination of name and origin; displayName and at least one top-level property are required. Optional metadata fields must be omitted rather than sent as null. The created event is returned with every node flagged explicitlyDefined.

Creates a structured email template using Omnisend's section/row/column/block system. Building sections from scratch by hand is complex — for most use cases, use Get an Email Template first to fetch an existing template's JSON structure, modify it, then feed it into this module instead of composing sections manually.

Creates a new contact or updates an existing one (upsert) based on email or phone number. Supports subscription status, profile fields, tags, and custom properties.

Creates a new product

Creates a new product category

Creates a new segment.

With this endpoint you can create a new universal layout.

Deletes a campaign from Omnisend by campaign ID.

Deletes a segment from Omnisend by segment ID.

Deletes an email template from Omnisend by template ID.

Deletes an image from Omnisend by image ID.

Delete product by ID

With this endpoint you can delete product category.

With this endpoint you can delete a universal layout by ID.

Get UTM tag settings for a campaign. The response shape is the same for all campaign types: tags is populated for regular campaigns, variants for A/B campaigns. The absent field is omitted.

With this endpoint you can get a single image by ID.

Get product by ID

Get product category by ID.

Imports an email template into Omnisend from raw HTML.

[v3 Legacy] Performs an arbitrary authorized API call against the Omnisend v3 API. Note: this module uses the v3 API which returns contactID for contact identifiers. New modules in this app use the latest API and return id instead. If connecting this module to newer Omnisend modules, map accordingly.

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

Renders an email template in Omnisend and returns the final HTML output.

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).

Replace product by ID

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.

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

Starts the sending process for a campaign in Omnisend.

Sends a custom or recommended event to Omnisend. Supports contact identification by email or phone and custom event properties to trigger automations and track customer behavior.

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.

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.

[v3 Legacy] Triggers a pre-created custom event for a contact using the v3 API. For new scenarios, use the Send a Custom Event module which uses the 2026-03-15 API.

Updates a draft campaign's name, language, email content, or sending schedule. Only the fields you fill in are changed - everything else stays as-is. Important: if you edit "Email Content Changes," you must provide both Subject and Sender Name together (Omnisend requires both whenever email content is touched). Important: Sending Strategy, Scheduled At, and Timezone Optimization are replaced as a single unit — if you set Sending Strategy, set all three together (leave Scheduled At blank only for "Send Immediately"). Partial values are not merged; they overwrite the current schedule entirely. Tip: Chain a "Get a Campaign" step before this one to fetch current values first.

Updates an existing contact in Omnisend by contact ID

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.

Updates the contact matching the provided email address.

Merges changes into an existing brand-custom event, identified by name and origin. Only supplied fields are applied: omitted metadata and omitted properties are preserved, and no property is deleted. The type of an already explicitly-defined property cannot change. Optional metadata fields must be omitted rather than sent as null. The merged event is returned.

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

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

Update product category by ID.

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.

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

Uploads an image to Omnisend by URL.

With this endpoint you can upload an image file directly from your computer.