Clari is a revenue orchestration platform that unifies forecasting, pipeline management, conversation intelligence, and revenue analytics across the go-to-market organization. The Clari Revenue connector lets Nexla exchange data with the Clari API to export forecast and activity data, retrieve opportunity and audit records, ingest entity data back into Clari, and manage long-running export and ingest jobs.
Power end-to-end data operations for your Clari Revenue API with Nexla. Our bi-directional Clari Revenue connector is purpose-built for Clari Revenue, 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 Revenue or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Clari Revenue 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
The Clari Revenue connector authenticates to the Clari API using an API token that is generated from within the Clari web application. The token is passed by Nexla as a bearer token in the Authorization header on every request, so the only credentials you need to gather before creating a Nexla credential are a valid API token and the Clari API base URL.
API tokens are created from your Clari user profile. Generating a token requires that your Clari user account has permission to access the relevant revenue, opportunity, audit, and ingest data, so confirm your account's access level with your Clari administrator before starting.
Click your profile avatar in the top navigation, and select Settings to open your user settings.
In the settings navigation, select API tokens.
Click Generate new API token.
Enter a descriptive Token name (for example, "Nexla Integration") so the token can be easily identified later, and then click Generate new token.
Copy the generated API token and store it securely. You will paste this value into Nexla in the steps below.
Important
The API token is displayed only once at the time of creation and cannot be viewed again. If the token is lost, revoke it and generate a new one. Store the token in a secure location, as it grants access to your Clari revenue data.
For complete information about Clari API tokens, authentication, and available endpoints, refer to the official Clari developer documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Clari Revenue uses API key authentication. Enter the API token you generated in Prerequisites in the API Key field. Nexla sends this token as a bearer token in the Authorization header of each request to the Clari API, so it should be kept secure.
Enter the Clari API base URL in the Base URL field. This value defaults to the Clari production environment, https://api.clari.com/v1, which is appropriate for most accounts. Modify this value only if your Clari account is provisioned to use a different API base URL.
Nexla validates the credential by calling the Clari Get Limits endpoint ({base_url}/admin/limits). A successful validation confirms that the API token and base URL are correct.
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 and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Clari Revenue connector tile, then select the credential that will be used to connect to the Clari Revenue instance, and click Next; or, create a new Clari Revenue credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Clari Revenue 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.
Create Forecast Export
This endpoint initiates a new forecast export job in Clari. Use it to export manual forecast submissions and related data—such as pipeline and quota—for a specified forecast and time period. The endpoint returns a job identifier that can be polled with the Get Job Status endpoint and retrieved with the Download Export Results endpoint once the job completes.
Enter the ID of the forecast to export in the Forecast ID field. This is the only required parameter and identifies the forecast whose data will be exported.
Enter the time period to include in the Time Period field (for example, a fiscal quarter such as 2026_Q2) to scope the export to a specific reporting period.
Enter a comma-separated list of data types to include in the Types to Export field, such as forecast,pipeline,quota.
Enter a Scope ID to filter the export to a specific organizational scope, hierarchy, or team.
Enter the Currency to use for numeric values in the export. This defaults to USD.
Enter a Schedule value if the export should run on a recurring or automated basis.
Set Include Historical to true to include historical data in the export, or leave it as false to export only current data.
Select the output format for the exported file from the Export Format field. Available values are JSON, CSV, and Excel, with JSON selected by default.
Forecast exports are processed asynchronously. After creating the export, use the Get Job Status endpoint to monitor progress, then use the Download Export Results endpoint to retrieve the completed data.
Create Activity Export
This endpoint creates and submits a new activity data export job for a specified date range. Use it to export sales activity records—such as calls, emails, and meetings—captured in Clari.
Enter a comma-separated list of activity types to include in the Activity Types field, such as call,email,meeting. Leave this field empty to include all activity types.
Enter the beginning date for the export period in the Start Date field using YYYY-MM-DD format. This field defaults to the macro {now-30}, which resolves to 30 days before the current date.
Enter the ending date for the export period in the End Date field using YYYY-MM-DD format. This field defaults to the macro {now}, which resolves to the current date.
Select the output format for the exported file from the Export Format field. Available values are JSON, CSV, and Excel, with JSON selected by default.
The {now} and {now-30} macros are dynamic datetime placeholders that Nexla resolves at run time, making it easy to maintain a rolling export window across scheduled ingestion runs.
Get Job Status
This endpoint retrieves the current status of an export job by its ID. Use it to determine whether a forecast or activity export job is still processing, has completed, or has failed before attempting to download its results.
Enter the ID of the export job to check in the Job ID field. This is the job identifier returned when the export was created.
Job IDs are returned by the Create Forecast Export and Create Activity Export endpoints. You can also retrieve all of your export jobs and their IDs using the List Export Jobs endpoint.
Download Export Results
This endpoint downloads the results of a completed export job. Use it once an export job's status indicates that it has finished processing to ingest the exported forecast or activity data into Nexla.
Enter the ID of the export job whose results you want to download in the Job ID field.
Confirm that the export job has completed using the Get Job Status endpoint before downloading results, as results are not available until processing finishes.
List Export Jobs
This endpoint lists all export jobs initiated by the current user. Use it to review existing export jobs, retrieve their job IDs, and monitor the overall state of your exports.
This endpoint requires no additional configuration beyond selecting the endpoint template. Nexla reads each job from the jobs array in the response and treats it as an individual record.
Use this endpoint to discover the job IDs needed by the Get Job Status, Download Export Results, and Update Job endpoints.
Update Job
This endpoint stops or cancels an export job that is currently in progress. Use it to halt a running export—for example, if it was configured incorrectly or is no longer needed.
Enter the ID of the export job to stop or cancel in the Job ID field.
Select the action to perform from the Action Type field. Available values are Stop and Cancel.
The Stop and Cancel actions terminate an in-progress export job. Retrieve the job ID using the List Export Jobs endpoint if it is not already known.
Get Opportunity
This endpoint fetches opportunity data from Clari, with optional filtering by opportunity ID and mode. Use it to ingest opportunity records for pipeline analysis, reporting, or syncing into a data warehouse.
Enter an Opportunity ID to filter results to a specific opportunity. Leave this field empty to retrieve opportunities more broadly.
Enter a Mode value to control how opportunity data is retrieved (for example, forecast or actual).
Nexla reads each opportunity from the opportunities array in the response and treats it as an individual record.
List Audit Events
This endpoint retrieves a paginated list of audit events with optional filtering. Use it to ingest a record of administrative and user activity within your Clari organization. Nexla automatically handles offset-based pagination to retrieve all matching events.
Enter an Actor ID to filter events by the ID of the user who initiated the action.
Enter an Impersonating Actor ID to filter events by the ID of the user being impersonated.
Enter a Session ID to filter events by a specific session.
Enter a Session Type to filter events by the type of session.
Enter the Date From value to set the inclusive start date for the events. This field defaults to the macro {now-30}, which resolves to 30 days before the current date.
Enter the Date To value to set the inclusive end date for the events. This field defaults to the macro {now}, which resolves to the current date.
Enter an Event value to filter by a specific event type.
The Clari audit events endpoint typically returns data for the past 30 days only, which aligns with the default {now-30} start date. Nexla reads each event from the events array in the response.
Export Audit Events
This endpoint creates an asynchronous job to export audit events filtered by specified criteria. Use it when you need a larger or more durable export of audit activity than the synchronous List Audit Events endpoint provides. The endpoint returns a job that can be monitored and downloaded using the job endpoints.
Enter an Actor ID to filter events by the ID of the user who initiated the action.
Enter an Impersonating Actor ID to filter events by the ID of the user being impersonated.
Enter a Session ID to filter events by a specific session.
Enter a Session Type to filter events by the type of session.
Enter the Date From value to set the inclusive start date for the export. This field defaults to the macro {now-30}.
Enter the Date To value to set the inclusive end date for the export. This field defaults to the macro {now}.
Enter an Event value to filter by a specific event type.
Because this export is asynchronous, use the Get Job Status endpoint to monitor the job and the Download Export Results endpoint to retrieve the exported audit events once processing completes.
Get Ingest Job Status
This endpoint retrieves the status of a data ingestion job by job ID. Use it to monitor the progress of entity data that has been uploaded to Clari through the Ingest Bulk Entities or Upload Entity Data destination endpoints.
Enter the ID of the ingestion job to check in the Job ID field. This is the job identifier returned when the ingest job was created.
Ingest job IDs are produced by the Clari ingest endpoints. This endpoint is commonly used to confirm that an entity upload completed successfully before continuing downstream processing.
Get Picklist Values
This endpoint retrieves picklist or multi-picklist field values for a specified entity. Use it to discover the valid values for a field before ingesting entity data, ensuring that the values you send conform to the entity's schema.
Select the entity type whose picklist values you want to retrieve from the Entity Type field. Available values are Account, Contact, and Opportunity.
Enter a comma-separated list of field names in the Field Names field to retrieve picklist values for specific fields. Leave this field empty to retrieve values across applicable fields.
Use this endpoint together with the Add Picklist Values endpoint to manage the allowed values for picklist fields in your Clari entity schema.
Add Picklist Values
This endpoint adds new picklist or multi-picklist field values to an entity schema. Use it to extend the set of allowed values for a field before ingesting entity data that relies on those values.
Select the entity type to which values will be added from the Entity Type field. Available values are Account, Contact, and Opportunity.
Enter the name of the picklist field to add values to in the Field Name field.
Select the field type from the Field Type field. Available values are Picklist and Multi-Picklist.
Enter a comma-separated array of values to add in the Values field, such as "Open","Closed","Pending".
The Entity Type, Field Name, Field Type, and Values fields are all required for this endpoint. Use the Get Picklist Values endpoint to review existing values before adding new ones.
Get Limits
This endpoint retrieves API and export limit information for your organization. Use it to review the quotas and rate limits that apply to your Clari account, which can help you plan export and ingest activity accordingly.
This endpoint requires no additional configuration beyond selecting the endpoint template.
This endpoint is the same one Nexla uses to validate your Clari Revenue credential, so a successful credential test confirms that the endpoint is reachable.
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.
Clari Revenue data sources can also be manually configured to ingest data from any valid Clari API endpoint — including endpoints not covered by the pre-built templates, such as chained API calls or 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.
The Clari API base URL is https://api.clari.com/v1, and endpoint paths are appended after it — for example, https://api.clari.com/v1/opportunity.
Clari list responses wrap records in a top-level key alongside pagination and metadata: enter $.events[*] as the path to data for the audit events endpoints, or $.opportunities[*] for the opportunity endpoint. Nexla reads the jobs array for the List Export Jobs endpoint.
Date/time macros such as {now} and {now-30} are useful for the dateFrom and dateTo parameters accepted by the audit and activity endpoints, making it easy to maintain a rolling ingestion window across scheduled runs.
You do not need to include the Authorization header in Request Headers — the bearer token configured in your Clari Revenue credential is applied automatically to each request.
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 Revenue 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.
Click the + icon on the Nexset that will be sent to the Clari Revenue destination, and select the Send to Destination option from the menu. Select the Clari Revenue connector from the list of available destination connectors, then select the credential that will be used to connect to the Clari Revenue organization, and click Next; or, create a new Clari Revenue credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Clari Revenue endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Ingest Bulk Entities
This endpoint uploads bulk entity data—such as accounts, contacts, opportunities, or activities—into Clari for ingestion. Use it to push revenue-critical data from Nexla into the Clari platform in batches. Each record in the Nexset is sent to Clari as JSON.
Select the type of entity being uploaded from the Entity Type field. Available values are Account, Contact, Opportunity, and Activity. This field is required.
Select the ingestion mode from the Mode field. Available values are Replace, Merge, and Upsert, with Upsert selected by default. Upsert inserts new records and updates existing ones, merge combines incoming data with existing records, and replace overwrites existing data.
Set Is Last Batch to indicate whether this is the final batch in a multi-batch upload. This field defaults to true. Set it to false for intermediate batches when uploading data across multiple calls.
After uploading entity data, use the Get Ingest Job Status endpoint on the data source page to confirm that the ingestion job completed successfully.
Upload Entity Data
This endpoint uploads incremental entity data in batches for ingestion into Clari. Use it to send ongoing, incremental updates for an entity type rather than performing a full bulk load. Each record in the Nexset is sent to Clari as JSON.
Select the entity type being uploaded from the Entity Type field. Available values are Account, Contact, Opportunity, and Activity. This field is required.
Select the ingestion mode from the Mode field. Available values are Incremental and Full, with Incremental selected by default. Incremental mode applies only the changes in the upload, while full mode treats the upload as a complete data set.
Set Is Last Batch to indicate whether this is the final batch in the upload sequence. This field defaults to true. Set it to false for intermediate batches when uploading data across multiple calls.
Use the Get Ingest Job Status endpoint on the data source page to monitor the progress of the ingestion job created by this endpoint.
Clari Revenue destinations can also be manually configured to send data to any valid Clari API endpoint. 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, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Clari's ingest endpoints expect JSON — select JSON as the content format so Nexla automatically serializes each Nexset record to the request body Clari expects. The Clari ingest endpoints use the POST method exclusively.
An entity ingest endpoint URL follows the pattern https://api.clari.com/v1/ingest/entity/account?mode=incremental&isLastBatch=true, where the entity type, mode, and last-batch flag are supplied as path and query parameters.
You do not need to include the Authorization header — the bearer token configured in your Clari Revenue credential is applied automatically to each request.
Record batching is useful for the Clari ingest endpoints, which are designed to accept multiple entity records per call; the default batch size is 100. Enabling the response webhook option lets you capture the ingest job ID that Clari returns, which can then be checked with the Get Ingest Job Status endpoint.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to Clari, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Clari until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
