Omnisend
Omnisend contacts, tagging, and customer events for ecommerce email/SMS marketing automation.
About
Omnisend ships in the w6w first-party pack. It declares 7 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.omnisend- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Marketing · Email
Overview
Omnisend manages the ecommerce marketing lifecycle from a workflow — creating and updating contacts, tagging them individually or in bulk by ID, email, phone, or segment, and sending the customer events (recommended events like “placed order”, or free-form custom events) that trigger Omnisend’s own automations, segments, and reporting.
A fit for syncing storefront data (contacts, orders) into Omnisend as it happens, or triggering an Omnisend automation from an external condition detected elsewhere in a workflow.
Build with Omnisend
Three routes to the same 7 actions. The Workflow tab is generated from Omnisend's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Batch Add Tags
add-contact-tags Add tags to contacts selected by IDs, emails, phone numbers, or a segment.
Create or Update Contact
create-or-update-contact Create a contact, or update it if a contact with the same email identifier already exists.
Batch Remove Tags
remove-contact-tags Remove tags from contacts selected by IDs, emails, phone numbers, or a segment.
Send Customer Event
send-event Send a recommended (e.g. "placed order") or custom event to trigger Omnisend automations, segments, and reporting.
Update Contact by Email
update-contact-by-email Update the contact matching the given email address. 404 if none exists.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Omnisend's real ids.
{
"manifestVersion": "2",
"name": "omnisend-example",
"steps": [
{
"id": "add-contact-tags",
"uses": {
"app": "io.w6w.omnisend",
"action": "add-contact-tags",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"tags": "<tags>"
}
}
]
}Here are some of the things you can do
-
Batch Add Tags
performadd-contact-tags -
Create or Update Contact
performcreate-or-update-contact -
Get Contact
readget-contact -
List Contacts
readlist-contacts -
Send Customer Event
performsend-event
+2 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Omnisend, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Omnisend. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "add-contact-tags",
payload: {
tags: "<value>",
// contactIDs: "<value>",
// emails: "<value>",
// phones: "<value>",
// segmentID: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action add-contact-tags --payload '{"tags":"<value>"}'Give an AI agent Omnisend — without giving it Omnisend's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.omnisend#add-contact-tags",
"input": {
"tags": "<tags>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Omnisend connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Omnisend's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Omnisend itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Omnisend declares its own checks, so its health is a property of the app rather than something the host guesses at.
Omnisend platform status
Component status from status.omnisend.com. Covers Email, SMS, Push Notifications, the store-platform connectors (Shopify, BigCommerce, WooCommerce, Wix), and the API, Campaigns, Automation, App, Segments, Signup Forms, Reporting, Integrations and Access components.