Omnisend connector for AI agents

Tools your email marketing agent reaches for on Omnisend, scoped per user.

CALL ANY TOOL

73 tools for email marketing in Omnisend: create and send campaigns, manage contacts, segments, and tags, run automations and forms, and sync products.

omnisend_analytics_report_generate

Generate analytics report

Get aggregated Omnisend campaign and automation performance (sends, opens, clicks, unsubscribes, attributed orders and revenue), grouped by the date messages were sent, the same way Omnisend's in-app reports work. Returns a reports array with one entry per query: its alias, dimensions, metrics and rows (one key per dimension and metric). Use omnisend_analytics_report_generate to match in-app campaign or workflow reports. Use omnisend_analytics_statistics_generate to group by when opens, clicks and orders actually happened, or for audience growth. Limited to 10 requests per minute and 55 per day.

Parameters

Name

Type

Required

Description

queries

array

Required

1 to 4 report queries. Each query needs a unique alias, metrics (at least one, for example [{"name": "sent"}, {"name": "openRate"}]) and dateRange. Optional dimensions break results down: timestamp (requires granularity hour, day, week or month), marketingActivityID, marketingActivityType (Campaign or Automation), messageID, messageChannel (Email, SMS or Push) or segmentID; up to 2 besides timestamp. Optional filters take name, operator (in or notIn) and values. Metrics include sent, failed, openedUnique, openRate, clickedUnique, clickRate, unsubscribedUnique, markedAsSpamUnique, attributedOrders, attributedRevenue and attributedRevenuePerSent. dateRange needs interval: custom (with from and to in RFC 3339, max 12 months) or a named range such as last7Days, last30Days, last90Days, thisMonth, lastMonth, thisYear (leave from and to out for named ranges). Example: [{"alias": "campaign-performance", "metrics": [{"name": "sent"}, {"name": "openRate"}, {"name": "attributedRevenue"}], "dimensions": [{"name": "marketingActivityID"}], "filters": [{"name": "marketingActivityType", "operator": "in", "values": ["Campaign"]}], "dateRange": {"interval": "last30Days"}}]

omnisend_automation_delete

Delete automation

omnisend_automation_disable

Disable automation

omnisend_automation_get

Get automation

omnisend_automation_test_email_send

Send automation test email

omnisend_automations_list

List automations

omnisend_batch_create

Create batch

omnisend_campaign_ab_test_stop

Stop campaign ab test

omnisend_campaign_ab_test_winner_select

Campaign ab test winner select

omnisend_campaign_cancel

Cancel campaign

omnisend_campaign_get

Get campaign

omnisend_campaign_test_email_send

Send campaign test email

omnisend_campaign_update

Update campaign

Update an Omnisend campaign that is still in draft status: name, language, email or SMS content, audience, sending settings, booster or A/B test settings. Returns the updated campaign with its id, status, content, audience and sending settings. Campaigns in any status other than draft are rejected with 409. Use omnisend_campaign_update to edit a draft. To change a scheduled campaign, run omnisend_campaign_restore_to_draft first; to change a sent campaign, use omnisend_campaign_copy and edit the copy.

Parameters

Name

Type

Required

Description

campaign_id

string

Required

Omnisend campaign ID (24-character hexadecimal). Get it from List Campaigns.

ab_test

object

Optional

A/B campaigns only: replacement A/B test settings and variants. Provided fields fully replace the stored values. Shape: {"settings": {"testSizePercent": 30, "winningMetric": "clickRate", "decisionTime": {"amount": 1, "unit": "d"}}, "variants": {"a": {"content": {"email": {"subject": "..."}}}, "b": {"content": {"email": {"subject": "..."}}}}}

booster_delay_amount

integer

Optional

Booster campaigns with a draft parent only: delay after the parent is sent, in booster_delay_unit units. Set together with booster_delay_unit.

booster_delay_unit

string

Optional

Unit for booster_delay_amount: h (hours) or d (days). One of: `h`, `d`.

booster_send_to

string

Optional

Booster campaigns only: who receives the booster, nonOpeners or nonClickers. One of: `nonOpeners`, `nonClickers`.

email_preheader

string

Optional

Email preheader text shown after the subject in the inbox (max 250 characters).

email_reply_to

string

Optional

Reply-to email address. Leave empty to have replies go to the sender address; it must be an address verified for the brand.

email_sender_email

string

Optional

Sender email address. Leave empty to use the brand's configured sender; set it only when a specific verified sender address is required.

email_sender_name

string

Optional

Sender display name shown in the inbox (max 250 characters).

email_subject

string

Optional

Email subject line (max 250 characters).

excluded_countries

array

Optional

SMS campaigns only: ISO 3166-1 alpha-2 country codes whose recipients are not sent to.

excluded_segment_ids

array

Optional

Segment IDs to leave out of the audience.

included_segment_ids

array

Optional

Segment IDs to send to. Leave empty to send to all subscribers. Must not overlap with excluded_segment_ids. Get IDs from List Segments.

language

string

Optional

Campaign language locale in xx_XX format.

name

string

Optional

New campaign name (max 250 characters).

optimize_for

string

Optional

Personalized strategy only (required there): what to optimize send times for, opens, clicks or orders. One of: `opens`, `clicks`, `orders`.

respect_quiet_hours

boolean

Optional

Personalized strategy only: avoid sending between 22:00 and 06:59 in the contact's local time. Defaults to true for personalized sends.

scheduled_at

string

Optional

Send time in RFC 3339 format. Required for the scheduled and personalized strategies; must be left empty for immediate. A scheduled time must be in the future.

sending_strategy

string

Optional

When to send: immediate (default), scheduled (at scheduled_at), or personalized (send-time optimization, regular email campaigns on plans that include it). Sending settings are replaced as a whole: send every field that applies to the chosen strategy. One of: `immediate`, `scheduled`, `personalized`.

sms_image_id

string

Optional

Image ID from the Images API. When set, US and Canadian recipients get an MMS with the image; others get the SMS without it.

sms_link_shortening

boolean

Optional

Automatically shorten links in the SMS body. Defaults to true.

sms_message

string

Optional

SMS message body. With the compliance text and unsubscribe link or keyword appended it must fit within 9 SMS segments.

sms_stop_keyword_text

string

Optional

Compliance STOP keyword text appended for US and Canadian recipients (max 250 characters).

sms_unsubscribe_link_text

string

Optional

Compliance unsubscribe link text appended for recipients outside the US and Canada (max 250 characters).

tz_optimization

boolean

Optional

Email campaigns with the immediate or scheduled strategy only: send at the same local time in each recipient's time zone.

omnisend_campaigns_list

List campaigns

List Omnisend email, SMS and push campaigns, newest first, filtered by name, status, channel, type, booster parent or created/updated dates. Returns campaigns with id, name, type, channel, status, audience, sending settings, content and timestamps, plus paging.cursors.after for the next page. With view=summary the heavy content and abTest sections are left out. Use omnisend_campaigns_list to find or browse campaigns. Use omnisend_campaign_get for one campaign's full details.

Parameters

Name

Type

Required

Description

after

string

Optional

Cursor for the next page. Pass the paging.cursors.after value from the previous response. Do not send together with before.

before

string

Optional

Cursor for the previous page. Pass the paging.cursors.before value from the previous response. Do not send together with after.

channel

array

Optional

Return campaigns on any of these channels: email, sms, push.

created_at_from

string

Optional

Return campaigns created after this time (ISO 8601).

created_at_to

string

Optional

Return campaigns created before this time (ISO 8601).

direction

string

Optional

Sort direction: asc or desc. Defaults to desc. One of: `asc`, `desc`.

include

array

Optional

With view=summary, heavy sections to keep anyway: content and/or abTest. Has no effect without view=summary.

limit

integer

Optional

Number of campaigns per page, 1 to 250. Defaults to 100.

name_contains

string

Optional

Return campaigns whose name contains this text (partial match, max 200 characters).

parent_campaign_id

string

Optional

Return only the boosters of this parent campaign ID. Implies type=booster.

sort

string

Optional

Field to sort by: createdAt, updatedAt, name. Defaults to createdAt. Keep it unchanged while paging with a cursor. One of: `createdAt`, `updatedAt`, `name`.

status

array

Optional

Return campaigns in any of these statuses: error, onHold, sent, paused, started, stopped, expired, draft, scheduled, canceled.

type

string

Optional

Return only this campaign type: regular, booster or abTest (A/B test parents). One of: `regular`, `booster`, `abTest`.

updated_at_from

string

Optional

Return campaigns updated after this time (ISO 8601).

updated_at_to

string

Optional

Return campaigns updated before this time (ISO 8601).

view

string

Optional

Set to summary to leave out the heavy content and abTest sections from every campaign. Leave empty for the full representation. One of: `summary`.

omnisend_contact_create_or_update

Update contact create or

Create an Omnisend contact, or update the existing contact that has the same email identifier. Returns the saved contact with its id, identifiers, channel statuses, tags and properties (201 when created, 200 when an existing contact was updated). Use omnisend_contact_create_or_update to add or upsert a contact by email or phone. Use omnisend_contact_update or omnisend_contact_update_by_email to change fields on a contact you already know.

Parameters

Name

Type

Required

Description

address

string

Optional

Street, house number and apartment number.

birthdate

string

Optional

Birthdate in YYYY-MM-DD format.

city

string

Optional

City.

country

string

Optional

Country name. Used to derive the ISO country code when country_code is not given.

country_code

string

Optional

ISO 3166-1 alpha-2 country code. Takes priority over country when both are given.

created_at

string

Optional

When the contact was created in your own system (RFC 3339). Stored as the externalCreated custom property.

custom_properties

object

Optional

Custom properties as a JSON object of name to value. Names use Latin letters, numbers and underscores (max 128 characters, case sensitive). Values can be strings (max 2048 characters), numbers, booleans, dates as strings, or lists of strings. Set a property to "" or null to remove it.

string

Optional

Email address to identify the contact by. Added as an email identifier. Provide email, phone, or identifiers (at least one) when creating a contact.

email_status

string

Optional

Email channel subscription status for the email identifier: subscribed, unsubscribed or nonSubscribed (status unknown). Only used together with email. One of: `subscribed`, `unsubscribed`, `nonSubscribed`.

first_name

string

Optional

Contact first name.

gender

string

Optional

Gender: m (male) or f (female). One of: `m`, `f`.

identifiers

array

Optional

Full identifiers array, for advanced cases such as consent details or status dates. When set, it is sent as-is and email, email_status, phone and phone_status are ignored. Each item needs type (email or phone) and id, and can carry channels (keyed email or sms, each with status and statusChangedAt), consent (source, ip, userAgent, createdAt), source and sendWelcomeMessage. Example: [{"type": "email", "id": "jane@example.com", "channels": {"email": {"status": "subscribed", "statusChangedAt": "2024-01-01T00:00:00Z"}}, "consent": {"source": "website-form", "ip": "192.168.1.1"}}]

last_name

string

Optional

Contact last name.

phone

string

Optional

Phone number in E.164 format with the country code prefix. Added as a phone identifier, which uses the SMS channel.

phone_status

string

Optional

SMS channel subscription status for the phone identifier: subscribed, unsubscribed or nonSubscribed (status unknown). Only used together with phone. One of: `subscribed`, `unsubscribed`, `nonSubscribed`.

postal_code

string

Optional

Postal or ZIP code.

send_welcome_message

boolean

Optional

Set to false to skip the welcome message for the email and phone identifiers built from email and phone. Defaults to true, and only matters when the welcome workflow is enabled. Ignored when identifiers is set.

state

string

Optional

State or region.

tags

array

Optional

Tags (labels) to set on the contact, up to 100. Omnisend recommends a source tag when creating contacts, for example "source: api".

omnisend_contacts_tags_add

Add contacts tags

omnisend_contacts_tags_remove

Remove contacts tags

omnisend_email_content_render

Render email content

omnisend_email_template_delete

Delete email template

omnisend_email_templates_list

List email templates

omnisend_event_metadata_query

Query event metadata

omnisend_event_metadata_update

Update event metadata

omnisend_form_disable

Disable form

omnisend_form_get

Get form

omnisend_forms_list

List forms

omnisend_image_upload_from_url

Image upload from url

omnisend_product_categories_list

List product categories

omnisend_product_category_create

Create product category

omnisend_product_category_delete

Delete product category

omnisend_product_category_get

Get product category

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Omnisend tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["omnisend"], toolNames: [
    "omnisend_segment_create",
    "omnisend_campaign_create",
    "omnisend_campaign_test_email_send"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Create a winter sale email campaign for recent buyers and send me a test" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["omnisend"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Create a winter sale email campaign for recent buyers and send me a test" }],
  tools,
});

// Execute the tool call with the user's vaulted Omnisend API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["omnisend"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Create a winter sale email campaign for recent buyers and send me a test" }],
  tools,
});

// Tool call runs with the user's vaulted Omnisend API key
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["omnisend"] }, pageSize: 100,
});

const agent = new Agent({
  name: "email_marketing_agent",
  model: "gemini-2.5-pro",
  instruction: "Omnisend tools scoped to this user",
  tools,
});

await agent.run("Create a winter sale email campaign for recent buyers and send me a test");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Omnisend tool. Click to copy, paste into your agent, done.

Campaigns

Copy the prompt

Copied

Create a draft email campaign for the winter sale.

Copy the prompt

Copied

Send a test of the winter sale email to marketing@acme.com.

Copy the prompt

Copied

List SMS campaigns scheduled for this week.

Contacts and segments

Copy the prompt

Copied

Tag these 30 contacts as vip.

Copy the prompt

Copied

Create a segment of contacts who started checkout in the last 7 days.

Copy the prompt

Copied

How many contacts are in the Lapsed buyers segment?

Automations and forms

Copy the prompt

Copied

Turn off the abandoned cart automation.

Copy the prompt

Copied

How did the spring popup form perform last month?

Copy the prompt

Copied

Which contacts signed up through the newsletter popup this week?

SEE HOW AUTH WORKS

Each user connects their own Omnisend API key once, and Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Omnisend

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Omnisend

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Omnisend

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Omnisend

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other email marketing connectors.

GTM and RevOps Teams

Outbound prospecting agent

Searches Apollo for prospects matching your ICP, scores and ranks them, drafts personalized outreach in Gmail, and logs every send to Google Sheets. Mail goes out as the rep, not from a shared inbox.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Omnisend API key looks fine in a demo. In production every campaign send and contact update looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Omnisend today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Omnisend as the user or through a shared key?

As the user. Each user connects their own Omnisend API key once, and Scalekit sends it with every call. Audit logs attribute every campaign send, contact change, and automation toggle to that user, not a shared service account.

Where is the Omnisend API key stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Omnisend?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the list and report tools without omnisend_campaign_send or omnisend_campaign_delete, which permanently deletes a campaign. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Omnisend access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Which Omnisend store does the agent work in?

The brand the user's API key belongs to. omnisend_brand_get returns that store account, and the campaign, contact, segment, form, and product tools all act inside it.