Omnisend is a marketing automation platform for ecommerce businesses, focusing on email and SMS marketing.
Omnisend is a marketing automation platform for ecommerce businesses, focusing on email and SMS marketing. On Nagent, Omnisend is exposed as a fully-configurable marketing automation integration that any agent can call — 43 actions, and API_KEY, OAUTH2 authentication. No code is required to wire Omnisend into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Omnisend to automate the kinds of tasks marketing automation teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Omnisend into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Omnisend, with input parameters and output schema. Drop these into any step of an agent built in Helix.
OMNISEND_ADD_CART_PRODUCTTool to add a product to a cart in Omnisend (v3 API). Use when updating cart contents or tracking abandoned carts.
Input parameters
Stock keeping unit identifier.
Current price in cents (e.g., 12111 for $121.11).
Product name or title.
Unique identifier of the cart to add the product to.
ISO 4217 currency code (3 characters).
Discount amount in cents.
Number of items. Must be a whole number greater than or equal to 1.
URL to product image.
Original price before discount in cents (e.g., 14311 for $143.11).
Unique product identifier from your catalog.
Product variant identifier for tracking specific product variations.
Product description text.
URL to product page.
Product identifier in cart. Must be unique within the cart.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_CREATE_BATCHTool to create a new batch operation for multiple items. Use when you need to process many records asynchronously in one call, e.g., bulk contacts, products, orders, or events. Use after preparing the items list to avoid rate limits.
Input parameters
Array of payload objects for each operation.
HTTP method for all operations in this batch. Must be POST or PUT.
Required when endpoint is 'events'; the ID of the event to trigger.
Target endpoint for the operations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_CREATE_CARTTool to create a new shopping cart in Omnisend. Use when tracking customer cart activity for abandoned cart campaigns.
Input parameters
Customer email address associated with this cart
Customer phone number
Unique cart identifier. Must be unique across all carts.
Total cart value in cents (e.g., 9999 for $99.99)
ISO 4217 currency code (e.g., USD, EUR, GBP)
Array of products in the cart
Existing Omnisend contact identifier to associate with this cart
Cart creation timestamp in ISO 8601 format. If not provided, current time is used.
Cart last update timestamp in ISO 8601 format
URL to recover the cart, used in abandoned cart emails
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_CREATE_CATEGORYTool to create a new category in Omnisend. Use when organizing products into categories.
Input parameters
Display name for the category.
Unique identifier for the category. Must be unique within your Omnisend account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_CREATE_ORDERTool to create a new order in Omnisend v3 API. Use when recording a customer purchase or order transaction.
Input parameters
Order tags
Customer email address (email or phone or contactID required)
Customer phone number (email or phone or contactID required)
Cart identifier
Order source
Tax amount in cents
Unique order identifier from your store
Order currency code (e.g., USD, EUR)
Customer last name
Total order amount in cents (must be integer, not float)
URL to view the order
Array of ordered products
Omnisend contact ID (email or phone or contactID required)
Order creation timestamp in ISO 8601 format (cannot be future date, required by API)
Customer first name
Order last update timestamp in ISO 8601 format
Tracking URL
Note about the customer or order
Total discount amount in cents
Order number for display
Shipping cost in cents
Subtotal amount in cents
Courier service name
Custom fields as key-value pairs
Discount code applied
Type of discount (e.g., fixedAmount, percentage)
Shipping tracking code
Discount value in cents
Payment method description
Payment status enum values.
Address information for billing or shipping.
Shipping method description
Address information for billing or shipping.
Fulfillment status enum values.
Whether tax is included in subtotal
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_CREATE_OR_UPDATE_CONTACTTool to create or update a contact in Omnisend. Use after collecting subscriber details.
Input parameters
City name
Contact's gender ('m' or 'f')
Street address
Full country name
Contact's last name
Birthdate in YYYY-MM-DD format
Contact's first name
Postal or ZIP code
ISO 3166-1 alpha-2 country code
One or more ways to identify the contact; at least one required
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_CREATE_PRODUCTTool to create a new product in the Omnisend product catalog. Use when adding products for email campaigns or syncing inventory.
Input parameters
Unique product identifier from your store. Must be unique across all products.
URL to the product page on your website.
Tags to categorize the product for filtering and organization (max 100 items).
Product type to categorize products (e.g., 'Electronics', 'Clothing').
Product title displayed to customers.
Additional product image URLs beyond the default image (max 300 items).
Overall product availability status. Keep in sync with your shop to avoid sending out-of-stock products.
Manufacturer or brand of the product.
ISO 4217 currency code (e.g., USD, EUR, GBP).
Product variants with their own prices and SKUs. At least one variant is required (min 1, max 500 items).
Product creation timestamp in ISO 8601 format (e.g., 2021-01-01T00:00:00Z).
Last update timestamp in ISO 8601 format.
List of category IDs this product belongs to (max 100 items).
Short description of the product. Can be used in the email body.
Primary image URL for the product. Recommended if more than one image is needed.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_CREATE_PRODUCT_CATEGORYTool to create a new product category in the Omnisend catalog. Use when organizing products into categories.
Input parameters
Title/name of the product category. Maximum 100 characters.
Unique identifier for the product category. Must be between 1 and 100 characters.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_DELETE_CARTTool to delete a cart from Omnisend by its ID (v3 API). Use when you need to remove an abandoned or expired cart from the system.
Input parameters
Unique identifier of the cart to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_DELETE_CATEGORYTool to remove a category from Omnisend by its ID. Use when you need to delete a category and ensure it is no longer available in your catalog.
Input parameters
Unique identifier of the category to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_DELETE_ORDERTool to delete an order from Omnisend by its ID. Use when you need to remove an order from the system.
Input parameters
Unique identifier of the order to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_DELETE_PRODUCTTool to remove a product from Omnisend by its ID. Use when you need to delete a product and ensure it is no longer available in your catalog.
Input parameters
Unique identifier of the product to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_DELETE_PRODUCT_CATEGORYTool to remove a product category from Omnisend by its ID. Use when you need to delete a product category from your catalog.
Input parameters
Unique identifier of the product category to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_GET_BATCHESTool to retrieve a list of batch operations. Use after initiating a batch job to monitor its progress and results.
Input parameters
Target endpoint for the batch operations to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_GET_BATCH_INFORMATIONTool to retrieve information about a specific batch by ID. Use after submitting a batch when you need a detailed status and counts.
Input parameters
The unique identifier of the batch to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_GET_BATCH_ITEMTool to retrieve a specific item within a batch by batchID and itemID. Use when you need to inspect the result of a single batch operation.
Input parameters
The unique identifier of the specific item to retrieve within the batch
The unique identifier of the batch containing the item
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_GET_BATCH_ITEMSTool to retrieve processed items of a specific batch by ID. Use when you need to inspect individual results of a batch operation after fetching batch details.
Input parameters
The unique identifier of the batch whose items you want to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_GET_BRANDTool to retrieve information about the current authenticated brand. Use when you need brand details like currency, platform, or website.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_GET_CARTTool to retrieve a specific cart by ID from Omnisend v3 API. Use when you need detailed cart information including products and customer contact details.
Input parameters
Unique identifier of the cart to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_GET_CATEGORYTool to retrieve details of a specific category by ID. Use when you need to fetch information about a category.
Input parameters
Unique identifier of the category to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_GET_CONTACTTool to retrieve details of a single contact by ID. Use when you already have a contactId and need the full profile.
Input parameters
Unique identifier of the contact to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_GET_ORDERTool to retrieve details of a specific order by ID. Use when you need order information including products, addresses, and payment details.
Input parameters
Unique identifier of the order to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_GET_PRODUCTTool to retrieve details of a specific product by ID from Omnisend. Use when you need full product information including variants, pricing, and stock status.
Input parameters
Unique identifier of the product to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_GET_PRODUCT_CATEGORYTool to retrieve a specific product category by ID. Use when you need details about a particular product category.
Input parameters
Unique identifier of the product category to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_LIST_CAMPAIGNSTool to retrieve a paginated list of campaigns with optional filtering by status and type. Use when you need to view or analyze campaign performance across multiple campaigns.
Input parameters
Filter campaigns by type (e.g., regular, automation, split).
Number of results to fetch. Default is 5000, maximum is 5000.
Number of results to skip. Use for pagination. Default is 0.
Campaign status values.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_LIST_CARTSTool to retrieve a paginated list of carts with optional filtering. Use when you need to fetch carts by date range, contact, or segment.
Input parameters
Sort order for results.
Filter carts by contact email address.
Number of results to fetch. Default is 100, max 250.
Filter carts by contact phone number including country code.
Cart creation date to. Format: YYYY-MM-DD.
Number of results to skip. Default is 0.
Cart creation date from. Format: YYYY-MM-DD.
Filter carts by contact ID.
Filter carts by segment ID.
Cart update date to. Format: YYYY-MM-DD.
Cart update date from. Format: YYYY-MM-DD.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_LIST_CATEGORIESTool to retrieve a paginated list of product categories. Use when you need category IDs for product management or catalog organization.
Input parameters
Field to sort results by. Format: 'fieldName' for ascending, '-fieldName' for descending.
Number of results to fetch. Defaults to 100, maximum 250.
Number of results to skip. Defaults to 0. Use for pagination.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_LIST_CONTACTSTool to retrieve a paginated list of contacts with optional filtering. Use when you need to fetch contacts in batches and handle cursor pagination.
Input parameters
Filter contacts by tag.
Cursor for pagination: contacts after this base64-encoded ContactID.
Filter contacts by exact email address.
Number of results per page. Defaults to 100, maximum 250.
Filter contacts by full phone number including country code.
Cursor for pagination: contacts before this base64-encoded ContactID.
Filter contacts by email channel status.
Filter contacts by segment ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_LIST_EVENTSTool to retrieve all custom events created in Omnisend app. Use when you need to view available event types for automation workflows or event tracking.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_LIST_PRODUCT_CATEGORIESTool to retrieve a paginated list of product categories from the Omnisend catalog. Use when fetching category data for product organization.
Input parameters
Field to sort by. Allowed values: 'date', 'createdAt', or 'updatedAt'.
Maximum number of categories to return. Defaults to 100.
Zero-based index of the first category to return. Use to page through results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_LIST_PRODUCTSTool to retrieve a paginated list of products. Use when syncing product catalog before campaign creation.
Input parameters
Field to sort by. Allowed values: 'date', 'createdAt', or 'updatedAt'.
Maximum number of products to return. Defaults to 100.
Zero-based index of the first product to return. Use to page through results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_REMOVE_CART_PRODUCTTool to remove a product from a cart in Omnisend. Use when you need to delete a specific product from a cart.
Input parameters
Unique identifier of the cart.
Unique identifier of the product in the cart to remove.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_REPLACE_CARTTool to replace an existing cart in Omnisend using the v3 API. Use when you need to completely replace all cart data including products, pricing, and recovery URL.
Input parameters
Unique identifier of the cart to replace
Total cart value in cents (e.g., 78777 = $787.77)
ISO 4217 currency code for the cart (e.g., USD, EUR, GBP)
List of products in the cart
ISO 8601 timestamp when the cart was created
ISO 8601 timestamp when the cart was last updated
URL to restore the cart, used for abandoned cart recovery
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_REPLACE_CART_PRODUCTTool to replace a product in a cart using Omnisend v3 API. Use when you need to update all details of a specific product in a cart.
Input parameters
Stock keeping unit identifier.
Product price in cents, without commas. For example, for 1.25 USD use 125.
Product title.
Unique identifier of the cart containing the product to replace.
ISO currency code (3 characters).
Discount sum in cents.
Link to product image (must be a valid URI).
Old price in cents, without commas. For example, for 1.43 USD use 143.
Product quantity (only whole numbers, minimum 1).
Product identifier.
Product modification identifier (variant ID).
Link to product page (must be a valid URI).
Product description.
Unique identifier of the product in the cart to replace.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_REPLACE_CATEGORYTool to replace a category's title by ID. Use when you need to update an entire category resource.
Input parameters
New title for the category
Unique identifier of the category to replace
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_REPLACE_ORDERTool to completely replace an existing order in Omnisend. Use when you need to update all order details at once, replacing the entire order record.
Input parameters
Tags associated with the order
Identifier of the cart that led to this order
Source of the order (e.g., 'web', 'mobile')
Total tax amount in smallest currency unit
Unique identifier of the order to replace
ISO 4217 currency code (e.g., 'USD', 'EUR')
Total order amount in the smallest currency unit (e.g., cents)
URL to view the order
List of products in the order
ISO 8601 timestamp when the order was created
ISO 8601 timestamp when the order was last updated
URL for courier tracking
Notes about the customer
Total discount amount in smallest currency unit
Human-readable order number
Shipping cost in smallest currency unit
Subtotal before taxes and shipping in smallest currency unit
Reason for order cancellation if applicable
ISO 8601 timestamp when the order was canceled
Name of the shipping courier
Discount or coupon code applied
Type of discount (e.g., 'percentage', 'fixed')
Shipment tracking code
Discount value (percentage or fixed amount)
Payment method used (e.g., 'credit_card', 'paypal')
Payment status. Available values: awaitingPayment, partiallyPaid, paid, partiallyRefunded, refunded, voided
Billing address information for the order.
Shipping method used
Shipping address information for the order.
Fulfillment status (e.g., 'fulfilled', 'unfulfilled', 'partially_fulfilled')
Whether subtotal includes tax
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_REPLACE_PRODUCTTool to replace an existing product in the Omnisend catalog. Use when you need to completely replace all product data with new information.
Input parameters
Product ID - must match the product_id path parameter
URL pointing to the product page on your website
Tags for product categorization (max 100 items)
Product type for categorization purposes
Product title
Additional product image URLs (max 300 items)
Product stock status. Keep in sync with your shop to avoid sending out-of-stock products
Manufacturer or brand of the product
ISO 4217 currency code (e.g., USD, EUR, GBP)
Product variants (different versions like sizes/colors). At least one variant required
Creation timestamp in ISO 8601 format
Last update timestamp in ISO 8601 format
Unique identifier of the product to replace. Must match the product ID in the request body
List of category IDs the product belongs to (max 100 items)
Short description of the product for email body usage
Primary image URL. Recommended if you need more than one image - additional images go in the images array
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_SEND_EVENTTool to send a customer event to Omnisend. Events can trigger automations and track customer behavior. Use when you need to record customer interactions such as product views, cart actions, or custom events.
Input parameters
Source of the event. Use 'api' for general API integrations. Platform or app integrations should have dedicated origin values.
Contact information. Contact will be created or updated based on the data provided. At least one identifier (email, phone, or id) is required.
UUID of the event (v4, v5, v6, v7). Used for event deduplication along with eventTime. If not provided, it will be generated automatically.
Name of the event (e.g., 'order placed', 'product viewed', 'test_event'). Check event documentation for standard event names.
Event timestamp in RFC3339 format (e.g., '2021-07-01T00:00:00Z'). If not provided, current time will be used.
Event-specific properties such as order details, product info, etc. Check events guide for recommended properties for each event type.
Event version string. Check event documentation for required version for each event. Leave empty for custom events.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_UPDATE_CARTTool to partially update a cart in Omnisend (v3 API). Use when you need to modify cart details such as currency, total amount, recovery URL, or products.
Input parameters
Unique identifier of the cart to update
Total cart value in cents, without commas. For example, for $1.25 USD use 125
ISO currency code (3 characters)
List of products in the cart
URL to recover the cart
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_UPDATE_CART_PRODUCTTool to update a product in a cart (v3 API). Use when you need to modify product details such as quantity, price, or other attributes for an existing cart item.
Input parameters
Stock keeping unit (SKU).
Current price in cents (e.g., 125 for $1.25).
Product title.
Unique identifier of the cart.
ISO currency code (3 characters). Must match the cart's currency.
Discount sum in cents.
Product quantity (must be a whole number, minimum 1).
Link to product image.
Original price in cents (e.g., 125 for $1.25).
Product identifier.
Product variant identifier.
Product description.
Link to product page.
Unique identifier of the product in the cart to update.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_UPDATE_CONTACTTool to update fields of an existing contact by ID. Use after retrieving contact ID. PATCH https://api.omnisend.com/v3/contacts/{contactId} Example: UpdateContact(contactId="..., body={firstName: 'John'})
Input parameters
Fields to update on the contact
Unique identifier of the contact to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_UPDATE_ORDER_STATUSTool to partially update an order status in Omnisend (v3 API). Use when you need to update shipping details, payment status, or fulfillment status of an existing order.
Input parameters
Identifier of the cart associated with this order.
Unique identifier of the order to update.
URL to track the shipment (must be a valid URI).
Reason for order cancellation.
ISO 8601 date-time when the order was canceled (e.g., '2017-05-30T14:11:12Z').
Name of the courier/shipping company.
Tracking code for the shipment.
Payment status of the order. You need to map your status with Omnisend's statuses (e.g., 'pending', 'paid').
Fulfillment status of the order. You need to map your status with Omnisend's statuses (e.g., 'unfulfilled', 'fulfilled').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OMNISEND_UPDATE_PRODUCT_CATEGORYTool to update an existing product category title in Omnisend. Use when you need to modify a category's name.
Input parameters
Updated title for the product category
Product category ID to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 87 agents privately built on Nagent that already use Omnisend.
Build on Nagent
Connect Omnisend to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Omnisend, and click "Connect Now." You'll authenticate with API_KEY, OAUTH2 — Nagent handles credential storage and refresh automatically. Once connected, Omnisend is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Omnisend is connected, you configure its 43 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Omnisend steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Omnisend event fires, the agent kicks off automatically.
Every Omnisend action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Omnisend ships with 43 pre-built marketing automation actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Omnisend together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Omnisend-based workflows tailored to your business.