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

# Connect lemlist to Spike.sh

When **New Activity** fires in [lemlist](https://apiant.ai/connections/lemlist), 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.

lemlist **1** trigger lemlist **8** 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 lemlist 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 lemlist can start in Spike.sh

- When **New Activity** in lemlist then **Add alert rule** in Spike.sh
- When **New Activity** in lemlist 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 lemlist and Spike.sh

## Triggers and actions 1 trigger · 33 actions

- Trigger

**New Activity**

Triggers when an activity has ocurred. It can be an email has been sent, replied to, bounced, or unsubscribed from or v3 new activity like a LinkedIn profile have been visited or a phone call just ended.

- Action

**Add Recipient to Unsubscribe List**

Add a recipient to the unsubscribe list.

- Action

**Mark a Lead From All Campaigns as Interested**

Mark a Lead From All Campaigns as Interested.

- Action

**Mark a Lead From One Campaign as Interested**

Mark a Lead From One Campaign as Interested.

- Action

**Remove Lead From Campaign**

Remove a Lead from a campaign.

- Action

**Remove Lead From Unsubscribe**

Remove a Lead from unsubscribe.

- Action

**Resume Lead From All or Specific Campaigns**

Resume Lead From All or Specific Campaigns.

- Action

**Search Lead**

Search a lead.

- Action

**Update Lead From Campaign**

Update Lead From Campaign.

- 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

- [ **lemlist** lemlist is an outreach email platform with personalized images and videos.](https://apiant.ai/connections/lemlist)
- [ **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 lemlist

- [ **lemlist to Refiner** Refiner is a customer survey tool for data driven SaaS teams.](https://apiant.ai/connect/lemlist-to-refiner)
- [ **lemlist to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/lemlist-to-salesforce)
- [ **lemlist to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/lemlist-to-slack)
- [ **lemlist to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/lemlist-to-google-sheets)
- [ **lemlist to Google Drive** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/lemlist-to-google-drive)
- [ **lemlist to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/lemlist-to-mailchimp)

## 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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](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

## lemlist and Spike.sh, answered

###

### What can start an automation from lemlist?

Any of lemlist's 1 trigger in the catalog, including New Activity. 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 lemlist?

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 lemlist?

Spike.sh has no triggers in the catalog today, so automations start in lemlist. 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 lemlist 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 lemlist 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.
