Connect First AI Employee to Towbook.

Industry software1 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.

Recommended route

Direct public Website Integration dispatch connection

The receptionist can read the company's enabled Towbook request options during setup and create one Towbook service request with the caller, pickup, destination, vehicle, and notes. This is a bounded public request write, not a private Towbook account sync. It does not read the dispatch board, assign a truck, select a driver, provide an ETA, update an existing call, or guarantee that a tow has been accepted. Activation is conditional on the deployment flag and the customer-owned public form passing preflight.

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.

Direct API

Direct public Website Integration dispatch connection

Serving now

Recommended route

What it does

The receptionist can read the company's enabled Towbook request options during setup and create one Towbook service request with the caller, pickup, destination, vehicle, and notes.

Before you start

Paste the company's official Towbook public Website Integration URL or four-character code. No Towbook password, API key, Zapier account, or developer registration is required. Website Integration requests must be enabled for that company.

What it does not do

This is a bounded public request write, not a private Towbook account sync. It does not read the dispatch board, assign a truck, select a driver, provide an ETA, update an existing call, or guarantee that a tow has been accepted. Activation is conditional on the deployment flag and the customer-owned public form passing preflight.

Set it up

Open Towbook in Integrations and paste the official public request URL or its four-character code.
Run the setup check and confirm that Towbook reports the public request page enabled.
Choose the returned reason and vehicle type defaults the receptionist may use.
Create one non-production request and confirm Towbook returns its call number or dispatch-entry ID before using live callers.

Provider documentation

Set it up: Direct public Website Integration dispatch connection

Open Towbook in Integrations and paste the official public request URL or its four-character code.

Run the setup check and confirm that Towbook reports the public request page enabled.

Choose the returned reason and vehicle type defaults the receptionist may use.

Create one non-production request and confirm Towbook returns its call number or dispatch-entry ID before using live callers.

Verify the complete result

Compare the returned call number or dispatch-entry ID with the customer's Towbook account and confirm exactly one request exists with the expected pickup, caller, and vehicle 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.

Open Integrations in your dashboard Browse all app guides