> ## 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.

# Connect data through your assistant

> Authorize a data provider and start its initial import from a conversation with your assistant.

If your workspace has integration setup tools enabled, you can connect Zendesk,
Intercom, or Slack ingestion through your assistant. You need permission to
manage integrations in the destination workspace.

1. Ask your assistant to connect the provider to Rippit. It checks your current
   workspace, signed-in email, and existing connections. Confirm the
   destination.
2. Supply the Zendesk subdomain or Intercom hosting region when asked.
3. Open the authorization link. Sign into the same Rippit account, review the
   workspace, and authorize the provider. Keep passwords, API keys, tokens, and
   authorization codes out of the conversation.
4. Return to your assistant and choose **I'm done, continue** if it shows an
   authorization prompt. Otherwise, say **Done**. The assistant verifies the
   saved authorization request before continuing.
5. Choose how much history to import and any optional fields. The assistant
   starts the import and checks its progress.
6. Once a table is available, the assistant uses `status.workspaceTableId` to
   inspect it, checks its coverage, and continues
   your original question. Initial availability does not mean all historical
   data has finished importing.

For example:

> Connect our Intercom account to Rippit, import the last seven days, and tell
> me the most common reasons customers contacted support.

An existing authenticated connection can be reused. Repeating an import request
for a connection already importing or ready does not expand its history or
restart it. A failed initial import can be retried with its saved settings.

For Slack, add the Rippit bot to the channels you want imported. It can only
read channels it has access to.

Authorization links are restricted to the requester. A different account cannot
use a copied link. Expired or denied requests require a new link. If these tools
are unavailable, your assistant will direct you to Rippit's connection settings.

Clients supporting MCP protocol 2026-07-28 and URL elicitation show an **Open in
browser** prompt. Finish authorization in the browser, then select **I'm done,
continue** in your assistant. Rippit checks the same request before reporting
completion. Opening the link alone does not complete authorization. Other
clients receive a link and use status checks after you return to chat. This
feature does not send automatic browser-completion notifications.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.