← LeaderboardThe Skill Leaderboard

Omnisend Automation

Automate ecommerce marketing workflows including contact management, bulk operations, and subscriber segmentation through Omnisend via Composio

Published by composio-community ↗composio-community/awesome-codex-skills

Try your first task

Omnisend Automation

Start a fresh conversation. Replace the highlighted placeholders.

Use Omnisend Automation to list contacts matching [email, subscription status, segment, or tag] and return the complete paginated results; use my connected Omnisend account.

Required inputs

  • [email, subscription status, segment, or tag]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: Omnisend Automationdescription: "Automate ecommerce marketing workflows including contact management, bulk operations, and subscriber segmentation through Omnisend via Composio"requires:   mcp:     - rube

Omnisend Automation

Automate ecommerce marketing operations -- create and update contacts, manage subscriber lists with cursor pagination, run bulk batch operations, and segment audiences -- all orchestrated through the Composio MCP integration.

Toolkit docs: composio.dev/toolkits/omnisend

Setup

  1. Connect your Omnisend account through the Composio MCP server at https://rube.app/mcp
  2. The agent will prompt you with an authentication link if no active connection exists
  3. Once connected, all OMNISEND_* tools become available for execution

Core Workflows

1. Create or Update a Contact

Upsert a contact by email identifier with subscription status, profile fields, and optional welcome message.

Tool: OMNISEND_CREATE_OR_UPDATE_CONTACT

ParameterTypeRequiredDescription
identifiersarrayYesAt least one identifier object with id (email), type (email), optional channels.email.status (subscribed, nonSubscribed, unsubscribed), and sendWelcomeMessage (boolean)
firstNamestringNoContact's first name
lastNamestringNoContact's last name
genderstringNom or f
birthdatestringNoFormat: YYYY-MM-DD
countrystringNoFull country name
countryCodestringNoISO 3166-1 alpha-2 code (e.g., US)
citystringNoCity name
addressstringNoStreet address
postalCodestringNoZIP/postal code

2. List Contacts with Pagination

Retrieve contacts in batches with optional filters for email, phone, status, segment, or tag.

Tool: OMNISEND_LIST_CONTACTS

ParameterTypeRequiredDescription
limitintegerNoResults per page (default: 100, max: 250)
afterstringNoCursor for next page (base64-encoded ContactID)
beforestringNoCursor for previous page
emailstringNoFilter by exact email address
phonestringNoFilter by full phone number with country code
statusstringNoFilter by: subscribed, nonSubscribed, unsubscribed
segmentIDintegerNoFilter by segment ID
tagstringNoFilter by tag (e.g., VIP)

3. Get Contact Details

Retrieve the full profile for a single contact when you already have their contact ID.

Tool: OMNISEND_GET_CONTACT

ParameterTypeRequiredDescription
contactIdstringYesUnique contact identifier (e.g., 60e7412b1234567890abcdef)

4. Update an Existing Contact

Patch specific fields on a contact by ID without overwriting the entire record.

Tool: OMNISEND_UPDATE_CONTACT

Requires the contactId and the fields to update. Retrieve the contact ID first via OMNISEND_LIST_CONTACTS or OMNISEND_GET_CONTACT.

5. Bulk Batch Operations

Process many records asynchronously in a single call -- contacts, products, orders, events, or categories.

Tool: OMNISEND_CREATE_BATCH

ParameterTypeRequiredDescription
methodstringYesPOST or PUT
endpointstringYesTarget: contacts, orders, products, events, categories
itemsarrayYesArray of payload objects for each operation
eventIDstringConditionalRequired when endpoint is events

Use batch operations to avoid rate limits when processing large data sets.

Known Pitfalls

PitfallDetails
Identifier requiredOMNISEND_CREATE_OR_UPDATE_CONTACT requires at least one identifier in the identifiers array -- only email type is supported
Cursor-based paginationOMNISEND_LIST_CONTACTS uses base64-encoded after/before cursors, not page numbers -- follow cursors to avoid incomplete data
Contact ID resolutionOMNISEND_UPDATE_CONTACT requires a contactId -- always resolve it first via list or get operations
Batch method constraintsOMNISEND_CREATE_BATCH only accepts POST or PUT methods -- no DELETE or PATCH
Event ID dependencyWhen batching events, the eventID parameter is mandatory -- omitting it causes the batch to fail

Quick Reference

Tool SlugPurpose
OMNISEND_CREATE_OR_UPDATE_CONTACTCreate or upsert a contact by email
OMNISEND_LIST_CONTACTSList contacts with filtering and cursor pagination
OMNISEND_GET_CONTACTGet full profile for a single contact by ID
OMNISEND_UPDATE_CONTACTPatch specific fields on an existing contact
OMNISEND_CREATE_BATCHBulk async operations for contacts, products, orders, events

Powered by Composio

Omnisend Automation by composio-community · The Skill Leaderboard