> For the complete documentation index, see [llms.txt](https://docs.limecall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limecall.com/integrations.md).

# Integrations

Connect LimeCall to your CRM, calendar, chat and automation tools.

Open **Settings → Integrations**.

## What is available

| Integration         | What it does                                     |
| ------------------- | ------------------------------------------------ |
| **HubSpot**         | Two-way sync of contacts, calls and deals.       |
| **Slack**           | Notifications into a channel.                    |
| **Google Calendar** | Availability and booking for your assistant.     |
| **Zapier**          | Connect to thousands of apps without code.       |
| **Make**            | Visual automation with more control than Zapier. |
| **n8n**             | Self-hosted automation.                          |
| **Google Sheets**   | Push rows for reporting.                         |
| **Webhooks**        | Send events to your own systems.                 |

## Choosing an approach

**Use a native integration** where one exists. HubSpot, Slack and Google Calendar are purpose-built and handle the details correctly.

**Use Zapier or Make** when you need to connect something without a native integration and do not want to write code.

**Use webhooks** when you have developers and want full control. See [Webhooks](/integrations/webhooks.md).

## Before connecting anything

Decide what should be the source of truth for each kind of data. Two systems both authoritative on contacts produces conflicts that are tedious to unpick later.

Usually: your CRM owns the customer record, LimeCall owns the conversation record.

## Connecting

Most integrations connect with OAuth — you authorise LimeCall from the other tool's own login screen. You will be asked to grant specific permissions; read them.

{% hint style="warning" %}
Connect using an account that will still exist in a year. Integrations authorised under a departing employee's login stop working the day their account is deactivated, usually silently.
{% endhint %}

## Disconnecting

Disconnecting revokes the credentials. Any automation depending on that connection stops. Check what you have built before disconnecting anything.

## In this section

* [HubSpot](/integrations/hubspot.md)
* [Slack](/integrations/slack.md)
* [Google Calendar](/integrations/google-calendar.md)
* [Zapier, Make & n8n](/integrations/zapier-and-make.md)
* [Webhooks](/integrations/webhooks.md)