Skip to main content
A read-only API key integration that syncs Attention sales call transcripts into Rippit on a schedule. For what applies to every integration, see how data integrations work. For the security model, see Data integration security. This page covers the data integration, which imports your Attention calls into Rippit. To let the Rippit agent search Attention live during a chat instead, see the Attention MCP server.

Connection summary

Before you connect

Rippit asks for an API key, created in Attention under Settings → Organization → API Keys. It can be a user-level key or an organization-level key. After you enter a user-level key, Rippit asks which calls to import:
  • Only my calls (the default): calls the key owner owns.
  • All calls my teams can see: every call the key owner’s teams can see.
An organization-level key has no owner, so Rippit skips that question and imports every team’s calls in your Attention organization.

Data handling

What a call becomes in Rippit

Each Attention call becomes one conversation in Rippit. Consecutive transcript segments from one speaker join the same turn until there is a pause of more than 3 seconds or the turn reaches 1,000 characters. Each turn carries the speaker name Attention identified, or the speaker’s email when there is no name. A turn with neither is attributed to a generic participant. A call’s start is the time its live stream started, or its creation time when Attention reports no stream start. The owner’s display name is the Attention user’s first and last name, or the organizer participant’s name. Speaker and owner emails are stored in lowercase.

API endpoints

The key lookup finds the key you entered in Attention’s list and reads whether it belongs to a user or to an organization. For a user-level key it also gives the owner’s user UUID, and Rippit adds filter[owner.id]=<owner UUID> to every call list request, field discovery included, unless you chose All calls my teams can see. Each sync repeats the lookup for an organization-level key and for Only my calls. If the sync cannot find the key in that list, it stops with an error rather than importing calls the key was not limited to. The organization lookup reads the organization UUID from the first team the key returns. It is only recorded alongside the connection, so a user-level key that cannot list teams still connects. There is no separate per-call fetch. detailedTranscript=true returns each call’s full transcript inline in the list, so one paged request both discovers calls and reads their content. No other Attention object is listed or swept. Owner, participants, and team come from the call record itself.

Sync behavior

Rate limiting

  • Every request, retries included, starts at least 1 second after the previous one, so a sync sends at most 60 requests per minute.
  • A 429 response pauses requests for up to 60 seconds, plus any Retry-After, and each request is tried at most 3 times.
  • Each page of up to 10 calls is one request. Each sync also spends one request on the credential check and, unless you chose All calls my teams can see, one more on the key lookup.