Skip to main content
Built-in integrations pull conversations straight from the tools your team already uses. Once connected, Rippit keeps importing new conversations into a data table. Supported from the API today: Zendesk, Intercom, Slack and Gong. See supported integrations for everything you can connect in the Rippit app.

​
How it works

  1. Check the workspace. get_integration_state with query: {kind: "workspace"} confirms which workspace the data will land in, who is signed in, which providers are supported and what’s already connected.
  2. Authorize the provider. connect_integration with a provider returns an authorization link. Zendesk needs its subdomain and Intercom its region (us, eu or au); Slack and Gong need only the source. The user opens it, signs in to the same Rippit account and authorizes the provider in the browser. For Gong, they enter the access key, secret and subdomain there. Credentials never pass through the API or your assistant.
  3. Confirm it’s authorized. get_integration_state with query: {kind: "request", request_id} reports when the authorization is complete. Authorized is not the same as imported.
  4. Start the import. import_integration with action: "start", plus the source, account_id and etl_id from the previous step. Choose how much history to pull with history_days.
  5. Watch it. get_integration_state with query: {kind: "connection", ...} reports progress. When it’s ready, status.workspaceTableId is the table to query.
list_active_integrations lists every connection in the workspace with its ids.

​
Good to know

  • Authorization links are for the person who requested them, and stay open for 30 minutes. Check a pending link with get_integration_state before creating another.
  • Starting an import again on a connection that’s importing or ready reports its current state. It doesn’t restart it or extend its history.
  • A failed import can be retried with action: "retry". A retry keeps the original history and field choices.
  • Slack imports only see channels the Rippit bot has been added to.
  • A ready import doesn’t guarantee every conversation in the history window has arrived. Check coverage with describe_table before reporting totals.

​
Operations

See the operation pages in this section for every parameter.