--- title: "Connect Waitwhile to Spike.sh - APIANT.ai" description: "When \"New customer\" fires in Waitwhile, your agent runs \"Add alert rule\" in Spike.sh." canonical: "https://apiant.ai/connect/waitwhile-to-spike-sh" --- # Connect Waitwhile to Spike.sh When **New customer** fires in [Waitwhile](https://apiant.ai/connections/waitwhile), 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. Waitwhile **1** trigger Waitwhile **19** 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 Waitwhile 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 Waitwhile can start in Spike.sh - When **New customer** in Waitwhile then **Add alert rule** in Spike.sh - When **New customer** in Waitwhile 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 Waitwhile and Spike.sh ## Triggers and actions 1 trigger · 44 actions - Trigger **New customer** Triggered when a new customer is created in Waitwhile. - Action **Add customer note** Adds a note entry to a Waitwhile customer, optionally tied to a location or visit. - Action **Add location** Creates a new Waitwhile location, optionally copying users, resources, services, data fields and labels from an existing location, and returns the new location record. - Action **Add resource** Creates a resource, such as a staff member or room, at one or more Waitwhile locations and returns the new resource. - Action **Add service** Creates a new service in Waitwhile and makes it available at the locations you choose. Returns the service that was created. - Action **Create Customer** Creates a customer in Waitwhile from their name and contact details, and returns the new customer record. - Action **Create or Update a Visit** Creates a new visit at a Waitwhile location, or updates an existing visit when its id is supplied, and returns the resulting visit. - Action **Delete a Visit** Deletes a visit by its ID. - Action **Delete customer** Deletes a Waitwhile customer by ID. - Action **Fetch Customer** Returns one Waitwhile customer by id, including contact details, tags, locations, last visit information and metadata. - Action **Fetch Location** Returns a single Waitwhile location, with its address, hours, contact details and settings, by its id or short name. - Action **Fetch Resource** Returns one Waitwhile resource, such as a staff member or room, with its availability settings, locations and supported services. - Action **Fetch Service** Returns one Waitwhile service with its name, price, duration, availability settings, hours and locations. - Action **Fetch Visit** Returns a single Waitwhile visit by its id, including the customer's details, its state, timing and any custom data fields. - Action **Find User** Returns up to 100 Waitwhile users whose email address starts with the text you provide. - Action **Find visits by criteria** Returns the visits that match the criteria you specify, such as location, state, tag, customer, service, resource or date range. - Action **List booking slots** Returns the booking slots for a location within a date range, with the capacity, booked spots and available spots of each slot. - Action **Search for Customer** Returns the customers whose name, phone, email or customer identifier starts with the search text, optionally narrowed by location, visit state, tag or date range. - Action **Search for User** Returns the Waitwhile users whose email address starts with the text you provide, up to 100 users. - Action **Update customer** Updates an existing Waitwhile customer's name, contact details, tags, locations or metadata, and returns the updated customer. - 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 - [ **Waitwhile** Waitwhile is a leading waitlist and scheduling service that helps you improve your lines and create a...](https://apiant.ai/connections/waitwhile) - [ **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 Waitwhile - [ **Waitwhile to Galileo** Galileo is a tool that turns text into beautiful UI designs instantly with Galileo AI—fast, smart, and ready...](https://apiant.ai/connect/waitwhile-to-galileo) - [ **Waitwhile to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/waitwhile-to-zoom) - [ **Waitwhile to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/waitwhile-to-webflow) - [ **Waitwhile to Wix** The Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...](https://apiant.ai/connect/waitwhile-to-wix) - [ **Waitwhile to LinkedIn** LinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...](https://apiant.ai/connect/waitwhile-to-linkedin) - [ **Waitwhile to Facebook** Facebook is a social media and advertising platform used by individuals and businesses to connect, share...](https://apiant.ai/connect/waitwhile-to-facebook) ## 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 ## Waitwhile and Spike.sh, answered ### ### What can start an automation from Waitwhile? Any of Waitwhile's 1 trigger in the catalog, including New customer. 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 Waitwhile? 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 Waitwhile? Spike.sh has no triggers in the catalog today, so automations start in Waitwhile. 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 Waitwhile 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 Waitwhile 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.