Why Rippit ingests
Questions like “what changed in billing complaints this quarter” or “which issues have no help article behind them” read across thousands of conversations, and no helpdesk API is built to answer that in a single request. So Rippit ingests and stores every conversation, keeps them current, and performs analysis across the entire set. This means:- Results are fast, because nothing round-trips to your helpdesk at query time.
- Your helpdesk is not under analysis load. After the first backfill, Rippit’s API usage is a steady background sync, not a spike whenever someone asks a question.
What Rippit stores
Conversation records: the message history, the participants, and the fields you select, including custom fields. Zendesk, Freshdesk, and Slack attachments and Gong and Decagon recordings are downloaded and stored too. There is no storage limit. Rippit does not cap how many conversations you can bring in, and plans do not charge for storage. The first sync backfills the history you choose at setup, up to 90 days. After that, new conversations sync in on a schedule. Intercom, Zendesk, Freshdesk, Slack, Granola, and Decagon also pick up updates to conversations already synced. Gong, Fireflies, and Attention pick them up only while a conversation falls inside a periodic re-sweep: the last 7 days for Gong, the last 24 hours for the others.Access model
Every data integration is read-only. Rippit never changes your data in the source system. Slack is the one exception: Rippit joins the public channels you select and replies privately to whoever invites its bot to a channel, but never posts visible messages, edits, or deletes. Intercom, Zendesk, and Slack authorize through OAuth, so no password or API key is shared. Granola, Fireflies, Attention, Decagon, and Freshdesk connect with an API key, and Gong with an access key and secret, that you create in the source system and Rippit stores. Rippit can read only what the connected credential can read. A Zendesk token, or a Fireflies, Freshdesk, or user-level Attention key, sees what its user sees. For those, authorize with a dedicated account where you can: you control what it can see, and the connection does not break when someone leaves. Slack connects as a bot, and Rippit reads only the public channels you select and the private channels you invite the bot to. For the full security model, see Data integration security.Supported integrations
Rippit currently ingests from Intercom, Zendesk, Granola, Gong, Fireflies, Attention, Decagon, Freshdesk, and Slack. Each has its own page covering authorization, the API endpoints it calls, and its sync behavior.Reconnecting
When a source rejects Rippit’s access, for example because the authorization was revoked or the API key changed, the integration shows as Disconnected, and the objects under Collection state on its page show Not syncing. Reconnect on the integration’s page signs in again, or takes a new API key, on the same connection. Syncing resumes and the tables and history you already have are kept. An admin has to reconnect. Reconnecting with a different account works differently by integration:- Intercom, Zendesk, and Slack: signing in to a different account or workspace adds it as a new connection, and the original stays disconnected.
- Attention: a key from a different user or organization becomes a new connection, and the original is removed.
- Granola, Fireflies, Gong, Decagon, and Freshdesk: the new key replaces the old one on the same connection, so use a key from the same account.
Removing an integration
Remove on an integration’s page stops future syncing:- Zendesk: Rippit also asks Zendesk to revoke its token.
- Slack: Rippit revokes the bot token, unless another Rippit account still uses the Slack workspace.
- Intercom: Rippit stops using its stored token and makes no call to Intercom. The grant stays until you uninstall the Rippit app in Intercom.
- Granola, Fireflies, Gong, Attention, Decagon, and Freshdesk: Rippit stops using its stored key and makes no call to the source, so the key stays valid until you revoke it there.