Skip to main content

Clio 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 Clio location.
clio_api.png

Clio

Create a Clio Destination​

  1. Click the + icon on the Nexset that will be sent to the Clio destination, and select the Send to Destination option from the menu.

  2. Select the Clio connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Clio account, and click Next; or, create a new Clio credential for use in this flow.

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

    Clio destinations can also be configured manually, allowing you to send data to Clio 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 Clio endpoints. Each template is designed specifically for the corresponding Clio 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.

    Create Activity

    This endpoint creates a new activity (a time entry or expense entry) in Clio. Use it to push time-tracking or expense data captured in other systems into Clio for billing.

    • Each record in the Nexset is sent as the JSON body of a POST request to the Clio activities endpoint. Map your Nexset fields so that each record contains the attributes required to create an activity (for example, the activity type, quantity, and the associated matter).
    • No additional endpoint parameters are required to configure this template.

    For the complete list of fields accepted when creating an activity, refer to the Clio API V4 Documentation.

    Update Activity

    This endpoint updates an existing activity in Clio by its unique ID. Use it to modify time or expense entries—for example, to correct a quantity or update billing status.

    • Enter the ID of the activity to update in the Activity ID field. This field is required and is used to build the request URL.
    • Each record in the Nexset is sent as the JSON body of a PATCH request containing the fields to update. Only the attributes you include are modified.

    Create Task

    This endpoint creates a new task in Clio. Use it to generate to-do items or assignments in Clio from workflows managed in other systems.

    • Each record in the Nexset is sent as the JSON body of a POST request to the Clio tasks endpoint. Map your Nexset fields so that each record contains the attributes required to create a task (for example, the task name, due date, and the associated matter).
    • No additional endpoint parameters are required to configure this template.

    Update Task

    This endpoint updates an existing task in Clio by its unique ID. Use it to modify task details—for example, to mark a task complete or change its due date.

    • Enter the ID of the task to update in the Task ID field. This field is required and is used to build the request URL.
    • Each record in the Nexset is sent as the JSON body of a PATCH request containing the fields to update. Only the attributes you include are modified.

Configure Manually​

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

Using manual configuration, you can also configure Nexla to automatically send the response received from the Clio 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 Clio API from the Method pulldown menu. Clio write operations typically use POST to create records and PATCH to update existing records.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Clio API from the Content Format pulldown menu. Clio expects JSON request bodies, so select JSON. Nexla will automatically convert the data to the selected format for each API call.

API Endpoint URL​

  1. Enter the URL of the Clio API endpoint to which you want to send the Nexset data in the URL field. Clio endpoints use the .json suffix—for example, https://app.clio.com/api/v4/tasks.json. For update operations, include the ID of the object to be updated in the path—for example, https://app.clio.com/api/v4/tasks/12345.json.

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). The Clio API uses the X-API-VERSION header to pin requests to a specific API version—for example, X-API-VERSION:4.

    You do not need to include any headers already present in the credentials.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Clio 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.

  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 Clio 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 ID of a newly created activity or task.

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

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Clio 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 Clio 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 Clio 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 send the data to the configured Clio endpoint, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to Clio until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.