Skip to main content

Clari Revenue Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Clari Revenue location.
clari_api.png

Clari Revenue

Create a Clari Revenue Destination​

  1. 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.

  2. 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.

  3. In Nexla, Clari Revenue destinations can be created using pre-built endpoint templates, which expedite destination setup for common Clari Revenue endpoints. Each template is designed specifically for the corresponding Clari Revenue endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Clari Revenue destinations can also be configured manually, allowing you to send data to Clari Revenue endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Clari Revenue endpoints. Each template is designed specifically for the corresponding Clari Revenue endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, 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.

Configure Manually​

Clari Revenue destinations can be manually configured to send data to any valid Clari API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Clari API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Clari API from the Method pulldown menu. The Clari ingest endpoints use the POST method.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Clari API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. Clari's ingest endpoints expect JSON.

API Endpoint URL​

  1. Enter the URL of the Clari API endpoint to which you want to send the Nexset data in the URL field. For example, an entity ingest endpoint 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.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include any headers already present in the credentials. The Authorization bearer token configured in your Clari Revenue credential is applied automatically to each request.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Clari Revenue destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching. Batching is useful for the Clari ingest endpoints, which are designed to accept multiple entity records per call.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the Clari API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call, such as the ingest job ID.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

    Capturing the API response is especially useful with the Clari ingest endpoints, as the returned ingest job ID can be passed to the Get Ingest Job Status endpoint to confirm that the upload completed successfully.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Clari API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Clari API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Clari API using the current settings.

Save & Activate the Destination​

  • 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.