＋ Add to collection

Install (CLI)

npx skillmds add composiohq/omnisend-automation

Or Copy and Paste in Your Agent chat

Please install the Agent Skill "composiohq/omnisend-automation" for me from skillmd.com. A SkillMD skill is a SKILL.md file — plain markdown — that you save into my skills directory. Use whichever fetch route fits your setup: (1) if you have a terminal, run npx -y skillmds add composiohq/omnisend-automation; (2) otherwise fetch https://api.skillmd.com/api/skills/composiohq/omnisend-automation/raw (served as text/markdown) and save it as omnisend-automation/SKILL.md in your skills directory; (3) if the SkillMD MCP tools are connected, call skillmd_download with slug "composiohq/omnisend-automation" and save the returned files under omnisend-automation/. Show me the SKILL.md before saving if you'd like me to review it. If your skills directory is read-only (e.g. the Claude desktop app), save the files to a working folder instead and tell me — I'll add them through my app's skills settings.

README badge

Show this skill's registry status in your repo:

[![SkillMD](https://skillmd.com/badge/composiohq/omnisend-automation.svg)](https://skillmd.com/skills/composiohq/omnisend-automation)

Omnisend Automation

Name: Omnisend Automation
Rating: 4.2 (5 reviews)
Author: Composio HQ

composiohq/omnisend-automation · Agent Skill

by Composio HQ · single

Published Jul 5, 2026 · Last updated Jul 6, 2026

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

SKILL.md

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

Connect your Omnisend account through the Composio MCP server at https://rube.app/mcp
The agent will prompt you with an authentication link if no active connection exists
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

Parameter	Type	Required	Description
`identifiers`	array	Yes	At least one identifier object with `id` (email), `type` (`email`), optional `channels.email.status` (`subscribed`, `nonSubscribed`, `unsubscribed`), and `sendWelcomeMessage` (boolean)
`firstName`	string	No	Contact's first name
`lastName`	string	No	Contact's last name
`gender`	string	No	`m` or `f`
`birthdate`	string	No	Format: `YYYY-MM-DD`
`country`	string	No	Full country name
`countryCode`	string	No	ISO 3166-1 alpha-2 code (e.g., `US`)
`city`	string	No	City name
`address`	string	No	Street address
`postalCode`	string	No	ZIP/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

Parameter	Type	Required	Description
`limit`	integer	No	Results per page (default: 100, max: 250)
`after`	string	No	Cursor for next page (base64-encoded ContactID)
`before`	string	No	Cursor for previous page
`email`	string	No	Filter by exact email address
`phone`	string	No	Filter by full phone number with country code
`status`	string	No	Filter by: `subscribed`, `nonSubscribed`, `unsubscribed`
`segmentID`	integer	No	Filter by segment ID
`tag`	string	No	Filter 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

Parameter	Type	Required	Description
`contactId`	string	Yes	Unique 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

Parameter	Type	Required	Description
`method`	string	Yes	`POST` or `PUT`
`endpoint`	string	Yes	Target: `contacts`, `orders`, `products`, `events`, `categories`
`items`	array	Yes	Array of payload objects for each operation
`eventID`	string	Conditional	Required when endpoint is `events`

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

Known Pitfalls

Pitfall	Details
Identifier required	`OMNISEND_CREATE_OR_UPDATE_CONTACT` requires at least one identifier in the `identifiers` array -- only `email` type is supported
Cursor-based pagination	`OMNISEND_LIST_CONTACTS` uses base64-encoded `after`/`before` cursors, not page numbers -- follow cursors to avoid incomplete data
Contact ID resolution	`OMNISEND_UPDATE_CONTACT` requires a `contactId` -- always resolve it first via list or get operations
Batch method constraints	`OMNISEND_CREATE_BATCH` only accepts `POST` or `PUT` methods -- no `DELETE` or `PATCH`
Event ID dependency	When batching events, the `eventID` parameter is mandatory -- omitting it causes the batch to fail

Quick Reference

Tool Slug	Purpose
`OMNISEND_CREATE_OR_UPDATE_CONTACT`	Create or upsert a contact by email
`OMNISEND_LIST_CONTACTS`	List contacts with filtering and cursor pagination
`OMNISEND_GET_CONTACT`	Get full profile for a single contact by ID
`OMNISEND_UPDATE_CONTACT`	Patch specific fields on an existing contact
`OMNISEND_CREATE_BATCH`	Bulk async operations for contacts, products, orders, events

Powered by Composio

---
name: omnisend-automation
description: Automate ecommerce marketing workflows including contact management, bulk operations, and subscriber segmentation through Omnisend via Composio.
---

# 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](https://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`

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `identifiers` | array | Yes | At least one identifier object with `id` (email), `type` (`email`), optional `channels.email.status` (`subscribed`, `nonSubscribed`, `unsubscribed`), and `sendWelcomeMessage` (boolean) |
| `firstName` | string | No | Contact's first name |
| `lastName` | string | No | Contact's last name |
| `gender` | string | No | `m` or `f` |
| `birthdate` | string | No | Format: `YYYY-MM-DD` |
| `country` | string | No | Full country name |
| `countryCode` | string | No | ISO 3166-1 alpha-2 code (e.g., `US`) |
| `city` | string | No | City name |
| `address` | string | No | Street address |
| `postalCode` | string | No | ZIP/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`

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Results per page (default: 100, max: 250) |
| `after` | string | No | Cursor for next page (base64-encoded ContactID) |
| `before` | string | No | Cursor for previous page |
| `email` | string | No | Filter by exact email address |
| `phone` | string | No | Filter by full phone number with country code |
| `status` | string | No | Filter by: `subscribed`, `nonSubscribed`, `unsubscribed` |
| `segmentID` | integer | No | Filter by segment ID |
| `tag` | string | No | Filter 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`

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `contactId` | string | Yes | Unique 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`

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `method` | string | Yes | `POST` or `PUT` |
| `endpoint` | string | Yes | Target: `contacts`, `orders`, `products`, `events`, `categories` |
| `items` | array | Yes | Array of payload objects for each operation |
| `eventID` | string | Conditional | Required when endpoint is `events` |

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

---

## Known Pitfalls

| Pitfall | Details |
|---------|---------|
| **Identifier required** | `OMNISEND_CREATE_OR_UPDATE_CONTACT` requires at least one identifier in the `identifiers` array -- only `email` type is supported |
| **Cursor-based pagination** | `OMNISEND_LIST_CONTACTS` uses base64-encoded `after`/`before` cursors, not page numbers -- follow cursors to avoid incomplete data |
| **Contact ID resolution** | `OMNISEND_UPDATE_CONTACT` requires a `contactId` -- always resolve it first via list or get operations |
| **Batch method constraints** | `OMNISEND_CREATE_BATCH` only accepts `POST` or `PUT` methods -- no `DELETE` or `PATCH` |
| **Event ID dependency** | When batching events, the `eventID` parameter is mandatory -- omitting it causes the batch to fail |

---

## Quick Reference

| Tool Slug | Purpose |
|-----------|---------|
| `OMNISEND_CREATE_OR_UPDATE_CONTACT` | Create or upsert a contact by email |
| `OMNISEND_LIST_CONTACTS` | List contacts with filtering and cursor pagination |
| `OMNISEND_GET_CONTACT` | Get full profile for a single contact by ID |
| `OMNISEND_UPDATE_CONTACT` | Patch specific fields on an existing contact |
| `OMNISEND_CREATE_BATCH` | Bulk async operations for contacts, products, orders, events |

---

*Powered by [Composio](https://composio.dev)*

ComposioHQ/awesome-claude-skills/tree/master/composio-skills/omnisend-automation commit · 92568c1eda

▌
lemlist-automation · composiohq
Automate Lemlist multichannel outreach: manage campaigns, enroll leads, add personalization variables, export campaign data, and handle unsubscribes via the Composio MCP integration.

66.9k
repo stars
▌
esputnik-automation · composiohq
Automate Esputnik marketing operations through Composio's toolkit via Rube MCP, including contact management and campaign execution.

66.9k
repo stars
▌
instantly-automation · composiohq
Manage Instantly cold email campaigns, sending accounts, lead lists, and analytics through natural language commands via the Composio MCP integration.

66.9k
repo stars
▌
remarkety-automation · composiohq
Automate Remarkety e-commerce marketing operations through Composio's Remarkety toolkit via Rube MCP.

66.9k
repo stars
▌
customer-io-automation · composiohq
Automate customer engagement workflows including broadcast triggers, message analytics, segment management, and newsletter tracking through Customer.io via Composio.

66.9k
repo stars
▌
hunter-automation · composiohq
Automate Hunter.io email intelligence: search domains for email addresses, find specific contacts, verify deliverability, manage leads, and monitor account usage through natural language commands.

66.9k
repo stars

Frequently asked questions

How do I install the Omnisend Automation skill?

Run npx skillmds add composiohq/omnisend-automation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Omnisend Automation skill do?

Automate ecommerce marketing workflows including contact management, bulk operations, and subscriber segmentation through Omnisend via Composio. It is listed under Marketing & Growth, Email Marketing on SkillMD.

Is Omnisend Automation safe to use?

SkillMD's automated safety review verdict for this skill is CAUTION. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Omnisend Automation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Omnisend Automation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Omnisend Automation?

Composio HQ (@composiohq) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Omnisend Automation

Omnisend Automation

Setup

Core Workflows

1. Create or Update a Contact

2. List Contacts with Pagination

3. Get Contact Details

4. Update an Existing Contact

5. Bulk Batch Operations

Known Pitfalls

Quick Reference

Related

Frequently asked questions