Omnisend
Omnisend is a marketing automation platform for ecommerce businesses, focusing on email and SMS marketing.
Verdict
Common use cases
- Bulk import customer lists from spreadsheets
- Sync product catalog changes to campaigns
- Audit subscriber segments before send
- Troubleshoot batch job failures in real time
- Update contact tags after support interactions
Integration
- Vendor
- Omnisend
- Category
- other
- Auth
- API_KEY
- Tools
- 10
- Composio slug
omnisend
Tools
- Create Batch
Tool 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.
- Create or Update Contact
Tool to create or update a contact in omnisend. use after collecting subscriber details.
- Delete Productdestructive
Tool 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.
- Get Batches
Tool to retrieve a list of batch operations. use after initiating a batch job to monitor its progress and results.
- Get Batch Information
Tool to retrieve information about a specific batch by id. use after submitting a batch when you need a detailed status and counts.
- Get Batch Items
Tool 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.
- Get Contact
Tool to retrieve details of a single contact by id. use when you already have a contactid and need the full profile.
- List Contacts
Tool to retrieve a paginated list of contacts with optional filtering. use when you need to fetch contacts in batches and handle cursor pagination.
- List Products
Tool to retrieve a paginated list of products. use when syncing product catalog before campaign creation.
- Update Contact
Tool 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'})
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations page. 2. Click 'Add Integration' and select Omnisend from the list. 3. Go to your Omnisend dashboard, navigate to Settings > API Keys, and generate a new API key with read and write permissions for contacts, products, and batches. 4. Paste the API key into Switchy's connection form and click 'Connect'. 5. Return to any Space in Switchy and type '@Omnisend list contacts' to test the connection — you should see a paginated list of your subscribers. 6. To invoke a tool, @mention Omnisend in a message and describe the task, like '@Omnisend create a contact for jane@example.com with tag VIP' or '@Omnisend delete product ID 12345'.
What teammates see: by default, memories from Omnisend are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Import New Subscribers
@Omnisend create a batch to import these contacts: emma@shop.com (tag: newsletter), liam@shop.com (tag: vip), olivia@shop.com (tag: newsletter). Then check the batch status.Open in a Space →
Audit VIP Segment
@Omnisend list all contacts with the tag 'VIP' and show me their email addresses and subscription status.Open in a Space →
Remove Discontinued Product
@Omnisend delete the product with ID 98765 from our catalog and confirm it's been removed.Open in a Space →
Check Batch Job Progress
@Omnisend get the status of batch ID abc123 and tell me how many items processed successfully versus failed.Open in a Space →
Update Contact After Purchase
@Omnisend create or update contact sophia@store.com with tag 'recent-buyer' and custom field 'last_purchase_date' set to today.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Omnisend list all contacts who subscribed in the last 30 days and show their email status
Retrieved 247 contacts from the past 30 days. Here's a summary: 198 contacts have 'subscribed' status, 31 are 'unsubscribed', and 18 are 'non-subscribed'. The most recent subscriber is sarah.chen@example.com (added 2 hours ago), followed by mike.torres@example.com (added 5 hours ago). All contacts include email addresses, subscription timestamps, and current status flags. This is an illustrative example—your actual contact list will reflect your Omnisend account data.
This example demonstrates the List Contacts tool with date filtering. Requires API key with read access to contacts. Omnisend uses cursor-based pagination, so large lists require multiple calls. The MCP returns raw contact objects—you'll need to specify what fields matter for your analysis.
@Omnisend create a new contact for james.wilson@example.com with first name James, last name Wilson, and tag them as 'webinar-2024'
Contact created successfully. James Wilson (james.wilson@example.com) has been added to your Omnisend account with contactID: 6a8f9c2e1b4d3a5f. Applied tag 'webinar-2024' and set status to 'subscribed' by default. The contact is now eligible for email campaigns and automations targeting that tag. This is an illustrative example—actual contact creation will generate a unique ID in your account and trigger any welcome automations you have configured.
This example shows the Create or Update Contact tool in action. Requires API key with write access. Important: creating a contact with 'subscribed' status may have compliance implications depending on your region (GDPR, CAN-SPAM). Always ensure you have proper consent before adding contacts.
@Omnisend create a batch operation to update 500 contacts with a new 'holiday-promo-2024' tag and show me the batch status
Batch operation initiated with batchID: batch_7x3k9m2p. Submitted 500 contact update requests for processing. Current status: 'processing' with 342 items completed, 158 pending. Of completed items: 338 succeeded, 4 failed (duplicate email addresses detected). Estimated completion in 2-3 minutes. This is an illustrative example—batch processing is asynchronous, so you'll need to poll Get Batch Information to see final results. Failed items will include error details for troubleshooting.
This example demonstrates the Create Batch and Get Batch Information tools for bulk operations. Batch processing is essential when updating hundreds or thousands of records—it avoids rate limits and processes asynchronously. Check batch status periodically rather than waiting synchronously. Failed items require manual review.
Use-case deep-dives
When Omnisend MCP fits transactional email workflows
A 6-person e-commerce team running a Shopify store wants to automate post-purchase emails—order confirmations, shipping updates, and win-back campaigns—without leaving their AI workspace. The Omnisend MCP is the right call here because it handles contact creation, product sync, and batch event ingestion in one integration. Your team can trigger workflows from Slack threads or standup notes, pushing customer data and order events to Omnisend in real time. The batch tools shine when you're syncing 500+ products or importing a CSV of past orders. The trade-off: if your email logic requires complex segmentation or A/B testing, you'll still configure that in Omnisend's dashboard—the MCP doesn't expose campaign design. Use this MCP when your bottleneck is data entry and event tracking, not creative strategy.
How support teams use Omnisend MCP for lifecycle messaging
A 3-person support team at a SaaS startup wants to tag resolved tickets in their helpdesk and automatically enroll customers in onboarding or feedback email sequences. The Omnisend MCP works well here because it lets you create or update contacts on the fly and attach custom properties (like ticket ID or resolution date) without switching tools. Your support agent closes a ticket in Linear, and Switchy's AI pushes that contact into an Omnisend segment for a 3-day follow-up drip. The MCP's contact lookup and batch retrieval tools let you audit who's enrolled and when. The boundary: if your team sends more than 10,000 emails per month or needs real-time SMS triggers, you'll hit Omnisend's plan limits before the MCP becomes the constraint. Use this when your support volume is under 200 tickets per week and email is your primary follow-up channel.
When Omnisend MCP speeds up launch-day product syncs
A 5-person product marketing team is launching a new SKU and needs to sync product details, update contact segments, and trigger a launch-day email—all coordinated in a shared Notion doc. The Omnisend MCP is a strong fit because it exposes product creation, contact batch updates, and event tracking in one integration. Your PM drafts the launch checklist in Notion, and Switchy's AI uses the MCP to push the new product to Omnisend, tag 2,000 VIP contacts, and queue the announcement email—no CSV exports, no manual portal clicks. The batch tools handle the contact tagging asynchronously, so you're not waiting on API rate limits. The catch: if your product catalog changes hourly (like a marketplace or dynamic inventory), the MCP's manual sync model gets tedious—you'd want a webhook-driven integration instead. Use this when launches happen weekly or monthly, not multiple times per day.
Frequently asked
What does the Omnisend MCP do in Switchy?
It connects your Omnisend email and SMS marketing account to Switchy's AI workspace. Your team can create and update contacts, manage product catalogs, run batch operations, and query subscriber data without switching to the Omnisend dashboard. Useful for syncing customer lists, updating product feeds, or pulling campaign data into your workflow.
Do I need admin access to connect Omnisend?
You need an Omnisend API key, which typically requires account admin or manager permissions to generate. The key grants full read-write access to contacts, products, orders, and batches. If your Omnisend account restricts API key creation to admins, ask them to generate one for Switchy.
Can the Omnisend MCP send campaigns or automations?
No. It handles contact management, product catalog updates, and batch operations—not campaign sends or automation triggers. If you need to launch a campaign, use Omnisend's dashboard or their separate campaign API. This MCP is for data sync and subscriber management, not message delivery.
Why use this instead of Omnisend's web interface?
The MCP lets AI agents bulk-update contacts, sync product feeds, or query subscriber lists without manual CSV uploads or clicking through the dashboard. If your team already automates workflows in Switchy, this keeps Omnisend data in the same loop. For one-off campaigns, the web interface is faster.
Does connecting Omnisend count against Switchy's MCP limit?
Yes. Each MCP connection uses one slot in your Switchy plan. If you're on a tier with five MCP slots and connect Omnisend, you have four remaining. The number of Omnisend contacts or API calls doesn't affect your Switchy limit—only the connection itself does.