Clari Copilot is a conversation intelligence platform that records, transcribes, and analyzes sales calls. Integrating Clari Copilot with Frontegg lets your application list calls and read their transcripts, work with scorecards and templates, read topics and users, and look up accounts, contacts, and deals on behalf of your users — all through Frontegg's integration layer. Clari Copilot's API authenticates with an API key and API password pair, so there is no OAuth flow.
The connector can also ingest calls and create accounts, contacts, and deals, but those write operations are disabled by default. Enable them deliberately, and only for a workspace where writing to conversation and CRM data is intended.
Prerequisites
Prerequisites
- A Clari Copilot account
- Administrator access to generate API credentials in Clari Copilot
Clari Copilot authenticates API requests with two values that are generated together in the admin settings: an API Key (sent in the X-Api-Key header) and an API Password (sent in the X-Api-Password header).
Sign in to Clari Copilot as an administrator and open the API settings in the admin area.
Generate a new API credential. Clari Copilot issues an API Key and an API Password together. Copy both values.
Copy your credentials now
Copy your credentials now
The API Key and API Password are shown only once, when they are created. Copy them immediately and store them securely — treat them like a password. If they are exposed, revoke them in the admin settings and generate new ones.
Once you have your API Key and API Password, configure the integration in the Frontegg portal:
- Open the Frontegg portal and navigate to [ENVIRONMENT] → Integrations → Clari Copilot.
- Enter the API Key and the API Password in the corresponding fields.
- Click Save.
Keep your credentials secure
Keep your credentials secure
Never share or commit your API Key or API Password to version control.
- Read calls with their transcripts — Call details come back with the transcript, topics, scorecard comments, and deal stage in one response.
- Signed media links — Call audio and video can be requested as signed URLs. Each link is valid for four hours, so fetch the media rather than storing the link.
- Narrow filters on the call list — Calls can be filtered by the users involved, meeting attendees, topics, processing status, source platform, source identifier, scheduled or modified time, and duration, and sorted by scheduled time or by when they were last processed.
- Faster listings — The total-count part of a listing can be omitted for a quicker response when you only need the current page.
- Optional call ingestion — When write access is enabled, a recording can be pushed in from another system, either for Clari to transcribe or with a transcript you already have.
- Accounts, contacts, and deals are addressed by their source CRM identifier — Not by a Clari identifier. An identifier taken from your own CRM integration will not resolve here unless it is the same identifier Clari mirrored, and the lookup answers that no such record was found. This is the most common reason a record that plainly exists cannot be fetched.
- Private calls are excluded by default — They appear only when the request explicitly asks for them.
- Paging is capped — A listing returns at most 100 records per request and cannot skip past 10,000 records, so very large histories must be narrowed with filters rather than paged through to the end.
- Duration filters top out at two hours — Longer thresholds are rejected.
- Rate limits — The vendor allows roughly 10 requests per second and 100,000 per week; bulk exports need to be paced.
- Empty scorecards are normal — A workspace that has never used scorecards returns an empty list rather than an error, while scorecard templates may still be present.
- Ingested calls need matching participant details — When pushing a call in, the external participants' names, email addresses, and phone numbers must be supplied as equally long lists, and at least one internal user must be named as the recording owner.
- Re-sending a call does not overwrite it — Calls are de-duplicated by their source-system identifier; replacing an existing one requires explicitly asking for the overwrite.