Caddi does not ship a standard Clio connector — every firm registers its own OAuth app inside its own Clio account. That keeps your IT team in control of which permissions Caddi holds and lets you revoke access at any time. This guide walks through creating the app in Clio, then connecting it to Caddi.
Clio is region-specific. Your app must be registered in the same region your firm signs in to, and credentials issued in one region will not work in another.
US app.clio.com · EU eu.app.clio.com · Canada ca.app.clio.com · Australia au.app.clio.com
Before you start
You'll need:
A Clio Manage account with access to Settings → Developer Applications (firm administrator)
Owner or Admin access to your Caddi organization
To know which Clio region your firm is on — check the domain you sign in to
You do not need Clio's approval to build or run a private app. Clio review is only required to list an app publicly in the Clio App Directory, which does not apply here.
Step 1: Create the OAuth app in Clio
Sign in to Clio as an administrator, in the region your firm uses.
Click the gear icon in the upper right, then open Developer Applications. You can also go directly to
https://app.clio.com/settings/developer_applications(substitute your region's domain).Click Add.
Fill in the application details:
Name —
Caddi. This is shown to your users on the Clio consent screen.Website URL —
https://trycaddi.comRedirect URIs —
https://app.trycaddi.com/oauth-callbackApp Permissions — see the guidance below
Accept Clio's Developer Terms of Service and save.
Copy the generated Key and Secret. The Key is your Client ID and the Secret is your Client Secret.
Clio treats Redirect URIs as a strict allowlist, so the value must match https://app.trycaddi.com/oauth-callback exactly — same protocol, domain, and path.
Step 2: Choose app permissions
Clio controls access with App Permissions checkboxes on the app itself rather than scope strings sent at sign-in time. Caddi's recommendation is to enable read and write on the record types your loops will touch — typically matters, contacts, documents, activities, calendars, and tasks — and to leave any user- or firm-administration permissions off.
Clio tokens are user-delegated: the access Caddi ends up with is the overlap between the permissions you check here and the Clio role of whoever connects their account. A paralegal connecting their own Clio account gives Caddi a paralegal's reach, not an administrator's.
On the app you just created, review the App Permissions section.
Enable the read and write permissions for each resource your loops need.
Leave administration permissions disabled unless a specific loop requires them.
Save.
Step 3: Configure Clio in Caddi
This step must be completed by a Caddi organization owner or admin.
In Caddi, open Integrations in the left sidebar, then click the Integration Setup tab at the top of the page. This tab is only visible to organization owners and admins.
Find Clio in the list and click Configure.
Enter the following values:
Client ID — the Key value from your Clio developer application
Client Secret — the Secret value from the same application
OAuth Scopes — leave blank to inherit Caddi's defaults. Clio governs access through App Permissions on the app itself, so there is normally nothing to enter here.
Click Save Configuration. Caddi validates the credentials immediately — if something is wrong you'll see an error right away, and nothing is stored until validation passes.
Step 4: Connect your account
Go back to the My Connections tab at the top of the Integrations page.
Find Clio and click Connect +.
Sign in to Clio and click Allow on the consent screen.
You'll be returned to Caddi with a confirmation, and Clio will appear under Connected Applications.
How the connection behaves
Each user connects their own Clio account. Caddi acts on behalf of the authenticated user and sees only what that user can see in Clio. Clio's audit history attributes actions to that user.
A custom connection replaces the standard one. Once configured, members of your organization only see the option to connect through your app.
Access tokens last 30 days and refresh tokens do not expire, so connections stay live without users re-authorizing. Revoking the app in Clio, or deleting the developer application, cuts Caddi off immediately.
Clio rate-limits API traffic to roughly 50 requests per minute during business hours, with higher allowances off-peak and no option to request an increase. Very high-volume loops may pace themselves against this.
Troubleshooting
redirect_uri_mismatch or an invalid redirect error at sign-in
The Redirect URIs field on the Clio app does not match https://app.trycaddi.com/oauth-callback exactly. Check for a trailing slash, http instead of https, or a typo in the path.
The connection succeeds but loops can't see matters or documents
Either the app's App Permissions don't include that resource, or the Clio user who connected doesn't have access to it. Check the app's permissions first, then the user's Clio role.
invalid_client when connecting
The Key/Secret pair is from a different Clio region than the one your firm signs in to. Register the app in the correct region and re-enter the credentials.
Loops intermittently fail with rate-limit errors
Clio's per-minute limit is being hit. Space out scheduled runs, or move high-volume loops to off-peak hours.
Still stuck? Contact Caddi support with the exact error message you're seeing and the time it occurred.
Automation ideas
Law Firms
Matter intake → Clio matter + folder structure
When a new client form arrives, Caddi creates the contact and matter in Clio, sets the practice area and responsible attorney, and provisions the matching document folder structure in your DMS — so the file is ready before anyone opens it.
Meeting or call → time entry
Caddi reads the meeting duration and participants from Zoom or your calendar, drafts a billing narrative, and creates the time entry against the right Clio matter and activity code.
Signed document → matter update
When a DocuSign envelope completes, Caddi files the executed copy against the Clio matter, logs the activity, and closes out the related task.
Deadline → calendar and task chain
Caddi reads a court date or filing deadline, calculates the dependent dates, and creates the full chain of Clio calendar entries and tasks for the responsible team.