Clari Copilot

Clari Copilot is a conversation intelligence platform that records, transcribes, and analyzes sales calls. It generates AI call summaries, surfaces highlights and action items, scores calls against coaching scorecards, and connects conversation data to deals and revenue insights. The Nexla connector lets you ingest calls, transcripts, summaries, users, teams, topics, scorecards, statistics, playlists, accounts, and opportunities from your Clari Copilot workspace.

Power end-to-end data operations for your Clari Copilot API with Nexla. Our bi-directional Clari Copilot connector is purpose-built for Clari Copilot, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Clari Copilot or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Clari Copilot workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

To connect Nexla to Clari Copilot, you need an active Clari Copilot workspace and a workspace role with access to integration settings (typically an administrator or workspace owner). Clari Copilot authenticates API requests using two values that are sent together as request headers: an API Key (sent as the X-Api-Key header) and an API Password (sent as the X-Api-Password header).

Generate Your Clari Copilot API Key and API Password

Clari Copilot issues a single API Key and API Password pair per workspace. Both values are required, and they are used together to authenticate every request.

1. Sign in to your Clari Copilot account at https://copilot.clari.com.

2. Open Workspace Settings from the workspace menu.

3. Navigate to Integrations, and select Copilot API.

4. Locate the API Key and API Password values displayed in this section. If no key has been generated yet, use the option provided to generate the API credentials.

5. Copy both the API Key and API Password values for use when creating your Nexla credential.

   Store your credentials securely

   The API Password may not be retrievable again after it is first generated or viewed. Copy it immediately and store it in a secure location. If the value is lost, you must revoke and regenerate the credentials, which will invalidate the previous pair.

Clari Copilot provides one API Key and API Password pair per workspace. Regenerating the credentials invalidates the previous pair, so any other integration using the prior values will stop working until updated. For complete details, refer to the Clari Copilot API documentation.

Authenticate

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

Clari Copilot uses API key authentication. The API Key and API Password are sent together as request headers (X-Api-Key and X-Api-Password) to authenticate Nexla with your workspace. Both values come from the Workspace Settings > Integrations > Copilot API section of your Clari Copilot account.

3. Enter the API key from your Clari Copilot workspace in the API Key field. This value is sent as the X-Api-Key header and identifies your workspace to the Clari Copilot API.

4. Enter the API password from your Clari Copilot workspace in the API Password field. This value is sent as the X-Api-Password header and is used together with the API key to authenticate each request. Keep this value secure, as it grants access to your workspace data.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Clari Copilot connector tile, then select the credential that will be used to connect to the Clari Copilot instance, and click Next; or, create a new Clari Copilot credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Clari Copilot endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

List Calls

Retrieves a paginated list of all recorded calls in your workspace. Use this endpoint to build an inventory of calls, track call volume over time, or collect call IDs to pass into the Get Call Details endpoint.

• Optionally, set the From Date field to fetch only calls recorded on or after a given date, formatted as yyyy-MM-dd. When left blank, this defaults to {now-30} (30 days ago).
• Optionally, set the To Date field to fetch only calls recorded on or before a given date, formatted as yyyy-MM-dd. When left blank, this defaults to {now} (today).
• Optionally, set the Page Size field to control how many calls are returned per page. The default is 100, which is also the maximum.

Nexla automatically paginates through the full result set, so all calls in the selected date range are ingested. The call IDs returned here can be used to configure the Get Call Details endpoint.

Get Call Details

Retrieves the full details for a single call, including the transcript, AI summary, action items, highlights, talk-time metrics, and scorecard scores. Use this endpoint when you need the complete conversation content and analysis for a specific call.

• Enter the unique call identifier in the Call ID field. This field is required. Call IDs can be obtained from the List Calls endpoint or from the call review page URL in the Clari Copilot console.

This endpoint returns the complete record for one call. To process details for many calls, first use the List Calls endpoint to gather call IDs, then reference those values to drive this endpoint.

List Users

Retrieves all users in the Clari Copilot workspace, including their roles and team membership. Use this endpoint to map call data to representatives or to build a roster for filtering and reporting.

• Optionally, set the Page Size field to control how many users are returned per page. The default is 100, which is also the maximum.

User IDs returned by this endpoint can be used to filter or join call, statistics, and scorecard data by representative.

List Teams

Retrieves all teams defined in the Clari Copilot workspace. Use this endpoint to group and filter call and statistics data by team.

• This endpoint automatically retrieves all teams in the workspace. No additional configuration is required beyond selecting this endpoint template.

Team information is useful for organizing reporting by sales group and for combining call data with user membership from the List Users endpoint.

List Topics

Retrieves keyword topics discussed across calls, with metadata such as type, timestamps, and relevance scores. Use this endpoint to analyze which themes appear in conversations.

• Optionally, set the Page Size field to control how many topics are returned per page. The default is 100, which is also the maximum.

For enriched topic data with richer metadata and contextual information, use the List Topics V2 endpoint instead.

List Topics V2

Retrieves enriched topics across calls via the v2 endpoint, which provides richer metadata, scores, and contextual information than the original Topics endpoint. Use this endpoint for more detailed topic analysis.

• Optionally, set the Page Size field to control how many topics are returned per page. The default is 100, which is also the maximum.

The v2 endpoint returns the same topics as List Topics but with additional context and scoring fields, making it preferable for advanced analytics.

List Scorecards

Retrieves all scorecard templates configured in the account, including criteria definitions and scoring rubrics. Use this endpoint to understand how calls are evaluated and to build coaching and quality-assurance reports.

• Optionally, set the Page Size field to control how many scorecard templates are returned per page. The default is 100, which is also the maximum.

Scorecard templates define the criteria used to evaluate calls. Per-call scores are available in the response from the Get Call Details endpoint.

Get User Stats

Retrieves per-representative statistics, including talk ratio, call count, and engagement metrics, for a specified date range. Use this endpoint to track individual rep performance over time.

• Optionally, set the From Date field to define the start of the stats reporting window, formatted as yyyy-MM-dd. When left blank, this defaults to {now-30} (30 days ago).
• Optionally, set the To Date field to define the end of the stats reporting window, formatted as yyyy-MM-dd. When left blank, this defaults to {now} (today).

Combine this endpoint with the List Users endpoint to attach user names and team membership to the per-representative statistics.

Get Aggregate Stats

Retrieves account-level aggregate statistics, including total calls, average duration, and talk ratio, for a specified date range. Use this endpoint for workspace-wide trend reporting.

• Optionally, set the From Date field to define the start of the aggregate stats window, formatted as yyyy-MM-dd. When left blank, this defaults to {now-30} (30 days ago).
• Optionally, set the To Date field to define the end of the aggregate stats window, formatted as yyyy-MM-dd. When left blank, this defaults to {now} (today).

This endpoint returns a single aggregate summary for the workspace rather than per-user breakdowns. For per-representative metrics, use the Get User Stats endpoint.

List Playlists

Retrieves all call playlists and coaching libraries configured in the account. Use this endpoint to discover curated collections of calls used for training and coaching.

• Optionally, set the Page Size field to control how many playlists are returned per page. The default is 50.

Playlist IDs returned by this endpoint can be used to configure the Get Playlist Calls endpoint to retrieve the calls contained in a specific playlist.

Get Playlist Calls

Retrieves all calls included in a specific playlist or coaching library. Use this endpoint to ingest the curated set of calls associated with a training collection.

• Enter the unique playlist identifier in the Playlist ID field. This field is required. Playlist IDs can be obtained from the List Playlists endpoint.
• Optionally, set the Page Size field to control how many calls are returned per page. The default is 100, which is also the maximum.

Use the List Playlists endpoint first to obtain the Playlist ID needed to configure this endpoint.

List Accounts

Retrieves CRM-linked accounts associated with Clari Copilot calls. Use this endpoint for pipeline and account-level analysis that connects conversations to specific customer accounts.

• Optionally, set the Page Size field to control how many accounts are returned per page. The default is 100, which is also the maximum.

Account data links conversation intelligence to your CRM, enabling reporting that combines call activity with account-level context.

List Opportunities

Retrieves CRM-linked opportunities associated with Clari Copilot calls. Use this endpoint for deal-level conversation analysis that connects calls to specific opportunities.

• Optionally, set the Page Size field to control how many opportunities are returned per page. The default is 100, which is also the maximum.

Opportunity data links conversations to specific deals, enabling analysis of how call activity relates to pipeline stage and deal outcomes.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Clari Copilot data sources can also be manually configured to ingest data from any valid Clari Copilot API endpoint, including endpoints not covered by the pre-built templates, chained API calls to fetch data from multiple endpoints, or sources that require custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Clari Copilot data retrieval uses the GET method. Endpoints are served from the https://rest-api.copilot.clari.com base URL—for example, https://rest-api.copilot.clari.com/calls to list calls or https://rest-api.copilot.clari.com/users to list users. Several endpoints, such as /calls and /stats, accept from and to date parameters in yyyy-MM-dd format, defaulting to the last 30 days when left blank, which makes date/time macros especially useful for incremental ingestion. List responses nest their array under a top-level key matching the resource name—for example, set the Path to Data to $.calls[*] for the List Calls endpoint, or $.users[*] for List Users—and pagination metadata alongside the array can be captured with a Path to Metadata. The X-Api-Key and X-Api-Password authentication headers are handled automatically by Nexla based on your Clari Copilot credential and do not need to be added manually. The complete list of available endpoints is documented in the Clari Copilot API reference.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Clari Copilot data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.