Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

WaitWhile

WaitWhile is an appointment scheduling and queue management platform.

CategoryCommerce
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect WaitWhile with Flows360

WaitWhile is an appointment scheduling and queue management platform.

Use the WaitWhile connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and 2 triggers.

Available actions

  • Create a customer
  • Create or Update a Visit
  • Delete a visit
  • Search customers
  • Custom API Call

Available triggers

  • New Or Updated Message
  • New Or Updated Visit

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: WaitWhile
  • Package: @activepieces/piece-waitwhile@0.1.0
  • Exact artifact digest: sha256:cbf789bc4b2403f4a200b359f31bdd92c3c3fbef7ba5ac76259fed756039077f
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create a customer (createACustomer), Create a new customer in Waitwhile Classification: read.
  • Create or Update a Visit (createOrUpdateAVisit), Create a new visit or update an existing visit in Waitwhile Classification: read.
  • Delete a visit (deleteAVisit), Permanently remove a visit from the database. The visit will no longer be retrievable and will not be factored into analytics. Classification: read.
  • Search customers (searchCustomers), Search for customers by name, phone, email, or identifier Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Or Updated Message, webhook.
  • New Or Updated Visit, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actions5
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create a customer Yes No Create a new customer in Waitwhile
Create or Update a Visit Yes No Create a new visit or update an existing visit in Waitwhile
Delete a visit Yes No Permanently remove a visit from the database. The visit will no longer be retrievable and will not be factored into analytics.
Search customers Yes No Search for customers by name, phone, email, or identifier
Custom API Call Yes No Make a custom API call to a specific endpoint
New Or Updated Message Yes No webhook trigger declared by the pinned package.
New Or Updated Visit Yes No webhook trigger declared by the pinned package.

Supported actions

Create a customer · Read

Create a new customer in Waitwhile

create_acustomer · Risk: low · Retry: safe

Inputs

  • firstName · string · Required, Customer first name
  • lastName · string · Optional, Customer last name
  • phone · string · Optional, Customer phone number
  • email · string · Optional, Customer email address
  • tags · array · Optional, Tags associated with the customer
Create or Update a Visit · Read

Create a new visit or update an existing visit in Waitwhile

create_or_update_avisit · Risk: low · Retry: safe

Inputs

  • id · string · Optional, Select a Visit ID
  • customerId · string · Required, Select a Customer ID
  • locationId · string · Required, Select a Location
  • notes · string · Optional, Visit notes
  • partySize · number · Optional, Number of people in the party
  • startDate · string · Optional, Start date/time in ISO format (e.g., 2024-01-01T10:00:00Z)
Delete a visit · Read

Permanently remove a visit from the database. The visit will no longer be retrievable and will not be factored into analytics.

delete_avisit · Risk: low · Retry: safe

Inputs

  • visitId · string · Optional, Select a Visit ID
Search customers · Read

Search for customers by name, phone, email, or identifier

search_customers · Risk: low · Retry: safe

Inputs

  • q · string · Optional, Search query for name, phone, email, or customer identifier (prefix match)
  • locationId · string · Optional, Filter by location identifier
  • state · string · Optional, Filter by visit state
  • tag · string · Optional, Filter by tag associated with visit
  • limit · number · Optional, Max number of results (1-100, defaults to 20)
  • page · number · Optional, Page in results (defaults to 1)
  • fromDate · string · Optional, Start date in ISO-8601 format (e.g., 2024-01-01T00:00:00Z)
  • toDate · string · Optional, End date in ISO-8601 format (e.g., 2024-12-31T23:59:59Z)
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Or Updated Message · Webhook

Triggers when an SMS or EMAIL notification is created or its delivery status changes

New Or Updated Visit · Webhook

Triggers when a visit is created or updated

Setup

Setup

  1. Add the WaitWhile connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-waitwhile@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required WaitWhile connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-waitwhile@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com