> ## Documentation Index
> Fetch the complete documentation index at: https://help.avoca.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations overview

> Connect a CRM or calendar, manage data exchange, and find Avoca's supported API and webhook tools.

Open **Settings → Integrations**. The landing page opens the **CRM** tab and shows the connection state for the integrations available to your team.

<Note>
  Integrations requires the Integrations feature and an appropriate team role. Individual tabs can have additional product, plan, or role requirements.
</Note>

## CRM integrations

The CRM list can include configurable integrations such as ServiceTitan, AccuLynx, Housecall Pro, Jobber, HubSpot, Salesforce, Dynamics 365, FieldEdge, and ServiceMinder. Google Calendar is also shown for calendar-based scheduling. Neighborly appears only for teams already configured for it.

Use the status badge before taking action:

* **Connected** means a saved connection is present; choose **Configure** to review it.
* **Not Connected** means setup has not been completed for this team.
* **Coming Soon** is informational. It is not a working connection flow.

Connection requirements differ by provider. Follow the fields and authorization flow shown for that integration, and coordinate with Avoca when credentials or provider registration are managed on your behalf. See [Connect a CRM or provider](/integrations/provider-integrations) for the current workflow.

## Other Integrations tabs

* **Google Calendar** connects supported calendars and availability for calendar-based scheduling. See [Configure Google Calendar](/integrations/google-calendar).
* **TradeEngage** configures the TradeEngage integration when available.
* **Webhooks** manages supported event delivery when Event Webhooks is enabled.
* **API Keys** creates and manages credentials for supported Avoca APIs. Availability and key-management actions depend on your role. See [Manage webhooks and API keys](/integrations/webhooks-and-api-keys).
* **API Docs** is the current reference for the public API exposed to your team. Use it instead of copying endpoint examples from old help articles.
* **Data Export** configures supported recurring exports and destinations. See [Configure Data Export](/integrations/data-export).

## Connect safely

1. Confirm the selected Avoca team and the matching provider account.
2. Use a dedicated integration identity when the provider supports one.
3. Grant only the scopes required by the dashboard setup.
4. Complete provider authorization or coordinate the managed credential step with Avoca.
5. Return to Integrations and confirm the status is **Connected**.
6. Sync or import the required catalog data.
7. Test one lookup and one write action that your product needs, such as creating a test booking.

<Warning>
  Never send passwords, client secrets, API keys, or webhook signing secrets in a normal email or support-ticket description. Use the secure setup field or an Avoca-approved credential exchange.
</Warning>

Connecting a CRM and enabling **CRM Sync** are related but different. Integrations establishes provider access; **Settings → CRM Sync** controls ongoing entity synchronization and its health.