Tab32 Integration

What the AI can do

Summary

Tab32 Integration connects Tab32 (dental clinic management SaaS) with Newo Platform.

It enables:

• Checking available appointment slots across clinic locations
• Booking dental appointments with automatic patient record management
• Cancelling existing appointments
• Multi-location clinic support with intelligent location matching

This integration is designed for dental clinic administrators and front-desk teams who need automated appointment scheduling through a conversational AI agent (voice or chat).

Common use cases

• When a patient asks about available slots → Check Tab32 availability and return open time slots
• When a patient wants to book an appointment → Search/create patient record and schedule appointment in Tab32
• When a patient wants to cancel an appointment → Cancel the appointment in Tab32
• When a clinic has multiple locations → Agent uses LLM to match patient's preferred location from natural language
• When a new patient books → Automatically create patient record in Tab32 before booking

Features at a glance

Feature	Supported	Notes
Check Availability	✅	Date/time/location-based slot search
Book Appointment	✅	With automatic patient creation if needed
Cancel Appointment	✅	Requires booking_id from prior booking
Multi-Location Support	✅	LLM-powered location matching (Gemini)
Single-Location Mode	✅	Simplified setup with pre-selected location
Patient Search	✅	By phone number + name matching
Patient Creation	✅	Auto-creates during booking flow
Timezone Handling	✅	Converts slots to clinic's local timezone
Reschedule Appointment	❌	Cancel + rebook as workaround
Historical Data Import	❌	Only new events after activation

Before You Start

Before installation:

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

Setup

Create the Newo project

If this project already exists in Newo Builder, skip this subsection and continue with the integration-specific settings below.

1. In Newo Builder, open the projects list and click Create Project (or Create New Project from the top-right menu).

2. Fill IDN and Title. The exact names do not matter; use any clear names your team will recognize.
3. In Registry, choose the release channel:
   • staging — the newest module fixes appear here first. Use it when you need the latest fix, but expect possible unfinished changes.
   • production — the final stable version for live projects.
4. In Module, select the module for this integration.

5. Leave Module version on Latest version unless support tells you to pin a specific version, then click Create.

3.1 Step 1 — Generate API Key in Tab32

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

3.2 Step 2 — Connect in Platform

1. Open Newo → Projects
2. Set the following attributes in Builder / Attributes:

Attribute	Required	Description
tab32_api_key	✅	API Subscription Key (PDDS-Subscription-Key)
tab32_base_url	❌	API base URL (default: https://openapi.tab32.com/api)
tab32_multilocation	❌	Enable multi-location support (default: True)
tab32_slot_duration	❌	Slot duration in minutes: 15, 30, 45, or 60 (default: 30)
tab32_enable_booking	❌	Enable booking capability
tab32_enable_cancellation	❌	Enable cancellation capability
tab32_enable_slot_check	❌	Enable availability check
tab32_check_existing_client	❌	Verify if patient already exists before creating
tab32_enable_client_history	❌	Enable client history tracking

3. Click Save + Publish All
4. On publish, the SetupFlow automatically:
   • Validates the API key
   • Fetches clinic locations from Tab32
   • Configures booking tools for the agent

How to use the integration

This section explains how the integration works, how to configure automation, and how to test it.

4.1 How the Integration Works

The integration operates based on Triggers and Actions via the event-driven system.

• A Trigger is a system event that starts a flow
• An Action is the API operation performed in Tab32

Where to test

Testing can be done through the Newo conversation interface (chat or voice channel) by interacting with the agent. Use the chat transcript and external-system console to confirm the result.

How to test that everything works

To test the integration:

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

If no action occurs:

• Ensure tab32_api_key is set correctly
• Verify tab32_base_url points to the correct endpoint
• Confirm the integration was re-published after 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

Note: This integration performs real operations in Tab32. Appointments created or cancelled through the agent are reflected in the live Tab32 system.

FAQ

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

Q: Can I connect multiple Tab32 accounts? A: 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? A: 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 is created automatically.

Q: How does multi-location mode work? A: When enabled (tab32_multilocation=True), the agent 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? A: 15, 30, 45, or 60 minute slots, configured via the tab32_slot_duration attribute. Default is 30 minutes.

Q: Why are availability times shown in a different timezone? A: 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.