Connect Waitwhile to Spike.sh

Both apps 45Waitwhile 20Spike.sh 25

• 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.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.