Tab32 is a cloud-based dental clinic management SaaS. This guide covers connecting Tab32 to Newo.ai so the AI Employee can check appointment availability, book appointments, and cancel appointments on behalf of patients.

Target audience : Newo.ai partners and technical teams
Integration type : Tab32 API ↔ Newo.ai platform
Use cases : Appointment availability checking, booking, and cancellation

Prerequisites

Before you begin, confirm the following:

An active Tab32 account with API access
Your Tab32 API Subscription Key (PDDS-Subscription-Key)
Tab32 API base URL (default: https://openapi.tab32.com/api)

Generate your API key in Tab32

Log in to your Tab32 account.
Navigate to the API management section.
Generate or locate your PDDS-Subscription-Key.
Copy the key and store it securely.

Connect Tab32 in the Newo Platform

Open the customer's Builder in Newo.ai.
Go to Attributes.
Set the following required attribute:
- Tab32 API Key : tab32_api_key — API Subscription Key (PDDS-Subscription-Key). Required.
Set any optional attributes:
- Tab32 base URL : tab32_base_url — API base URL. Default: https://openapi.tab32.com/api
- Multi-location : tab32_multilocation — Enable multi-location support. Default: True
- Slot duration : tab32_slot_duration — Appointment slot duration in minutes: 15, 30, 45, or 60. Default: 30
- Enable booking : tab32_enable_booking — Enable the booking capability
- Enable cancellation : tab32_enable_cancellation — Enable the cancellation capability
- Enable slot check : tab32_enable_slot_check — Enable availability checking
- Check existing client : tab32_check_existing_client — Verify whether a patient record already exists before creating a new one
- Client history : tab32_enable_client_history — Enable client history tracking
Click Save + Publish All.

On publish, the integration automatically validates your API key, fetches clinic locations from Tab32, and configures booking tools for the AI Employee.

Supported features

The integration supports the following capabilities:

Check availability — Date, time, and location-based slot search
Book appointment — Books a slot; auto-creates a patient record if one does not exist
Cancel appointment — Cancels a booking by booking_id
Multi-location support — LLM-powered location matching (Gemini) when multiple clinic offices are configured
Single-location mode — Simplified setup with a pre-selected location
Patient search — Looks up existing patients by phone number and name
Patient creation — Automatically creates a new patient record during the booking flow
Timezone handling — Converts available slots to the clinic's local timezone

The following are not supported:

Reschedule appointment — Use cancel + rebook as a workaround
Historical data import — Only appointments created after activation are processed

Multi-location support

When tab32_multilocation is set to True, the AI Employee uses an LLM (Gemini) to match the patient's natural language location description to the available clinic offices. The matched location is cached for the session.

When disabled, a pre-selected location is used instead (single-location mode).

Test the integration

After publishing, verify each capability using the Newo conversation interface (chat or voice):

Setup : Publish the project and confirm the logs show a successful location fetch.
Availability : Ask the AI Employee "What slots are available on Monday?" and verify that slots are returned from Tab32.
Booking : Complete a booking conversation and verify the appointment appears in the Tab32 dashboard.
Cancellation : Request cancellation of a booked appointment and verify the status changed in Tab32.

🗒️ NOTE

This integration performs real operations in Tab32. Appointments created or cancelled through the AI Employee are reflected in the live Tab32 system.

Troubleshooting

If the integration is not responding as expected:

Confirm tab32_api_key is set correctly.
Verify tab32_base_url points to the correct endpoint.
Confirm the integration was re-published after any configuration changes.
Check that the relevant feature flags are enabled: tab32_enable_booking, tab32_enable_slot_check, tab32_enable_cancellation.
In multi-location mode, verify tab32_offices was populated during setup.

FAQ

Q: Does the integration import historical appointments? No. Only appointments created or managed after activation are processed.

Q: Can I connect multiple Tab32 accounts? Each integration instance supports one Tab32 API key. For multiple accounts, create separate integration instances.

Q: What happens if a patient already exists in Tab32? The booking flow searches for existing patients by phone number and name. If a match is found, the existing patient record is used. If not, a new patient record is created automatically.

Q: How does multi-location mode work? When tab32_multilocation is set to True, the AI Employee uses an LLM (Gemini) to match the patient's natural language location description to the available clinic offices. The matched location is cached for the session.

Q: What slot durations are supported? Slot durations of 15, 30, 45, or 60 minutes are supported, configured via the tab32_slot_duration attribute. The default is 30 minutes.

Q: Why are availability times shown in a different timezone? All times are converted to the clinic location's local timezone. Verify that the correct timezone was imported during setup by checking the location_time_zone attribute.

Tab32 integration