Clio Manage legal practice management for United States-region accounts on app.clio.com. Manage clients, matters, calendars, tasks, time, and billing. Canada, EU, and Australia accounts require separate regional OAuth applications and hosts.
Assign one Clio task template list to a matter, creating its tasks with assignee notifications disabled. The action reads the current Matter ETag before the PATCH and does not retry a rejected write. Clio does not return guaranteed generated Task IDs or provide atomic undo; find and delete generated tasks separately if cleanup is needed. Requires Matters and Tasks access.
Create a Clio time or expense activity. Requires Clio's Activities write permission.
Create a Clio custom calendar. Requires the Calendars write permission selected on the Clio developer application.
Create a Clio calendar entry. Only internal Clio calendars can be attendees because Clio always emails contact attendees. Calendar notifications are disabled. Requires Clio's Calendars write permission.
Record a phone or email communication in Clio. This creates a communication log; it does not place a call or send an email. Notification subscribers are intentionally unsupported. Requires Communications write permission in the Clio developer application.
Create a Clio person or company, including new email addresses and phone numbers. A Company requires name; a Person requires first_name or last_name. Requires Clio's Contacts write permission.
Upload one non-sensitive file directly to Clio's documented multipart route and create a document template suitable for START_DOCUMENT_FROM_TEMPLATE or GENERATE_DOCUMENT_FROM_TEMPLATE. Requires Documents write permission.
Create only the Clio document record and signed-upload initiation. This action does not upload bytes, follow signed destinations, finalize an upload, or create a version of an existing document. Upload without Clio OAuth, then use a separate finalization operation. Requires Documents write permission.
Create a Clio matter for a client. Requires Clio's Matters write permission.
Create a subfolder inside a Clio Matter. Clio creates each Matter's root folder automatically; this action creates a child folder and always uses the supplied Matter as its parent. Requires Documents write permission.
Create a note associated with a Clio Matter. The action fixes the note type to Matter and intentionally does not support notification subscribers. Requires Notes and Matter access in the Clio developer application.
Create a Clio task-template list plus one to ten documented task templates, read it back to confirm it is non-empty, and clean up partial creation on failure. Templates are private, non-cascading, plain text, and have no reminders; this does not assign a list to a matter or notify assignees. Requires Tasks write permission.
Create a non-complete Clio task with assignee notifications disabled. To complete it safely, create it as pending and then call UPDATE_TASK with status complete. Requires Clio's Tasks write permission.
Permanently delete one Clio time or expense activity by ID. Requires Clio's Activities write permission.
Permanently delete an owned Draft or Pending Approval bill after exact ID, number, ETag, state, ownership, and confirmation checks. Clio only accepts bills without recorded payments. Unpaid bills must use Void Bill. Requires Billing write permission.
Permanently delete one manually created Clio calendar after verifying it is an owner-controlled AdhocCalendar. Built-in firm and user calendars are refused. This tool does not check whether the calendar contains entries, and Clio does not document whether deletion preserves, migrates, or deletes them. Requires Calendars write permission.
Permanently delete a non-recurring Clio calendar entry or an explicitly scoped recurring occurrence, future sequence, or series. Fails closed when Contact attendees exist because Clio would email them. Clio DELETE has no atomic ETag guard, so a concurrent attendee change after preflight remains a notification risk for non-recurring or series deletion. Requires Calendars write permission.
Permanently delete one recorded Clio communication after an exact-ID preflight and explicit confirmation. This does not notify subscribers. Requires Communications write permission.
Permanently delete one Clio contact by ID. Requires Clio's Contacts write permission.
Move a Clio document to trash after an exact ID-and-name preflight and explicit confirmation. Clio permanently deletes trashed documents after 30 days. Requires Documents write permission.
Permanently delete a Clio document template after an exact ID-and-filename preflight and explicit confirmation. Requires Documents write permission.
Move a non-root, unlocked Clio folder to trash after an exact ID-and-name preflight and explicit confirmation. Trashed folders are permanently deleted after 30 days. Requires Documents write permission.
Permanently delete one Clio matter by ID. Requires Clio's Matters write permission.
Permanently delete one Clio note after an exact-ID preflight and explicit confirmation. This does not notify subscribers. Requires Notes write permission.
Permanently delete one Clio task by ID. Requires Clio's Tasks write permission.
Permanently delete a Clio task-template list after an exact ID-and-name preflight and explicit confirmation. This does not assign tasks or send notifications. Requires Tasks write permission.
Download the latest or a specified Clio document version as a managed file. The runtime follows Clio's 303 with cross-host authorization stripping, so Clio OAuth is never sent to the signed download host. Requires Documents read permission.
Exhaustively find Clio bills by exact client, matter, bill number, and state criteria. Provide client_id, matter_id, or invoice_number; state only narrows that lookup. All supplied criteria are combined with AND; duplicate exact bills are returned as ambiguous rather than selecting one. Requires Billing read permission on the Clio developer application.
Exhaustively find exact Clio company contacts without choosing an arbitrary duplicate. Requires Contacts read permission.
Validate a Clio Contact custom field, exhaustively search its exact typed value, and report duplicate ambiguity. Requires Custom Fields read and Contacts read permissions.
Find by matter_id alone, or exhaustively search using display_number, description, or client_reference, optionally narrowed by client_id and status. All collection results are exact-filtered; multiple matches are reported as ambiguous. Requires Matters read permission.
Validate a dynamic Matter custom field, exhaustively scan all exact provider candidates, and report zero, one, or every ambiguous exact match. Requires Custom Fields and Matters read permissions.
Resolve exactly one contact by exact email, exhaust all of that client's matters, and select the greatest created_at with greatest ID as the tie-break. If any candidate lacks a valid created_at, return comparison_incomplete and do not select a newest matter. Requires Contacts and Matters read permissions.
Exhaustively preflight a Clio company identity using email or a complete custom-field ID/value pair, create only when absent, then postflight for races. Requires Contacts write and, when used, Custom Fields read permissions.
Choose either client_id or client_email, not both, plus client_reference or a complete custom-field ID/value pair. Resolve exactly one client, exhaustively find an exact matter identity, create only when absent, then repeat the exhaustive search to detect concurrent duplicates. Requires Matters write and relevant Contacts/Custom Fields access.
Exhaustively preflight a Clio person identity using email or a complete custom-field ID/value pair, create only when absent, then postflight for races. Requires Contacts write and, when used, Custom Fields read permissions.
Exhaustively find exact Clio person contacts without choosing an arbitrary duplicate. Requires Contacts read permission.
Find one Clio user using a single selector: user_id, email, or full name. enabled and include_co_counsel apply only to email or name searches. ID uses the documented single-user endpoint; email and name searches exhaust all id-ascending pages and report duplicate exact users as ambiguous. Requires Users read permission on the Clio developer application.
Create a Clio document automation, then poll its documented status endpoint within the caller's bounded interval and timeout. This creates a persistent automation and generated Documents; completed returns those documents, failed or empty returns that terminal outcome, and polling expiry returns still_pending with the automation ID and latest state so callers do not start a duplicate. Clio publishes no polling SLA. Requires Documents read/write access and access to the Matter and template.
Get one Clio time or expense activity by ID, including billing state and its user and matter references.
Get one Clio bill with its ETag, lifecycle state, permitted transitions, and concrete financial totals. Requires Billing read permission.
Get one Clio calendar by ID, including its type, permission, visibility, source, and colors. Requires the Calendars read permission selected on the Clio developer application.
Get one Clio calendar entry or expanded recurring occurrence by ID with recurrence, attendee, owner, and matter details. Requires the Calendars read permission selected on the Clio developer application.
Retrieve one recorded Clio communication. This does not send a message or notify subscribers. Requires Communications read permission.
Get one Clio person or company by its known ID, including primary and structured email and phone details. Use Search Contacts to discover an ID. Requires Contacts read permission on the Clio developer application.
Return the authenticated Clio user and role information for identity checks and default user references. Requires the Users read permission selected on the Clio developer application.
Get one Clio document and its latest-version metadata by ID. Requires Documents read permission.
Retrieve one Clio folder by ID. Requires Documents read permission.
Get one Clio matter by ID with lifecycle, client, staffing, practice area, dates, and billing method. Requires read access to Matters.
Retrieve the client contact for one Clio matter. Requires Contacts and Matters read permission.
Retrieve one Clio matter or contact note. Reading a note does not notify subscribers. Requires Notes read permission.
Get one Clio task by its known ID, including description, status, due date, priority, assignee, matter, and completion-notification state. Requires read access to Tasks in the Clio developer application.
Get one Clio firm user by ID with identity, account role, locale, time zone, and default calendar information. Requires the Users read permission selected on the Clio developer application.
List selectable Clio activity descriptions and resolved rates for time entries. Requires Activities read permission.
List visible or writable Clio calendars to resolve the owner ID for calendar entries. Requires the Calendars read permission selected on the Clio developer application.
Return one bounded page of recorded Clio email or phone communications. This reads logs and does not send messages or notify subscribers. Requires Communications read permission.
Return one bounded page of email addresses for a Clio contact. Requires Contacts read permission.
Return one bounded page of phone numbers for a Clio contact. Requires Contacts read permission.
Return one bounded page of Clio document-generation automations. Requires Documents read permission.
List Clio document templates and IDs for document automation. Requires Documents read permission; availability can depend on the Clio plan.
Return one bounded provider page of Clio documents. Requires Documents read permission.
List selectable Clio expense categories and rates for expense entries. Requires Activities read permission.
Return one bounded page of Clio documents and folders, optionally below a parent folder. Requires Documents read permission.
Return one bounded page of Clio folders using documented filters. Requires Documents read permission.
List Clio groups and IDs for matter assignments and user grouping. Requires Groups read permission.
Return one bounded page of Clio matter-contact association records, including association ID and ETag, relationship label, is_client, matter reference, and contact details. Use LIST_MATTER_RELATED_CONTACTS for the related-contact relationship view. Requires Contacts and Matters read permissions.
Return one bounded page of protected funds for a Clio matter. Requires Matters read permission.
Return one bounded page of Clio related-contact relationship records, including relationship ID, contact_id, and whether the contact is also the matter client. Use LIST_MATTER_CONTACTS for matter-contact association labels. Requires Contacts and Matters read permissions.
List Clio matter stages and practice-area associations for selecting a matter stage. Requires Matters read permission.
Return one bounded page of Clio matter or contact notes. Reading notes does not notify subscribers. Requires Notes read permission.
List Clio practice areas and IDs for matter and task-template selection. Requires Matters read permission.
List Clio task template lists and IDs for assigning templates to matters. Requires Tasks read permission.
List Clio users available for attorney, staff, task-assignee, and activity-user references. Requires the Users read permission selected on the Clio developer application.
Render one Clio bill as HTML, cap the response at 2 MB, and offload it as a file instead of returning active HTML inline. This does not change or send the bill. Requires Billing read permission.
Deprecated compatibility action. Use CREATE_ACTIVITY when activity_id is omitted and UPDATE_ACTIVITY when it is provided. Preserves the combined Clio time-or-expense create/update behavior. Requires Activities write permission.
Deprecated compatibility action. Use CREATE_CALENDAR when calendar_id is omitted and UPDATE_CALENDAR when it is provided. Preserves custom-calendar creation and ETag-safe updates. Requires Calendars write permission.
Deprecated compatibility action. Use CREATE_CALENDAR_ENTRY when calendar_entry_id is omitted and UPDATE_CALENDAR_ENTRY when it is provided. Contact attendees are unsupported because Clio always emails them, so updates fail closed when any already exist. Recurring updates require occurrence or series scope; future-series updates are unsupported. Calendar notifications are disabled. Requires Clio's Calendars write permission.
Deprecated compatibility action. Use CREATE_CONTACT when contact_id is omitted and UPDATE_CONTACT when it is provided. Person writes intentionally use first_name/last_name because live Clio rejects the OpenAPI-documented name field for Person. Nested records can be irreversibly deleted.
Deprecated compatibility action. Use CREATE_MATTER when matter_id is omitted and UPDATE_MATTER when it is provided. Preserves combined matter create/update behavior. Requires Clio's Matters write permission.
Deprecated compatibility action. Use CREATE_TASK when task_id is omitted and UPDATE_TASK when it is provided. Assignee notifications are disabled on creation and reassignment; completion notifications are disabled and verified before a complete status transition. Requires Clio's Tasks write permission.
Search and filter Clio activities, including multiple activity IDs, one page at a time. Use Get Activity for one known ID and full billing details. Requires Activities read permission in the Clio developer application.
Search Clio calendar entries by time window, text, calendar, matter, or ID, one page at a time. Requires read access to the Calendars permission in the Clio developer application.
Search and filter Clio contacts, including multiple contact IDs, one page at a time. Use Get Contact for one known ID and full contact details. Requires Contacts read permission in the Clio developer application.
Search and filter Clio matters, including multiple matter IDs, one page at a time. Use Get Matter for one known ID and full lifecycle, staffing, and billing details. Requires Matters read permission in the Clio developer application.
Search and filter Clio tasks, including multiple task IDs, one page at a time. Use Get Task for one known ID and full task details. Requires Tasks read permission in the Clio developer application.
Start Clio's asynchronous create-document-from-template generation and return the automation ID, current state, and any documents already present. This action does not wait for completion because Clio documents no polling SLA. Check GET /document_automations/{id}.json using Platform Equivalent via proxy, or a future show action, before treating the document as generated. Requires Clio Documents write access and access to the Matter and template.
Irreversibly transition a bill to paid, void, or deleted only after exact identity, ETag, expected current state, available transition, and explicit confirmation checks. Uses Clio's official PATCH bill operation and requires Billing write permission.
Update at least one field on an existing Clio time or expense activity, optionally using its ETag as a concurrency precondition. Posted or billed activities may be immutable. Requires Clio's Activities write permission.
Update ordinary bill presentation, financial, tax, discount, or interest fields using the required current ETag. Lifecycle state is deliberately excluded; use Transition Bill State for a confirmed state change. Requires Billing write permission.
Update at least one of an existing Clio calendar's name, color, source, or visibility after reading its current ETag. Requires the Calendars write permission selected on the Clio developer application.
Update at least one field on a Clio calendar entry without sending calendar notifications. Existing contact attendees cause the update to fail closed because Clio always emails them. Recurring updates require occurrence or series scope; future-series updates are unsupported. Requires Clio's Calendars write permission.
Update a recorded Clio communication using its current ETag, including explicitly confirmed irreversible deletion of external properties. Notification subscribers are intentionally unsupported. Requires Communications write permission.
Update at least one field on a Clio person or company, including adding or updating nested email and phone records. Setting destroy=true with a nested record ID irreversibly deletes that record. Requires Clio's Contacts write permission.
Update only Clio document metadata with an If-Match ETag. It cannot restore a trashed document, initialize or finalize uploads, create versions, or mutate external properties. HTTP 412 is surfaced without retry. Requires Documents write permission.
Rename, move, recategorize, or restore a Clio folder, and add, change, or explicitly and irreversibly delete external properties, using its current ETag. Requires Documents write permission.
Update at least one field on an existing Clio matter, optionally using its ETag for concurrency safety. Requires Clio's Matters write permission.
Update a Clio note using its current ETag. Notification subscribers are intentionally unsupported. Requires Notes write permission.
Update at least one field on an existing Clio task. Assignee notifications are disabled on reassignment. Completion notifications are disabled and verified before a complete status transition. Requires Clio's Tasks write permission.
Irreversibly void an Unpaid bill after exact ID, number, ETag, state, and confirmation checks. Clio only accepts bills without recorded payments. Draft and Pending Approval bills must use Delete Bill. Uses Clio's official DELETE bill operation and requires Billing write permission.
The Clio Manage (US) integration connects your Dench AI CRM directly to Clio Manage (US), so agents can read and act on your Clio Manage (US) data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
99 actions are available for agents to invoke on your behalf. Every call runs through Clio Manage (US)'s own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Clio Manage (US) and click Connect — you'll authorize access through Clio Manage (US)'s own sign-in flow. No API keys or code required.
Ask an agent to use Clio Manage (US) in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Clio Manage (US) integration connects your AI CRM to Clio Manage (US), so AI agents can work with your Clio Manage (US) data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Clio Manage (US) integration currently exposes 99 actions, including Assign Task Template List, Create Activity, Create Calendar, Create Calendar Entry, Create Communication, and Create Contact. Agents invoke them on your behalf from chat or from automations.
No. You connect Clio Manage (US) from your Dench workspace using Clio Manage (US)'s own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Clio Manage (US)'s own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Clio Manage (US) connection from your workspace settings at any time.