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

# CRM & marketing

> GoHighLevel, HubSpot, Pipedrive, Zoho, and Google Sheets.

General CRM and marketing platforms sync contacts and leads with Recepta.ai, so calls and bookings show up alongside the rest of your pipeline.

<Note>
  If you run a field-service CRM — Jobber, Housecall Pro, or ServiceTitan — that's the integration that matters most for booking and dispatch. See [Field-service CRM](/integrations/field-service-crm).
</Note>

## Supported

<AccordionGroup>
  <Accordion title="GoHighLevel" icon="chart-line">
    Contact sync, lead management, and campaign automation. GHL calendars can also serve as the availability source the agent books against — see [Calendars](/booking/calendars).

    The most complete of the general CRM integrations, and a common choice for agencies running Recepta.ai on behalf of clients.
  </Accordion>

  <Accordion title="HubSpot" icon="hubspot">
    Contact sync and lead management. Contacts created by calls and forms flow into HubSpot so your pipeline reflects phone activity.
  </Accordion>

  <Accordion title="Pipedrive" icon="pipe-valve">
    Contact sync and lead management.
  </Accordion>

  <Accordion title="Zoho CRM" icon="z">
    Contact sync and lead management.
  </Accordion>

  <Accordion title="Google Sheets" icon="table">
    Contact sync to and from a spreadsheet. Useful for teams whose list lives in Sheets today, and as a quick way to get data out for analysis.
  </Accordion>
</AccordionGroup>

## Connecting

All of these connect over OAuth from **Integrations**. Authorize with an account that has permission to read and create contacts, and that will still exist in six months.

<Warning>
  Decide which system owns contact data before you connect. Two systems both treating themselves as the source of truth produces duplicate records and edits that overwrite each other.
</Warning>

## Choosing a direction

<Columns cols={2}>
  <Card title="CRM as source of truth" icon="arrow-right">
    Your CRM holds customer data; Recepta.ai reads from it and pushes back call and booking activity. The usual arrangement when you already run a mature CRM.
  </Card>

  <Card title="Recepta.ai as capture point" icon="arrow-left">
    New leads arrive through calls, [web forms](/channels/web-forms), and ads, and flow out to the CRM. Sensible when most of your new business starts on the phone.
  </Card>
</Columns>

## Depth varies

These integrations are built around contact and lead sync. Deeper write-back — deals, pipelines, custom objects — differs by provider and is not uniform across them. If you depend on a specific field or object being written, test it end to end before you rely on it, and contact [info@recepta.ai](mailto:info@recepta.ai) if you need something that isn't there.

## Building your own

When the native integration doesn't reach far enough, the API and webhooks do:

<CardGroup cols={2}>
  <Card title="Contacts API" icon="code" href="/api-reference/contacts">
    Create, read, update, and delete contacts from your own systems.
  </Card>

  <Card title="Webhooks" icon="bolt" href="/api-reference/webhooks">
    Receive `call.ended`, `sms.received`, and `contact.created` as they happen.
  </Card>
</CardGroup>