Ada

A read-only API key integration that syncs Ada AI agent conversations and messages into Rippit on a schedule, using Ada’s Data Export API. Ada is in beta. For what applies to every integration, see how data integrations work. For the security model, see Data integration security. This page covers importing Ada conversations as data. To let the Rippit agent read Ada’s metrics and configuration directly, see the Ada connector.

​

Connection summary

​

Before you connect

Rippit asks for two values. The Ada handle is the part of your Ada dashboard URL before .ada.support: acme in acme.ada.support. You can paste the whole URL and Rippit extracts the handle. Rippit always connects to https://<handle>.ada.support, and the handle accepts only letters, numbers, and hyphens. The API key must be a Data Export API key, created in your Ada dashboard. If you don’t see the Data Export API in your dashboard, it may not be included in your Ada contract. Contact your Ada team or email help@ada.support to confirm.

​

Data handling

​

What a conversation becomes in Rippit

Each Ada conversation becomes one conversation in Rippit. Ada intents list each intent with its Ada status in parentheses, such as Billing question (pending), so intents Ada has not yet accepted are not shown as settled. Ada Playbooks, Playbook outcomes, knowledge articles, and coaching types are filled only for conversations handled by a generative Ada AI agent. On other conversations they are empty. When you choose fields during setup, the list shows the fields above plus other attributes from your Ada conversations: top-level conversation attributes, and metavariables, shown with metavariables_ 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 and nested objects never show, and neither do metavariables whose names end in jwt, token, secret, or password. The sample decides what shows in the list:

• An attribute used only on conversations outside the 50 checked does 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 built from one page of conversations updated in the last 30 days.

​

API endpoints

All paths are under https://<handle>.ada.support/api/v2. Timestamps are ISO 8601 in UTC. Ada pages with meta.next_page_uri, and Rippit follows it until it is absent. Conversations and messages are listed separately. Conversations are matched to their messages by conversation ID, so a conversation’s messages can arrive in a different sync from the conversation itself.

​

Sync behavior

​

Rate limiting

Ada’s Data Export API allows 3 requests per second and 15,000 requests per day for each Ada instance. The daily quota is shared with any other exports you run against the same instance. Rippit pages with the largest page size Ada allows, and re-syncs a single conversation with at most 3 requests at a time. When Ada reports the daily quota is used up, Rippit saves its progress, stops for that sync, and picks up where it left off on a later scheduled sync. A large backfill or a busy instance can take more than a day to catch up, which is why the default backfill is 30 days rather than 90.