--- title: "Connect Commerce Tools to Spike.sh - APIANT.ai" description: "When \"New customer\" fires in Commerce Tools, your agent runs \"Add alert rule\" in Spike.sh." canonical: "https://apiant.ai/connect/commerce-tools-to-spike-sh" --- # Connect Commerce Tools to Spike.sh When **New customer** fires in [Commerce Tools](https://apiant.ai/connections/commerce-tools), 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 Tools **2** triggers Commerce Tools **21** 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 Tools 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 Tools can start in Spike.sh - When **New customer** in Commerce Tools then **Add alert rule** in Spike.sh - When **New order** in Commerce Tools 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 Tools and Spike.sh ## Triggers and actions 2 triggers · 46 actions - Trigger **New customer** Triggers when a new customer is created in your commercetools project. - Trigger **New order** Triggers when a new order is created in the commercetools project. - Action **Add cart** Creates a new shopping cart in your commercetools project, optionally with line items, customer, addresses and discount codes. - Action **Add category** Creates a category in your commercetools project for organizing products. - Action **Add customer** Creates a customer in your commercetools project and returns the new customer record. - Action **Add order from cart** Creates an order from an existing cart, optionally setting its order number and initial order, payment and shipment states. - Action **Add product** Creates a product in your commercetools project with its product type, name, slug and optional variants, prices, categories and attributes. - Action **Delete customer** Deletes a customer, optionally erasing all of their related personal data. Returns the deleted customer. - Action **Delete product** Deletes a product from the catalog and returns the product as it was when deleted. - Action **Find categories** Finds categories in your commercetools project that match a filter, such as a key, slug or name. - Action **Find customers** Finds customers matching a filter condition, such as an email address or last name. - Action **Find inventory entries** Returns the inventory entries (stock quantities per SKU and supply channel) that match a filter. - Action **Find orders** Finds orders in the commercetools project that match a filter condition. - Action **Find products** Finds products in your commercetools project that match a filter condition, such as a product key or name. - Action **Get cart** Returns a cart by its id, including its line items, totals, addresses and state. - Action **Get customer** Returns a single customer by its id, including addresses and custom fields. - Action **Get order** Returns an order by its id, including line items, totals, state and custom fields. - Action **Get product** Returns a product by its id, including its current and staged data, variants and prices. - Action **Update cart** Updates a cart by applying one or more update actions, such as adding line items or setting the shipping address, and returns the updated cart. - Action **Update customer** Applies one or more update actions to an existing customer, such as changing their email, name or addresses, and returns the updated customer. - Action **Update inventory entry** Updates an inventory entry, for example adding, removing or setting its stock quantity, and returns the updated entry. - Action **Update order** Updates an order by applying one or more update actions, such as changing its order, shipment or payment state. - Action **Update product** Updates a product by applying one or more update actions, and returns the updated product. - 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 Tools** Headless commerce platform providing APIs for product catalog, cart, order, and inventory management across...](https://apiant.ai/connections/commerce-tools) - [ **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 Tools - [ **Commerce Tools to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/commerce-tools-to-hubspot) - [ **Commerce Tools to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/commerce-tools-to-salesforce) - [ **Commerce Tools to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/commerce-tools-to-slack) - [ **Commerce Tools to Google Sheets** Google Sheets](https://apiant.ai/connect/commerce-tools-to-google-sheets) - [ **Commerce Tools to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/commerce-tools-to-gmail) - [ **Commerce Tools to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/commerce-tools-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](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 Tools and Spike.sh, answered ### ### What can start an automation from Commerce Tools? Any of Commerce Tools's 2 triggers in the catalog, including New customer and New order. 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 Tools? 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 Tools? Spike.sh has no triggers in the catalog today, so automations start in Commerce Tools. 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 Tools 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 Tools 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.