Known limitations

Review these limitations before turning on beta Zaps.

Private beta access

The TracsConnect Zapier app is shared by private invite only. It is not listed in Zapier’s public app directory, and public setup is not approved yet.

Private beta use requires:

• The TracsConnect tenant feature flag integrations.zapier.
• A scoped API key created in the dashboard.
• A private Zapier app invite accepted by the Zapier account that owns the Zaps.

Trigger timing

Visible beta triggers use Zapier REST Hooks for event delivery when the Zap is on and subscribed. Zapier also calls recent-record polling endpoints during setup, testing, and fallback sample collection.

REST Hook delivery is still beta. If a hook subscription is not active, the Zap is paused, or the event producer cannot enrich a payload, the connector falls back to recent-record data and the fields available from that record.

The New Customer trigger is intentionally search-term based during beta. It is useful for focused workflows, but it is not a full “all new customers” feed.

The New or Updated Work Order trigger uses recent work-order data for setup and fallback. The New Appointment trigger uses event delivery plus recent or upcoming calendar data for setup and fallback. For older history, use TracsConnect reporting workflows instead of Zapier beta triggers.

Data sharing

Zapier receives the fields needed for the trigger, search, or create action you configure. Depending on the Zap step, this can include customer contact details, vehicle identifiers, appointment details, work-order identifiers, and shop context.

Only create Zapier keys for users who are allowed to automate that shop’s data. Limit each key to the shops that the Zapier account actually needs.

Zapier result objects include a stable dedupe id, resource type, resource id, shop UUID, timing fields when available, a summary label, and a data object with fields for the selected resource. Do not send Zapier output to another app unless that app is approved to receive those customer, vehicle, appointment, or work-order details.

Capability boundaries

The private beta is deliberately narrow:

• Customer search can match customer names, phone numbers, email addresses, or customer details.
• Vehicle search is limited to VIN or TracsConnect customer id.
• Work-order search filters recent returned work orders by summary fields such as work-order number, customer, vehicle, or status.
• Appointment search filters recent returned appointments by subject, customer, vehicle, or summary.
• Create Customer requires a phone number and either a first name or company name.
• Create Appointment requires an existing TracsConnect customer id, existing vehicle id, start time, and end time.

Unsupported actions

The beta intentionally does not expose:

• Payment collection or payment posting
• Accounting exports or ledger posting
• Invoice posting, mark-posted, or mark-unposted actions
• Broad work-order mutation actions
• Direct TRACS database access

Use safe create actions only after testing with sample data.

Search results

Searches return the records visible to the selected shop and key scope. Empty results usually mean the shop selection, search text, or API key scope does not match the data.

Some beta operations use recent-list endpoints and local filtering until dedicated search endpoints are expanded.

For vehicle searches, use a VIN or a known TracsConnect customer id. General vehicle text such as make, model, color, or plate is not a supported beta search input yet.

Rate limits

Zapier private app usage is subject to Zapier plan limits and TracsConnect API protections. High-frequency setup testing, broad searches, repeated fallback polling, or many active Zaps using the same private app may be throttled.

Use narrow search terms, avoid duplicate Zaps watching the same data, and pause failing Zaps while troubleshooting.