Skip to main content
Open Settings → Integrations → CRM. Each card shows its current connection state and, when setup is available, a Connect or Configure action.

​
Current connection cards

The dashboard currently provides configurable cards for:
  • ServiceTitan
  • AccuLynx
  • Housecall Pro
  • Jobber
  • HubSpot
  • Salesforce
  • Dynamics 365
  • FieldEdge
  • ServiceMinder
  • AutoOps
  • Xtime
  • Tekmetric
  • Google Calendar
Neighborly appears only for teams already configured to use the Neighborly integration. Google Calendar also has its own Integrations tab for account and service-routing settings. Use Configure ServiceTitan and Connect Housecall Pro for the provider-specific booking and catalog workflows.
Cards marked Coming Soon do not have a working setup flow. Do not create credentials or follow an old help article for one of those providers.

​
Connect or review a provider

  1. Confirm the selected Avoca team and the matching provider account.
  2. Read the status badge on the provider card.
  3. Choose Connect for a new connection or Configure for an existing one.
  4. Complete only the authorization or credential fields shown on that provider’s current page.
  5. Return to the CRM list and confirm that the card shows Connected.
  6. Import or map the catalog records required by your Avoca products.
  7. Run an approved lookup and booking test before relying on the integration for live traffic.
The supported actions and required fields differ by provider. Do not assume that a capability documented for one CRM—such as rescheduling, tags, or a particular sync—is available in another.

​
Connect or reconnect Jobber

The clearest path is Settings → Integrations → CRM → Jobber → Connect because Avoca already knows which team should receive the connection. Authorize the matching Jobber account, then return to Avoca and confirm that the card shows Connected. You can also start from the Avoca listing in the Jobber App Marketplace. Sign in to Avoca first. Marketplace setup can select a team automatically only when your Avoca user has exactly one eligible team; otherwise, return to Avoca’s Jobber integration page to choose the team. On the confirmation page, verify the team before selecting Connect Jobber. The email on the signed-in Avoca user must match the Jobber user who authorizes the app. To connect a different Jobber account, open the existing Jobber configuration and select Remove first. Confirm the removal and wait for it to complete before reconnecting; Avoca rejects an authorization attempt while an existing Jobber connection is still present.
Put provider secrets only in the dashboard’s secure credential fields or an Avoca-approved credential exchange. Never paste a password, client secret, or API key into a help article, ticket description, chat, or screenshot.

​
Connect an auto-service CRM location

AutoOps, Xtime, and Tekmetric use an enterprise connection managed by Avoca plus a location mapping for the selected team. Ask your Avoca contact to establish the enterprise connection before configuring a location. If the page says that the provider is not connected for the enterprise, the location cannot be linked yet. Enter the location identifier shown by the provider:
  • AutoOps: Client ID; Client name, Client key, and time zone are optional
  • Xtime: Dealer code; Dealer name and time zone are optional
  • Tekmetric: Shop ID; Shop name and time zone are optional
Select Connect for a new mapping or Save changes for an existing one. A saved mapping can still show a warning when Avoca could not complete all follow-up wiring; treat that state as incomplete and send the warning text to your Avoca contact without including credentials. The enterprise API or OAuth credential is shared across locations and is not customer-editable. Do not enter a secret into a location-name, identifier, or support-message field.

​
TradeEngage

Open Settings → Integrations → TradeEngage when your team uses TradeEngage to refer requests outside its service coverage. The page accepts the API key and brand location ID provided for the TradeEngage account and offers separate controls for:
  • requests outside your service area
  • requests for services your business does not offer
  • staging versus production delivery
  • enabling or disabling the integration
Keep the integration disabled or in the agreed testing environment until Avoca and your TradeEngage owner have verified the destination and referral conditions. Use the secure API-key field; do not share the value in a ticket. Deleting the integration removes its saved connection from the team, so coordinate that action before using it to troubleshoot a referral.

​
If a card does not connect

Check the selected team, your Integrations permission, the provider account, and any provider-side authorization. Some connections require setup coordinated by Avoca or the provider. Contact Avoca Support with the provider name and non-secret error message; do not include credentials.