All integrations

Connect First AI Employee to Newbook.

Hospitality1 routeRoute facts checked August 28, 2026

This page shows every cataloged route for this app and marks the most capable working path. The recommended route is serving now after you authorize your own account.

You authorize and keep control of the provider account. No page view means an account is connected.

Every available route

More than one route is shown when it adds a real capability or gives you a customer-owned alternative. Recommended means most capable today, not already connected.

Set it up: Direct Newbook REST reservation connection

The Newbook owner supplies the REST username, REST password, regional API key, and the category or site the receptionist may book. The direct Newbook lane must be enabled for the deployment.

01

Create or obtain the least-privileged Newbook REST credentials.

02

Paste the username, password, API key, and region in Integrations and run the authentication check.

03

Choose the approved category or site in the receptionist configuration.

04

Run one test booking and compare its Newbook booking ID before enabling live calls.

Verify the complete result

Confirm that Newbook returns one booking ID with the expected category or site, dates, guest counts, and contact details.

Account ownership and data boundaries

The route sends only the event fields needed for the action you configure. Provider credentials stay in the approved connection or are sealed by First AI Employee where the guide explicitly says so.

  • Your provider and automation accounts remain yours.
  • A successful transport test is not the same as a verified provider write.
  • The pages never claim a native or two-way sync unless that exact capability exists.

Ready to connect it?

Use the dashboard to authorize your account, select the customer-owned destination, and test the complete downstream result.