---
title: "Connect Omnisend to Spike.sh - APIANT.ai"
description: "When \"New Contact\" fires in Omnisend, your agent runs \"Add alert rule\" in Spike.sh."
canonical: "https://apiant.ai/connect/omnisend-to-spike-sh"
---

# Connect Omnisend to Spike.sh

When **New Contact** fires in [Omnisend](https://apiant.ai/connections/omnisend), your agent runs **Add alert rule** in [Spike.sh](https://apiant.ai/connections/spike-sh). Describe the whole flow and it is built, tested on every scenario and kept running.

Omnisend **2** triggers Omnisend **36** actions Spike.sh **25** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Omnisend and Spike.sh to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Omnisend can start in Spike.sh

- When **New Contact** in Omnisend then **Add alert rule** in Spike.sh
- When **Updated Contacts** in Omnisend then **Add escalation** in Spike.sh

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Omnisend and Spike.sh

## Triggers and actions 2 triggers · 61 actions

- Trigger

**New Contact**

Triggers when a new contact is added to your Omnisend account, optionally limited to a subscription status, segment or tag.

- Trigger

**Updated Contacts**

Triggers when a contact is created or updated in Omnisend, newest changes first.

- Action

**Add email template**

Creates a new email template in Omnisend with a name, general style settings and content sections.

- Action

**Add product**

Creates a product in your Omnisend catalog, with optional variants, images, categories and tags.

- Action

**Add product category**

Creates a new product category in your Omnisend store.

- Action

**Add segment**

Creates a new contact segment in Omnisend from a name and a set of condition rules.

- Action

**Add tags to contacts**

Adds one or more tags to contacts chosen by contact ID, email, phone number or segment. Tagging happens in the background, so tags may take a moment to appear.

- Action

**Cancel Campaign**

Cancels a scheduled or paused campaign (or a started email campaign) in Omnisend and marks it as canceled.

- Action

**Copy Campaign**

Creates a new draft copy of an existing campaign, including its content, audience and settings. The copy is named "Copy of: " followed by the original name.

- Action

**Create Campaign**

Creates a new draft campaign (email or SMS; regular, A/B test or booster) in Omnisend and returns the created campaign.

- Action

**Create Subscriber**

Creates a subscriber (contact) in Omnisend, or updates the existing contact with the same email address.

- Action

**Delete Campaign**

Deletes a campaign from your Omnisend account.

- Action

**Delete Email Template**

Deletes an email template from your Omnisend account by its ID.

- Action

**Delete Image**

Deletes an image from the Omnisend image library by its ID.

- Action

**Delete product**

Deletes a product from the Omnisend product catalog by its ID.

- Action

**Delete Segment**

Permanently deletes a segment in Omnisend.

- Action

**Find Campaign**

Returns a single Omnisend campaign by its ID, including its name, status, channel, audience, content and sending settings.

- Action

**Find Campaigns**

Returns campaigns whose name contains the given text, optionally filtered by status, channel, type and created/updated dates.

- Action

**Find Email Template**

Returns a single email template, including its name, layout sections and general settings, looked up by its ID.

- Action

**Find Email Templates**

Returns email templates whose names contain the given text.

- Action

**Find Image**

Returns a single image from your Omnisend image library by its ID, including its URL, size and dimensions.

- Action

**Find Images**

Returns images in your Omnisend library whose names contain the search text.

- Action

**Find Segment**

Returns an Omnisend segment by its ID, including its name, status and condition rules.

- Action

**Find Segments**

Finds segments whose name contains the given text.

- Action

**Get contact**

Returns a single Omnisend contact by its ID, including profile details, identifiers, tags, segments and custom properties.

- Action

**Get product**

Returns a single product from your Omnisend catalog by its ID, including its variants, images, categories and stock status.

- Action

**Get Segment Statistics**

Returns statistics for a segment, including how many contacts it currently contains.

- Action

**Import Email Template**

Creates a new Omnisend email template by importing raw HTML. Returns the created template.

- Action

**List contacts**

Returns Omnisend contacts, optionally filtered by email, phone, subscription status, segment, tag or last-update time.

- Action

**Remove tags from contacts**

Removes one or more tags from contacts chosen by contact ID, email, phone number or segment. Omnisend processes the removal in the background.

- Action

**Render Email Template**

Renders an email template and returns its full HTML body for preview.

- Action

**Send Customer Event**

Sends a customer event (custom or recommended) to Omnisend for a contact, creating or updating the contact and triggering any automations based on that event.

- Action

**Update Campaign**

Updates a draft campaign's name, language, content, audience, sending settings, booster or A/B test settings. Only campaigns still in draft can be updated.

- Action

**Update contact**

Updates an existing Omnisend contact by its ID, changing only the fields you fill in, and returns the updated contact.

- Action

**Update email template**

Fully replaces an existing Omnisend email template's name, sections and general settings, and returns the updated template.

- Action

**Update product**

Replaces an existing product in your Omnisend catalog with the details you provide. Fields left blank are not kept from the previous version.

- Action

**Update segment**

Updates an existing segment's name and rules. The segment can't be updated while it is being built.

- Action

**Upload Image**

Uploads an image to your Omnisend image library from a publicly accessible URL and returns the stored image details.

- Action

**Acknowledge incident**

Acknowledge one or more Spike.sh incidents by counter id or incident id.

- Action

**Add alert rule**

Create a new alert routing/automation rule with conditions and actions.

- Action

**Add escalation**

Creates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps.

- Action

**Add integration**

Create a new integration for a team (source system that sends alerts into Spike).

- Action

**Add on-call**

Create a new on-call schedule for a team.

- Action

**Add service**

Create a new service in a team, with name and description.

- Action

**Create Incident**

Creates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to.

- Action

**Delete alert rule**

Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.

- Action

**Delete escalation**

Archives (soft-deletes) a Spike escalation policy by its ID.

- Action

**Escalate incident**

Escalates one or more Spike incidents to the next step of their escalation policy.

- Action

**Get escalation**

Get escalation policy details by id.

- Action

**Get incident**

Fetch a single incident by counter id.

- Action

**Get integration**

Fetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found.

- Action

**Get service**

Get a Spike service's details, along with its incidents and open-incident count.

- Action

**List alert rules**

Lists all alert rules (enabled and disabled) configured for a Spike team.

- Action

**List escalations**

Lists the escalation policies that belong to a Spike team.

- Action

**List incidents**

Lists the incidents for a Spike.sh team.

- Action

**List on-calls**

Lists the on-call schedules for a team.

- Action

**List services**

Lists the services in a Spike team.

- Action

**List teams**

Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.

- Action

**Resolve incident**

Resolve one or more incidents by counter id array.

- Action

**Update alert rule**

Replace an existing Spike alert rule's name, conditions and actions.

- Action

**Update escalation**

Replaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep.

- Action

**Update on-call**

Updates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.

- Action

**Update service**

Updates the name and/or description of an existing Spike.sh service.

## Each app on its own

- [ **Omnisend** Omnisend is a marketing automation platform built for growing ecommerce businesses that have graduated their...](https://apiant.ai/connections/omnisend)
- [ **Spike.sh** Spike is an incident management system with unlimited alerts and on-call schedules](https://apiant.ai/connections/spike-sh)

Reviews

## What our customers say

## More from Omnisend

- [ **Omnisend to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/omnisend-to-salesforce)
- [ **Omnisend to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/omnisend-to-slack)
- [ **Omnisend to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/omnisend-to-stripe)
- [ **Omnisend to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/omnisend-to-shopify)
- [ **Omnisend to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/omnisend-to-quickbooks-online)
- [ **Omnisend to Pipedrive** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/omnisend-to-pipedrive)

## More into Spike.sh

- [ **HubSpot to Spike.sh** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-spike-sh)
- [ **Salesforce to Spike.sh** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-spike-sh)
- [ **Slack to Spike.sh** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-spike-sh)
- [ **Google Sheets to Spike.sh** Google Sheets](https://apiant.ai/connect/google-sheets-to-spike-sh)
- [ **Gmail to Spike.sh** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-spike-sh)
- [ **Google Calendar to Spike.sh** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-spike-sh)

Questions

## Omnisend and Spike.sh, answered

###

### What can start an automation from Omnisend?

Any of Omnisend's 2 triggers in the catalog, including New Contact and Updated Contacts. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Spike.sh when something happens in Omnisend?

Any of Spike.sh's 25 actions, including Create Incident, Update alert rule, Update escalation and Update on-call. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Spike.sh to Omnisend?

Spike.sh has no triggers in the catalog today, so automations start in Omnisend. If you need the other direction, ask: your agent reads Spike.sh's API documentation and adds it.

###

### Do I have to build a connector for Omnisend or Spike.sh?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Omnisend and Spike.sh without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
