Skip to main content
A read-only API key integration that syncs Decagon AI agent conversations into Rippit on a schedule. For what applies to every integration, see how data integrations work. For the security model, see Data integration security.

Connection summary

Before you connect

Rippit asks for an API key and an optional team ID. Find or create the API key on the Developer page of your Decagon dashboard. The team ID is needed only if you connect more than one Decagon team, so each connection has its own name. It accepts letters, numbers, underscores, and hyphens.

Data handling

What a conversation becomes in Rippit

Each Decagon conversation becomes one conversation in Rippit. When you choose fields during setup, the list shows the fields above plus other attributes from your Decagon conversations: top-level conversation attributes such as conversation_url and updated_at, and metadata attributes, shown with metadata_ in front of the name. Rippit finds them by checking the first 50 conversations updated in the last 7 days. An attribute shows if at least one of those conversations has a single text, number, or true/false value for it. Lists, nested objects, and metadata keys ending in jwt or token never show. The sample decides what shows in the list:
  • An attribute used only on conversations outside the 50 checked does not show. When more than 50 conversations were updated in the last 7 days, an attribute added in the last day or two may not show.
  • If no conversation was updated in the last 7 days, the list shows only the fields above.
After setup, the list of fields you can add to the table is rebuilt at most every 6 hours from a small sample: one recently collected conversation, plus the oldest page of conversations updated in the last 30 days and the oldest page from all time. Each rebuild replaces the previous list. A commonly used new field usually appears within hours. A rarely used one can be missed, or drop out of the list at a later rebuild.

API endpoints

The credential check sets an upper bound of 0, the Unix epoch, so it always returns an empty page and reads no conversations. /conversation/export returns each conversation in full, with its messages, so no other endpoint is called for content. Timestamps are Unix seconds. Decagon pages with a next_cursor timestamp, and Rippit requests the next page by moving min_timestamp to it. Recordings. For each voice conversation, Rippit first requests a signed URL from /conversation/recording_url/<conversation ID> with the API key, then downloads the file from that URL. A recording that fails 4 times, or that Decagon returns no URL for, is not retried, and the conversation shows no recording. The API key is sent only to URLs on an api.decagon.ai host.

Sync behavior