Integration
Connect Commerce Layer to Spike.sh
When something happens in Commerce Layer, your agent does the next thing in Spike.sh. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Commerce Layer and Spike.sh to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Commerce Layer can start in Spike.sh
When New Attachment in Commerce Layer
then Add alert rule 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 · 43 actions
- New Attachment
Triggers when a new Attachment is created.
- New Customer
Triggers when a new Customer is created.
- New Customer Address Event
Triggers when a customer address is created.
- New Customer Password Reset Event
Triggers when a customer password reset is requested.
- New Customer Subscription Event
Triggers when a given customer_subscription event (one of create or destroy) is fired.
- New Price
Triggers when a new Price is created.
- New Price Import
Fires when a new price import is created in Commerce Layer.
- New Price List
Triggers when a new Price List is created.
- New Shipping Category
Triggers when a Shipping Category is created.
- New SKU
Triggers when a new SKU is created.
- New SKU Import
Triggers when a new SKU import is created.
- New Stock Item Import
Triggers when a new Stock Item import is created.
- New Stock Transfer Event
Triggers when a given stock transfer event (one of create, upocoming, picking, in_transit, complete, cancel is fired).
- Balance Change Gift Card
Change balance of a gift card.
- Create Attachment
Creates a new Attachment.
- Create Customer
Creates a new Customer.
- Create Gift Card
Creates a new Gift Card.
- Create Price Import
Creates a new Price Import.
- Create Price List
Creates a new Price List.
- Create SKU
Creates a new SKU.
- Find Attachment
Finds a Attachment by name.
- Find Customer
Finds a customer by id or reference.
- Find Gift Card
Finds a gift card by id or reference.
- Find Price
Finds a price by price list.
- Find Price Import
Finds a Price Import by status.
- Find Price List
Finds a Price List by name.
- Find Shipping Category
Finds an Shipping Category by name.
- Find SKU
Finds an SKU by code.
- Find SKU Import
Finds an SKU Import by status.
- Find Stock Item Import
Finds a Stock Item Import by status.
- Update Customer Reference
Update customer data setting external identifier.
- Acknowledge incident
Acknowledge one or more Spike.sh incidents by counter id or incident id.
- Add alert rule
Create a new alert routing/automation rule with conditions and actions.
- 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.
- Add integration
Create a new integration for a team (source system that sends alerts into Spike).
- Add on-call
Create a new on-call schedule for a team.
- Add service
Create a new service in a team, with name and description.
- 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.
- Delete alert rule
Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.
- Delete escalation
Archives (soft-deletes) a Spike escalation policy by its ID.
- Escalate incident
Escalates one or more Spike incidents to the next step of their escalation policy.
- Get escalation
Get escalation policy details by id.
- Get incident
Fetch a single incident by counter id.
- 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.
- Get service
Get a Spike service's details, along with its incidents and open-incident count.
- List alert rules
Lists all alert rules (enabled and disabled) configured for a Spike team.
- List escalations
Lists the escalation policies that belong to a Spike team.
- List incidents
Lists the incidents for a Spike.sh team.
- List on-calls
Lists the on-call schedules for a team.
- List services
Lists the services in a Spike team.
- List teams
Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.
- Resolve incident
Resolve one or more incidents by counter id array.
- Update alert rule
Replace an existing Spike alert rule's name, conditions and actions.
- 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.
- 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.
- Update service
Updates the name and/or description of an existing Spike.sh service.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Commerce Layer
Commerce Layer to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Commerce Layer to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Commerce Layer to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Commerce Layer to Google SheetsGoogle Sheets
Commerce Layer to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Commerce Layer to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into 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.
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.