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

# Supported integrations

> Which systems Rippit can ingest conversation data from, and what each one needs.

Rippit ingests conversation data from the systems below. Each one has its own page covering authorization, the API endpoints Rippit calls, and its sync behavior.

| Integration | What Rippit brings in                                                                                                                            | Setup needed first                                  | Guide                                       |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------- | ------------------------------------------- |
| Intercom    | Full message history for every synced conversation, participants, and custom attributes, including ones Intercom's schema endpoint does not list | Pick your region (US, EU, or AU) before authorizing | [Intercom](/plg/data-integrations/intercom) |
| Zendesk     | Full ticket content via ticket audits, ticket fields, and attachments, which are downloaded and stored rather than linked                        | A Zendesk Admin account to authorize                | [Zendesk](/plg/data-integrations/zendesk)   |

## What every integration has in common

* Connections are made by a **Rippit workspace admin**, and authorization happens through **OAuth**. No password or API key is shared with Rippit.
* Every integration is **read-only**. Nothing Rippit does writes back to your source system.
* Rippit can read only what the authorizing account can read. Use a dedicated service account where the source system supports one.
* The first sync backfills up to **90 days** of history. After that, new and updated conversations sync in on a schedule.
* There is **no storage limit** on how many conversations you bring in.
* **Disconnect** stops future syncing. It does not delete conversations already imported.

For the shared ingestion model, see [How data integrations work](/plg/data-integrations). For the security model, see [Data integration security](/security/data-integrations).