--- title: "Connect Pelcro to Spike.sh - APIANT.ai" description: "When \"Customer Created\" fires in Pelcro, your agent runs \"Add alert rule\" in Spike.sh." canonical: "https://apiant.ai/connect/pelcro-to-spike-sh" --- # Connect Pelcro to Spike.sh When **Customer Created** fires in [Pelcro](https://apiant.ai/connections/pelcro), 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. Pelcro **5** triggers Pelcro **12** 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 Pelcro 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 Pelcro can start in Spike.sh - When **Customer Created** in Pelcro then **Add alert rule** in Spike.sh - When **Customer Updated** in Pelcro 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 Pelcro and Spike.sh ## Triggers and actions 5 triggers · 37 actions - Trigger **Customer Created** Triggers when a user registers via the Pelcro Platform. This means that a customer record exists in Pelcro and has a unique email address, password, and customer ID associated to it. - Trigger **Customer Updated** Triggers when a customer is updated in Pelcro. - Trigger **Newsletter Created** Triggers when a new newsletter subscription is created in Pelcro. - Trigger **Newsletter Updated** Triggers when an existing Pelcro newsletter subscription is updated, such as a change to the subscriber's mailing lists or consent. - Trigger **Subscription Created** Triggers when a new subscription is created in Pelcro. - Action **Add address** Creates a new shipping, billing or primary address for a Pelcro customer. - Action **Add coupon** Creates a new discount coupon on your Pelcro site, with either a fixed amount or a percentage off. - Action **Create Customer** Creates a new customer on your Pelcro site. - Action **Create Newsletter** Creates a newsletter subscriber in Pelcro with their email, signup source and optional consent details. - Action **Create Plan** Creates a new pricing plan under a Pelcro product, setting its price, currency, billing interval and subscription behavior. - Action **Create Product** Creates a product in your Pelcro site. Plans and their prices are added under a product. - Action **Create Subscription** Creates a subscription for a Pelcro customer on a plan, optionally with a coupon, trial period or gift details. - Action **Get coupon** Returns a single coupon by id, including its code, discount, duration, redemption count and expiration. - Action **Get newsletter** Returns a single newsletter subscriber by id, including their email, name, lists and consent details. - Action **List newsletters** Returns newsletter subscribers on your Pelcro site, optionally filtered by exact email address. - Action **Update customer** Updates an existing Pelcro customer's profile, such as contact details, marketing preferences, password and metadata. Fields left blank are left unchanged. - Action **Update Newsletter** Updates an existing newsletter subscriber's email, signup source, name, lists and consent 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 - [ **Pelcro** Pelcro is a subscription and membership management platform](https://apiant.ai/connections/pelcro) - [ **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 Pelcro - [ **Pelcro to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/pelcro-to-salesforce) - [ **Pelcro to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/pelcro-to-slack) - [ **Pelcro to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/pelcro-to-stripe) - [ **Pelcro to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/pelcro-to-shopify) - [ **Pelcro to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/pelcro-to-quickbooks-online) - [ **Pelcro to Pipedrive** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pelcro-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 ## Pelcro and Spike.sh, answered ### ### What can start an automation from Pelcro? Any of Pelcro's 5 triggers in the catalog, including Customer Created, Customer Updated, Newsletter Created and Newsletter Updated. 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 Pelcro? 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 Pelcro? Spike.sh has no triggers in the catalog today, so automations start in Pelcro. 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 Pelcro 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 Pelcro 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.