Clio Custom Actions Setup

What You’re Setting Up

Custom Actions are menu items that you add to Clio’s user interface. When a user clicks one, Clio sends data about the current record to a URL you specify — our webhook endpoint. This is how we add things like a “Run Conflict Check” button directly inside Clio.

Instead of switching to a separate tool or manually entering data, your staff clicks a button in Clio and the integration handles the rest.

Prerequisites

• A Clio developer account with a registered application (set that up first)
• API authentication already configured (Clio API Authentication)
• The webhook URL we provide for the custom action

How Custom Actions Work

A Custom Action adds a clickable menu item to a specific record type in Clio (contacts, matters, etc.). When clicked:

1. Clio collects data about the current record (ID, name, and other context)
2. Clio sends that data to the URL you’ve configured
3. Our endpoint receives the data and triggers the appropriate action (conflict check, document generation, etc.)
4. Results can be displayed back to the user or logged in Clio

Step-by-Step Setup

1. Open Custom Actions in the Developer Portal

1. Log into the Clio developer portal
2. Navigate to your registered application
3. Find the Custom Actions configuration section

2. Create a New Custom Action

1. Click to add a new Custom Action
2. Configure the following:
   • Label: What the user sees in Clio’s menu, like “Run Conflict Check”
   • Target URL: The webhook URL we provide
   • Type/Context: Which record type this action appears on — typically Contacts or Matters for conflict checks

3. Configure the Data Payload

Clio Custom Actions include parameters about the record when they call your URL. At minimum, the action sends:

• The record ID of the contact or matter
• The record type

Depending on configuration, additional fields may be available. We’ll specify what we need for your particular workflow.

4. Set Visibility

You may be able to control which users in your firm see the Custom Action. If only certain team members should run conflict checks, configure the visibility accordingly.

5. Test the Action

1. Open a contact or matter in Clio
2. Look for the Custom Action in the actions menu or toolbar area
3. Click it and verify that our endpoint receives the request

We’ll confirm on our end that the data came through correctly.

Example: Run Conflict Check

Here’s how this plays out in practice for a conflict check workflow:

1. A staff member opens a new matter in Clio
2. They click “Run Conflict Check” from the Custom Actions menu
3. Clio sends the matter details to our endpoint
4. Our middleware searches across your CRM, prior matters, and adverse party lists
5. Results are returned — either displayed in a new window or logged as a note on the matter

The whole process takes seconds instead of manual cross-referencing.

Common Issues

Custom Action Not Appearing

If the action doesn’t show up in Clio’s interface, check that: the app is properly authorized with the Clio account, the Custom Action is saved and active in the developer portal, and you’re looking at the correct record type (contacts vs. matters).

“Unauthorized” When Clicked

If clicking the action results in an error, the webhook URL may be unreachable or the authentication between Clio and our endpoint needs to be re-verified. Contact us to troubleshoot.

Action Appears on Wrong Record Type

If the conflict check button shows up on calendar entries instead of matters, the context/type was set incorrectly. Edit the Custom Action in the developer portal and update the record type.

Next Steps

• Set up Clio API authentication: Clio API Authentication
• Learn more about our Legal Conflict Check Automation