This article may be out of date!
Visit the New Knowledge Center

Custom Actions

What are Custom Actions?

Third-party applications in Clio have the ability to create custom actions within the Clio interface. When a custom action is created, Clio firm users will see a dropdown menu item uniquely related to the third-party application for every Activity, Contact, Document, or Matter. 

Custom actions help Clio firm users reduce the time it takes to switch between applications by unlocking the potential for powerful workflows to be built between Clio and our integration partners.

How do Custom Actions work?

A label and target URL is provided for each custom action, allowing integration partners to launch their third-party application from directly within Clio. 

When a user clicks on a custom action, Clio will open a new browser tab pointing to the target URL. Clio will add a few URL parameters to the target URL, including:

  • the custom action ID;
  • the ID of the user who clicked the custom action;
  • the URL of the object(s) which the link was clicked on; and
  • a single-use code the third-party application can use to verify that the call originated from Clio

Where are Custom Actions utilized?

Custom actions are currently supported for Activities, Contacts, Documents, and Matters. Depending on which of these objects you work with, the custom action will appear only in the locations outlined below.

Activities, Contacts, and Matters (List View)

Custom actions are shown when selecting the dropdown menu beside the Edit button for each individual Activity, Contact, or Matter.


Activities, Contacts, and Matters (Singular View)

You will also see the same custom actions under the More Actions dropdown when viewing the details of a single Activity, Contact, or Matter.



In the case of Documents, custom actions can be found under the More Actions dropdown for each document.

Further reading

For additional information on how to utilize Clio’s custom actions with your third-party application, please visit our API documentation.



Was this article helpful?
This information is confusing or wrong
This isn't the information that I was looking for
I don't like this functionality