Troubleshoot

Zapier cannot find TracsConnect

In Zapier

The beta app is private. Open Zapier using the invite URL from your rollout contact, then accept the invite with the same Zapier account that will own the Zap.

If the app still does not appear, ask the rollout owner to confirm the Zapier account was invited to the current integration version.

The authentication test fails

Check these items:

• The API key was copied from the dashboard before closing the one-time secret panel.
• The key has not been revoked.
• The tenant still has the integrations.zapier beta feature enabled.
• The key is scoped to at least one shop.
• Zapier has no extra spaces before or after the key.

If the secret was lost, rotate the key in TracsConnect and paste the new value into Zapier.

A Zapier step is missing

The private beta exposes only these visible steps:

• Triggers: New Customer, New or Updated Work Order, New Appointment
• Searches: Find Customer, Find Vehicle, Find Work Order, Find Appointment
• Actions: Create Customer, Create Appointment

If you expected payment, accounting, invoice, or work-order mutation steps, those are not available in the beta app.

If a supported create action is missing or blocked, confirm the API key includes Safe create actions. Read-only keys can still authenticate and run trigger/search steps.

A trigger returns no records

Visible beta triggers use REST Hook subscriptions when the Zap is on. Zapier test/setup screens may still call recent-record endpoints for samples.

If the trigger still returns nothing:

• Confirm the selected shop has matching data.
• Use a record created or updated after the Zap was turned on.
• Check that the API key includes the selected shop.
• Confirm the Zap step is using the expected TracsConnect connected account.
• For New Customer, use a search term with at least two characters that matches the customer data you expect.
• For New or Updated Work Order, test with a recent work order.
• For New Appointment, test with a recent or upcoming appointment.

A search returns no records

Use a narrower search term that exactly matches a known customer, vehicle, work order, or appointment.

For work orders and appointments, remember that beta searches may rely on recent records plus local filtering. Very old records may not appear until dedicated search endpoints are expanded.

For vehicles, use a VIN or known TracsConnect customer id. Make/model-only, color-only, and plate-only searches are not supported beta inputs yet.

Create customer or appointment fails

Confirm the key includes Safe create actions. Read-only keys can run triggers and searches, but cannot create TracsConnect records.

Then check required fields in the Zap step. Appointment creates need a valid shop and appointment details. If the Zap is using customer or vehicle ids, confirm those ids came from TracsConnect search steps.

Create Customer requires a phone number and either a first name or company name. Create Appointment requires an end time after the start time, plus an existing customer id and vehicle id that belong to the selected shop.

REST Hook or trigger setup fails

Confirm the Zap is on, the selected TracsConnect account is connected, and the key includes Read triggers and searches. If the Zap was copied from another account, reconnect the TracsConnect step so Zapier creates a fresh hook subscription.

If setup still fails, rotate the TracsConnect key, reconnect the Zapier account, and test with a recent customer, work order, or appointment in the selected shop.

A Zap starts failing after key changes

If a key was rotated, paste the new one-time secret into the connected account in Zapier. If a key was revoked, create or rotate a key and reconnect the Zap.

After reconnecting, test the Zap step, turn the Zap back on, and confirm at least one successful Zap run.