Connect Tableo to your AI Employee to let restaurant guests check availability, select a dining area, book a table, modify an existing reservation, or cancel — all through a phone or chat conversation.
Prerequisites
An active Tableo restaurant account with admin access
Your restaurant's Tableo API token (retrieved from the Tableo admin panel)
At least one dining area configured in Tableo (e.g., "Main Dining," "Terrace")
Reservation availability set up in Tableo for your intended dates and party sizes
Access to the Builder with publish permissions
Add a project
Add the Tableo integration module to the customer's Builder. Follow the steps in Create a new project using these values:
Field | Value |
|
|
|
|
|
|
|
|
Ensure Auto update enabled is on, then click Create. Once created, click the three dots next to the project and select Force Update Project to pull the latest module version.
Configure the Tableo integration in the Builder
In the Builder, go to Attributes and search for
tableo.Enable Show Hidden to display all related attributes.
Set the following attributes and click Save after each:
Attribute | Required | Description |
| No | A display name for this connector (e.g., the restaurant's name). Default: |
| Yes | Bearer token from the Tableo admin panel. Paste it exactly as provided — don't add the word "Bearer". |
| No | Enable availability checking. Default: |
| No | Enable reservation creation. Default: |
| No | Enable returning-customer lookup by phone number. Default: |
| No | Enable reservation cancellation. Default: |
| No | Enable rescheduling of existing reservations. Default: |
| No | Auto-install the default Via Agent booking scenarios on the conversation canvas. Default: |
| No | Number of upcoming days to check for a returning guest's existing reservations. Default: |
| No | Number of days ahead of the requested date to search for available slots. Default: |
Click Publish All.
What the AI Employee can do
Once configured, the AI Employee can handle the following during a guest conversation:
Availability checking — queries Tableo for live reservation slots by date and party size
Dining area selection — presents available areas when multiple options exist
Booking — creates confirmed reservations in Tableo with full guest details
Returning guest recognition — matches callers by phone number to surface existing reservations
Cancellation and rescheduling — modifies or removes accepted reservations
Test the integration
After publishing, verify each capability using the Newo conversation interface:
Availability — ask "Do you have a table for 4 on Saturday at 7 PM?" and confirm the slots match what the Tableo admin panel shows.
Booking — complete a reservation conversation and verify the booking appears in Tableo with the correct guest details.
Lookup — call from a phone number associated with an existing reservation; the AI Employee should surface it.
Cancellation and rescheduling — request a change and verify the reservation status updates in Tableo.
Troubleshooting
Confirm the API token is valid and was copied without extra whitespace.
Re-publish after any attribute change for the update to take effect.
If the AI Employee cannot find a guest's reservation by phone, check that the number in Tableo matches the caller's format exactly.
If dining area options are missing, confirm areas are configured and available in the Tableo admin panel before the availability check is triggered.
The phone-number lookup window is limited to upcoming reservations within
tableo_booking_lookup_days(default: 7 days). Reservations outside this window will not be returned.
Limitations
Cancelled reservations are excluded from active booking lists.
Some Tableo API errors may not surface a detailed message in the conversation — the AI Employee will handle these gracefully.
Dining area selection is based on the most recent availability check. If the guest changes their date or party size, availability is re-checked and the area list refreshes.
One Tableo restaurant per Newo project. For multiple restaurants, create separate projects.
