--- title: "Connect Commerce Layer to Spike.sh - APIANT.ai" description: "When \"New Attachment\" fires in Commerce Layer, your agent runs \"Add alert rule\" in Spike.sh." canonical: "https://apiant.ai/connect/commerce-layer-to-spike-sh" --- # Connect Commerce Layer to Spike.sh When **New Attachment** fires in [Commerce Layer](https://apiant.ai/connections/commerce-layer), 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. Commerce Layer **13** triggers Commerce Layer **28** 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 Commerce Layer 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 Commerce Layer can start in Spike.sh - When **New Attachment** in Commerce Layer then **Add alert rule** in Spike.sh - When **New Customer** in Commerce Layer 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 Commerce Layer and Spike.sh ## Triggers and actions 13 triggers · 53 actions - Trigger **New Attachment** Triggers when a new Attachment is created. - Trigger **New Customer** Triggers when a new Customer is created. - Trigger **New Customer Address Event** Triggers when a customer address is created. - Trigger **New Customer Password Reset Event** Triggers when a customer password reset is requested. - Trigger **New Customer Subscription Event** Triggers when a given customer_subscription event (one of create or destroy) is fired. - Trigger **New Price** Triggers when a new Price is created. - Trigger **New Price Import** Fires when a new price import is created in Commerce Layer. - Trigger **New Price List** Triggers when a new Price List is created. - Trigger **New Shipping Category** Triggers when a Shipping Category is created. - Trigger **New SKU** Triggers when a new SKU is created. - Trigger **New SKU Import** Triggers when a new SKU import is created. - Trigger **New Stock Item Import** Triggers when a new Stock Item import is created. - Trigger **New Stock Transfer Event** Triggers when a given stock transfer event (one of create, upocoming, picking, in_transit, complete, cancel is fired). - Action **Add Customer Address** Adds an existing address to a customer's address book. - Action **Add Customer Password Reset** Requests a password reset for a customer, returning the reset token to send them. - Action **Add Customer Subscription** Subscribes a customer email to a list, identified by a reference such as a newsletter id. - Action **Add Stock Transfer** Moves a quantity of a SKU from one stock location to another. - Action **Balance Change Gift Card** Change balance of a gift card. - Action **Create Address** Creates a postal address that can be attached to customers, orders and stock locations. - Action **Create Attachment** Creates a new Attachment. - Action **Create Customer** Creates a new Customer. - Action **Create Gift Card** Creates a new Gift Card. - Action **Create Price Import** Creates a new Price Import. - Action **Create Price List** Creates a new Price List. - Action **Create SKU** Creates a new SKU. - Action **Find Attachment** Finds a Attachment by name. - Action **Find Customer** Finds a customer by id or reference. - Action **Find Gift Card** Finds a gift card by id or reference. - Action **Find Price** Finds a price by price list. - Action **Find Price Import** Finds a Price Import by status. - Action **Find Price List** Finds a Price List by name. - Action **Find Shipping Category** Finds an Shipping Category by name. - Action **Find SKU** Finds an SKU by code. - Action **Find SKU Import** Finds an SKU Import by status. - Action **Find Stock Item Import** Finds a Stock Item Import by status. - Action **Get Address** Retrieves one address by id. - Action **Get Customer Address** Retrieves one customer address link by id. - Action **Get Customer Password Reset** Retrieves a customer password reset by id, returning customer_email, reset_password_token and reset_password_at. - Action **Get Customer Subscription** Retrieves one customer subscription by id. - Action **Get Stock Transfer** Retrieves one stock transfer by id. - Action **Update Customer Reference** Update customer data setting external identifier. - 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 - [ **Commerce Layer** Commerce Layer is a lightning fast, super flexible and ultra secure REST API that lets you build...](https://apiant.ai/connections/commerce-layer) - [ **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 Commerce Layer - [ **Commerce Layer to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/commerce-layer-to-hubspot) - [ **Commerce Layer to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/commerce-layer-to-salesforce) - [ **Commerce Layer to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/commerce-layer-to-slack) - [ **Commerce Layer to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/commerce-layer-to-google-sheets) - [ **Commerce Layer to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/commerce-layer-to-gmail) - [ **Commerce Layer to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/commerce-layer-to-google-calendar) ## 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 ## Commerce Layer and Spike.sh, answered ### ### What can start an automation from Commerce Layer? Any of Commerce Layer's 13 triggers in the catalog, including New Attachment, New Customer, New Customer Address Event and New Customer Password Reset Event. 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 Commerce Layer? 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 Commerce Layer? Spike.sh has no triggers in the catalog today, so automations start in Commerce Layer. 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 Commerce Layer 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 Commerce Layer 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.