Connect Waitwhile to Vectara

Both apps 30Waitwhile 20Vectara 10

• 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
  Add corpus

  Creates a corpus (container for documents).

• Action
  Add document

  Adds a document to a Vectara corpus for indexing, either as a structured document (sections the platform chunks automatically) or a core document (explicit document parts).

• Action
  Delete corpus

  Permanently deletes a Vectara corpus and all of its documents and data. The corpus key is released and can be reused.

• Action
  Delete document

  Deletes a document from a corpus.

• Action
  Find documents by criteria

  Returns up to 100 documents in a corpus whose document metadata matches the specified filter expression.

• Action
  Get corpus

  Retrieves the settings and usage of a corpus by its key, without searching its contents.

• Action
  Get document

  Retrieves a document from a Vectara corpus, including its text parts, metadata, tables and images.

• Action
  List corpora

  Lists the corpora in the Vectara account, optionally filtered by name/summary or corpus ID.

• Action
  List documents

  Lists documents in a corpus.

• Action
  Query corpus

  Queries a corpus with full control over retrieval, hybrid search, reranking, and RAG generation.

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