Skip to main content
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.

​
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. For the security model, see Data integration security.