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

# Connect Pipefy to Spike.sh

When **Moved Card** fires in [Pipefy](https://apiant.ai/connections/pipefy), 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.

Pipefy **6** triggers Pipefy **11** 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 Pipefy 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 Pipefy can start in Spike.sh

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

## Triggers and actions 6 triggers · 36 actions

- Trigger

**Done Card**

Triggers when a card is done.

- Trigger

**Moved Card**

Triggers when a card is moved.

- Trigger

**New Card**

Triggers when a new card is created.

- Trigger

**New Database Record**

Triggers when a new record is created.

- Trigger

**Updated Card Field**

Triggers when a card field is updated.

- Trigger

**Updated Record Field**

Triggers when a record field is updated.

- Action

**Create Card**

Creates a card in a Pipefy pipe, filling in its start form fields.

- Action

**Create Record**

Creates a new table record.

- Action

**Delete Card**

Permanently deletes a card from its pipe.

- Action

**Delete Database Record**

Delete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.

- Action

**Find Card**

Returns the cards in a pipe whose chosen field matches the specified value.

- Action

**Find Database Records**

Find a database records by title.

- Action

**Get Card**

Retrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.

- Action

**Get Database Record**

Fetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.

- Action

**Move Card**

Moves a Pipefy card to another phase of its pipe.

- Action

**Update Card Field**

Sets a new value on one field of an existing Pipefy card.

- Action

**Update Database Record**

Update a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation.

- 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

- [ **Pipefy** The easy button for processes and workflows Easily organize and run all your processes in one place, leaving...](https://apiant.ai/connections/pipefy)
- [ **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 Pipefy

- [ **Pipefy to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/pipefy-to-trello)
- [ **Pipefy to Hyrule Compendium** Hyrule Compendium is an open-source REST service exposing data on every interactive item in The Legend of...](https://apiant.ai/connect/pipefy-to-hyrule-compendium)
- [ **Pipefy to Spaceflight News** Spaceflight News API aggregates news coverage of spaceflight and the space industry from many publishers.](https://apiant.ai/connect/pipefy-to-spaceflight-news)
- [ **Pipefy to SparrowDesk** SparrowDesk is an AI-first helpdesk that unifies customer support across email & chat while automating...](https://apiant.ai/connect/pipefy-to-sparrowdesk)
- [ **Pipefy to Timing** Timing is an automatic time tracking app for macOS.](https://apiant.ai/connect/pipefy-to-timing)
- [ **Pipefy to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/pipefy-to-salesforce)

## 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

## Pipefy and Spike.sh, answered

###

### What can start an automation from Pipefy?

Any of Pipefy's 6 triggers in the catalog, including Moved Card, New Card, New Database Record and Updated Card Field. 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 Pipefy?

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

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