Omnisend integration | Zervanor
← All connectors

Omnisend

Also an agent tool
marketing

Omnisend email & SMS marketing: sync contacts, run campaigns, push carts/orders/products/categories, trigger custom events, and bulk-import via batches.

40 actions · 2 triggers

The Omnisend integration lets you connect Omnisend to your automations with 40 actions and 2 triggers — and every action is also a tool an AI agent can call. Examples: List Contacts, Create or Update Contact, Get Contact, Update Contact, Update Contact by Email. No blank-canvas wiring — connect it and use it in your workflows.

Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.

Triggers 2

Events in Omnisend that can start a workflow.

polling

New or updated Omnisend contacts (polled)

Polls GET /contacts on a schedule with an updatedAtFrom watermark; dedupe by contactID.

polling

New Omnisend orders (polled)

Polls GET /orders on a schedule paging by offset; dedupe by orderID.

Actions 40

What Zervanor can do in Omnisend.

Carts9

GET

List Carts

List carts (GET /carts). Offset pagination.

POST

Create Cart

Create a new cart, typically to power abandoned-cart automations (POST /carts).

GET

Get Cart

Get a cart by id (GET /carts/{cartID}).

PATCH

Update Cart

Update a cart's info or products (PATCH /carts/{cartID}).

DELETE

Delete Cart

Delete a cart by id (DELETE /carts/{cartID}).

POST

Add Product to Cart

Add a line item (product) to a cart (POST /carts/{cartID}/products).

PUT

Replace Cart Product

Replace an existing cart line item — change product, quantity, or price (PUT /carts/{cartID}/products/{cartProductID}).

PATCH

Update Cart Product

Partially update an existing cart line item (PATCH /carts/{cartID}/products/{cartProductID}).

DELETE

Remove Cart Product

Remove a line item from a cart (DELETE /carts/{cartID}/products/{cartProductID}).

Contacts7

GET

List Contacts

List contacts, optionally filtered by email, phone, status, tag, segment, or update time (GET /contacts). Offset pagination. Recommended polling action for new/updated contacts.

POST

Create or Update Contact

Create a new contact or update an existing one, matched by identifiers (POST /contacts).

GET

Get Contact

Get a single contact by its Omnisend contact id (GET /contacts/{contactID}).

PATCH

Update Contact

Update an existing contact by its Omnisend contact id (PATCH /contacts/{contactID}).

PATCH

Update Contact by Email

Update an existing contact identified by email (PATCH /contacts).

POST

Add Contact Tags

Batch-add tags to contacts (POST /contacts/tags).

DELETE

Remove Contact Tags

Batch-remove tags from contacts (DELETE /contacts/tags).

Products6

GET

List Products

List products in the catalog (GET /products). Offset pagination.

POST

Create Product

Add a product to the catalog (POST /products).

GET

Get Product

Get a single product by id (GET /products/{productID}).

PUT

Replace Product

Replace a product's full definition (PUT /products/{productID}).

PATCH

Update Product

Partially update a product (PATCH /products/{productID}).

DELETE

Delete Product

Delete a product from the catalog (DELETE /products/{productID}).

Categories5

GET

List Categories

List product categories (GET /categories). Offset pagination.

POST

Create Category

Create a product category (POST /categories).

GET

Get Category

Get a single product category by id (GET /categories/{categoryID}).

PUT

Update Category

Update a product category (PUT /categories/{categoryID}).

DELETE

Delete Category

Delete a product category by id (DELETE /categories/{categoryID}).

Batches4

GET

List Batches

List bulk-import batches for a given endpoint (GET /batches). Offset pagination.

POST

Create Batch

Create a bulk-import batch of contacts, products, or events (POST /batches).

GET

Get Batch

Get a batch's status and summary (GET /batches/{batchID}).

GET

Get Batch Items

Get the per-item results of a batch (GET /batches/{batchID}/items).

Campaigns4

GET

List Campaigns

List campaigns, optionally filtered by status or type (GET /campaigns). Offset pagination.

POST

Create Campaign

Create a new campaign (POST /campaigns).

GET

Get Campaign

Get a single campaign by id (GET /campaigns/{campaignID}).

POST

Send Campaign

Send (dispatch) a campaign (POST /campaigns/{campaignID}/send). No request body.

Orders4

GET

List Orders

List orders, optionally filtered by contact/cart/date/status (GET /orders). Offset pagination. Recommended polling action for new/updated orders.

POST

Create Order

Create a new order (POST /orders). One of email, phone, or contactID is required to attach the order to a contact.

GET

Get Order

Get a single order by id (GET /orders/{orderID}).

PATCH

Update Order

Update an order's status or fields (PATCH /orders/{orderID}).

Events1

POST

Trigger Custom Event

Send a customer event to trigger automations; the contact is created or updated from the event data (POST /events).

Automations using Omnisend

Build your own automation with Omnisend in the visual builder.

Frequently asked questions

What can I automate with Omnisend?

40 actions are available — for example: List Contacts, Create or Update Contact, Get Contact, Update Contact, Update Contact by Email, and more.

Which Omnisend events can start a workflow?

2 triggers — for example: New or updated Omnisend contacts (polled), New Omnisend orders (polled).

Can Omnisend be used as an AI agent tool?

Yes. Every Omnisend action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.

How is the Omnisend integration modelled?

Omnisend is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.