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

  • Every integration is read-only. Rippit never changes your data in the source system. The Slack bot joins the channels you select and replies privately to whoever invites it, and posts nothing else.
  • Rippit can read only what the connected credential can read. Where a credential belongs to one user, use a dedicated account.
  • The first sync backfills the history you choose at setup, up to 90 days. After that, new conversations sync in on a schedule. How updates to synced conversations are picked up varies by integration.
  • There is no storage limit on how many conversations you bring in.
  • Remove 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.