Connect Airparser and Waitwhile

Both apps 30Airparser 10Waitwhile 20

• Trigger
  Document Parsed

  Triggers when Airparser finishes parsing a document in the chosen inbox, giving you the extracted data.

• Action
  Create an Inbox

  Creates a new Airparser inbox that documents can be sent to for parsing.

• Action
  Create or Update Extraction Schema

  Sets which fields Airparser should pull out of documents sent to an inbox, replacing whatever schema was there before.

• Action
  Delete an Inbox

  Deletes an Airparser inbox and the documents stored in it.

• Action
  Extract Data From a Document

  Sends a document to an Airparser inbox, waits for it to be parsed, and returns the extracted data.

• Action
  Extract Data From a Document (Async)

  Sends a document to an Airparser inbox and returns straight away without waiting for parsing. Use the Document Parsed trigger or Get Document to pick up the result.

• Action
  Get a Document

  Returns a parsed Airparser document, including the data extracted from it.

• Action
  Get an Inbox

  Returns one Airparser inbox with its settings, its email address prefix and its current extraction schema.

• Action
  List Documents

  Lists the documents in an Airparser inbox, with the data extracted from each one.

• Action
  List Inboxes

  Lists all the Airparser inboxes in the connected account.

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

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