Integration
Connect Orderspace to Spike.sh
When New Customer fires in Orderspace, your agent runs Add alert rule in Spike.sh. Describe the whole flow 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 Orderspace 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 Orderspace can start in Spike.sh
When New Customer in Orderspace
then Add alert rule in Spike.sh
When New Dispatch in Orderspace
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 Orderspace and Spike.sh
Triggers and actions 10 triggers · 44 actions
Trigger
New CustomerTriggers when a new customer is created in Orderspace.
Trigger
New DispatchTriggers when items on an Orderspace order are dispatched.
Trigger
New InvoiceTriggers when an invoice is created in Orderspace.
Trigger
New OrderTriggers when a new order is placed in Orderspace.
Trigger
New PaymentTriggers when a payment is made or recorded on an Orderspace invoice.
Trigger
New ProductTriggers when a new product is created in Orderspace.
Trigger
Updated CustomerTriggers when a customer is updated in Orderspace, returning the customer record with the updates applied.
Trigger
Updated Inventory LevelTriggers when the stock on hand or available quantity of a product variant changes in Orderspace.
Trigger
Updated OrderTriggered when an order is changed. Watches the 200 most recently created orders.
Trigger
Updated ProductTriggers when a product is updated in Orderspace, returning the product with the updates applied.
Action
Add invoiceCreates an invoice in Orderspace for one or more of a customer's orders.
Action
Add productCreates a new product with its variants, prices and categories in Orderspace.
Action
Create CustomerCreates a new customer (a company that places orders) in Orderspace, with its buyer login, contact emails and address.
Action
Create DispatchCreates a dispatch for an order, marking the given items as shipped and reducing stock on hand. The order becomes fulfilled once all its items are dispatched.
Action
Create OrderCreates an order for an existing customer, with product, custom and shipping lines.
Action
Delete customerDeletes a customer from your Orderspace site.
Action
Delete orderDeletes an order in Orderspace.
Action
Delete productDeletes a product (and its variants) from your Orderspace catalog.
Action
Get customerReturns a single Orderspace customer by its ID, including buyers, addresses, email addresses and assigned price list, payment terms and customer group.
Action
Get dispatchReturns a single dispatch (the fulfilled items of an order) by its ID, including shipping address and dispatch lines.
Action
Get invoiceReturns a single invoice by its ID, including its lines, orders, billing address and payments.
Action
Get orderReturns a single Orderspace order by its ID, including customer details, addresses, order lines and totals.
Action
Get productReturns a single product by its ID, including its variants, prices, categories and images.
Action
List customersReturns a list of customers, most recently created first, optionally filtered by company name, buyer email, status, reference, payment terms, group or price list.
Action
List inventory levelsReturns stock levels (on hand and available quantities) for product variants, optionally filtered by product, SKU, or created/updated date.
Action
List ordersReturns orders from your Orderspace site, most recently created first, optionally filtered by date, number, status, reference, customer or standing order.
Action
Update customerUpdates an existing Orderspace customer. Fields left blank keep their current values.
Action
Update Inventory LevelSets the on-hand or available stock quantity for a product variant, identified by its SKU.
Action
Update productUpdates an existing product in Orderspace, including its details, variants, categories and images. Fields left blank stay unchanged.
Action
Acknowledge incidentAcknowledge one or more Spike.sh incidents by counter id or incident id.
Action
Add alert ruleCreate a new alert routing/automation rule with conditions and actions.
Action
Add escalationCreates 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 integrationCreate a new integration for a team (source system that sends alerts into Spike).
Action
Add on-callCreate a new on-call schedule for a team.
Action
Add serviceCreate a new service in a team, with name and description.
Action
Create IncidentCreates 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 ruleArchives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.
Action
Delete escalationArchives (soft-deletes) a Spike escalation policy by its ID.
Action
Escalate incidentEscalates one or more Spike incidents to the next step of their escalation policy.
Action
Get escalationGet escalation policy details by id.
Action
Get incidentFetch a single incident by counter id.
Action
Get integrationFetches 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 serviceGet a Spike service's details, along with its incidents and open-incident count.
Action
List alert rulesLists all alert rules (enabled and disabled) configured for a Spike team.
Action
List escalationsLists the escalation policies that belong to a Spike team.
Action
List incidentsLists the incidents for a Spike.sh team.
Action
List on-callsLists the on-call schedules for a team.
Action
List servicesLists the services in a Spike team.
Action
List teamsLists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.
Action
Resolve incidentResolve one or more incidents by counter id array.
Action
Update alert ruleReplace an existing Spike alert rule's name, conditions and actions.
Action
Update escalationReplaces 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-callUpdates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.
Action
Update serviceUpdates 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 Orderspace
Orderspace to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Orderspace to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Orderspace to StripeStripe is a payment processing platform for online businesses.
Orderspace to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Orderspace to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Orderspace to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Spike.sh
HubSpot to Spike.shHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Spike.shSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Spike.shSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Spike.shGoogle Sheets
Gmail to Spike.shGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Spike.shGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Orderspace and Spike.sh, answered
What can start an automation from Orderspace?
Any of Orderspace's 10 triggers in the catalog, including New Customer, New Dispatch, New Invoice 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 Orderspace?
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 Orderspace?
Spike.sh has no triggers in the catalog today, so automations start in Orderspace. 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 Orderspace 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.