Integration
Connect MarketBox to Spike.sh
When New Booking fires in MarketBox, 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 MarketBox and Spike.sh to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 MarketBox can start in Spike.sh
When New Booking in MarketBox
then Add alert rule in Spike.sh
When New Order Created in MarketBox
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 MarketBox and Spike.sh
Triggers and actions 3 triggers · 59 actions
Trigger
New BookingTriggers when a new booking is created in your MarketBox project.
Trigger
New Order CreatedTriggers when a new order is created in your MarketBox project.
Trigger
New ReviewTriggers when a new supplier review is posted in your MarketBox project.
Action
Add Booking NoteAdds a note to a booking.
Action
Add booking participantRegisters a client as a participant on a group booking such as a class. Rejected if the booking is at capacity or the client is already registered.
Action
Add order itemAdds a line item for a service offering to an existing order and returns the updated order with all its items and totals.
Action
Add serviceCreates a new service in MarketBox as a draft. Add an offering and publish it before it can be booked.
Action
Change Booking StatusChanges a booking's status, for example to cancel it.
Action
Change Order StatusChanges an order's status, for example to cancel it.
Action
Check in booking participantChecks in a client who is registered on a booking, recording that they arrived. Returns the participant's updated attendance details.
Action
Create ReviewPosts a 1 to 5 star review of a supplier.
Action
Delete BookingDeletes a booking.
Action
Delete OrderDeletes an order.
Action
Delete serviceDeletes a service. The service is marked inactive and removed from lists, while bookings and orders already placed against it still resolve.
Action
Delete SupplierDeletes a supplier.
Action
Find available time slotsFinds the suggested and open time slots when a service offering can be booked at a location (or a lat/lng point) within a look-ahead window.
Action
Get BookingReturns one booking by its ID.
Action
Get locationReturns one location (a physical venue, virtual location or travel zone) by its id, including its address, coordinates, time zone and travel-zone settings.
Action
Get OrderReturns one order by its ID.
Action
Get ServiceReturns one service by ID.
Action
Get SupplierReturns one supplier by ID.
Action
List booking notesReturns every note on a booking, newest first.
Action
List booking participantsReturns everyone registered on a booking, with their participant and check-in status.
Action
List BookingsReturns the bookings in your project, optionally filtered by date range and status.
Action
List client bookingsReturns one client's bookings, past and upcoming, ordered by date, optionally filtered by date range and status.
Action
List LocationsReturns your project's venues, virtual locations and travel-zone areas.
Action
List OrdersReturns orders in your project, filtered by status, payment method or date range.
Action
List packagesReturns every package (session bundle) sold under a service, across all of its offerings, optionally filtered by status.
Action
List ReviewsReturns supplier reviews, newest first, optionally for one supplier.
Action
List ServicesReturns the services offered in your project.
Action
List SkillsReturns the skills defined in your project.
Action
List SuppliersReturns the suppliers in your project with their services and skills.
Action
List transactionsReturns the project's payment ledger transactions, newest first, optionally filtered by order, client or status and narrowed by date range.
Action
Record Order PaymentRecords a cash, external or comp payment against an order.
Action
Update BookingReschedules a booking or changes its supplier, location or capacity.
Action
Update serviceUpdates a service's name, description, language, category, tax settings or participant settings. Status is changed separately.
Action
Update supplierUpdates a supplier's profile, contact details, location and the services and skills they offer. Fields left blank keep their current values.
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 MarketBox
MarketBox to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MarketBox to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
MarketBox to StripeStripe is a payment processing platform for online businesses.
MarketBox to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
MarketBox to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
MarketBox 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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
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
MarketBox and Spike.sh, answered
What can start an automation from MarketBox?
Any of MarketBox's 3 triggers in the catalog, including New Booking, New Order Created and New Review. 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 MarketBox?
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 MarketBox?
Spike.sh has no triggers in the catalog today, so automations start in MarketBox. 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 MarketBox 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 MarketBox 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.