Omnisend Automation
Automate ecommerce marketing workflows including contact management, bulk operations, and subscriber segmentation through Omnisend via Composio
Author
Category
Office AutomationInstall
Hot:44
Download and extract to your skills directory
Copy command and send to AI Agent for auto-install:
Download and install this skill https://openskills.cc/api/download?slug=composiohq-composio-skills-omnisend-automation&locale=en&source=copy
Omnisend Automation - E-commerce Marketing Automation Skills
Skill Overview
By integrating with Composio MCP, automate Omnisend e-commerce marketing workflows, including core capabilities such as creating and updating contacts, bulk subscriber operations, and customer segmentation.
Use Cases
Core Features
OMNISEND_CREATE_OR_UPDATE_CONTACT tool to create or update contacts using email as the unique identifier. Supports setting subscription status (subscribed / unsubscribed / unsubscribed) and an optional welcome message to send.OMNISEND_LIST_CONTACTS tool for cursor-based pagination queries. Supports multi-dimensional filtering (email, phone, status, segment ID, tags) and provides bidirectional paging using both before and after cursors.OMNISEND_CREATE_BATCH tool to perform bulk POST or PUT operations for contacts, orders, products, events, and categories. When processing large datasets, helps avoid triggering rate limits.Frequently Asked Questions
How do I connect my Omnisend account via Composio MCP?
Connect to the Composio MCP server at
https://rube.app/mcp, and the system will prompt you to authenticate. After completing the connection, all OMNISEND_* tools will be available for AI agents to call and execute. If the connection is interrupted, revisit the authentication link to restore it.What data types and operation methods are supported for bulk operations?
OMNISEND_CREATE_BATCH supports both POST and PUT methods, and can handle contact, product, order, event, and category data. Bulk operations are executed asynchronously, making them especially suitable for large-scale data import scenarios. Note: DELETE or PATCH is not supported. When handling events, you must provide the eventID parameter.What is the difference between cursor-based pagination and traditional page-number pagination?
The Omnisend API uses cursor-based pagination rather than traditional page numbers. The
after and before parameters accept base64-encoded contact IDs as cursors. This approach is more stable when the dataset changes, helping avoid duplicated or missing records. When using it, save the returned cursor values for the next page query rather than incrementing page numbers.