Mattering Automations Clio Manage integration
Connect Clio Manage to Mattering Automations: matters and contacts, time entries and timers, bills and receivables, tasks, calendar entries, notes, communications and documents as workflow steps, authorized by signing in with Clio rather than pasting a key.
The Mattering Automations Clio Manage integration puts Clio Manage API v4, pinned to version 4.0.13, on your automation canvas: read and write matters, contacts and matter contacts, record and edit time entries and expenses, start and stop the running timer, work bills through their states, read payment allocations and outstanding client balances, create and update tasks and calendar entries, write notes, log communications, and find and download documents. Sixty nodes in total, thirty five that read and twenty five that act.
The credential is an OAuth connection rather than a key you paste. You create a Developer Application in the Clio developer portal, click Connect in Mattering, and approve the connection on Clio's consent screen. Clio's authorize endpoint takes no scope parameter, so the permissions the connection holds are the ones configured on your application, per resource, as read-only or read/write. That detail matters more than it looks: once a user has authorized, their permissions are fixed even across token refreshes, so a permission added later means everyone reauthorizes.
Two things are worth knowing before you build anything, and both are easier to read now than to hit later. First, Clio returns a minimal representation by default, which for most endpoints is only the id and the etag. Every node here that returns a Clio record already carries a well chosen fields value, so Clio Manage: List Matters returns real matters rather than a page of bare ids. Second, only Clio's United States deployment is connectable through the connect flow today, because Clio requires a separate account and a separate Developer Application in every region. Both are explained in full below, and this guide ends with the complete node reference.
Before you start
- A Clio Manage account on a paid plan. Apps and integrations, including private apps, are not available on Clio's EasyStart tier, and creating a Developer Application requires access to a paid Clio account. This is a plan boundary rather than something to debug.
- A Developer Application created in the Clio developer portal, with its permissions set per resource before anyone authorizes. For the node set in this integration that means read/write on Matters, Contacts, Activities, Bills, Tasks, Calendar, Notes, Communications, Documents and Clio Payments, plus read on Users. Clio does not review private Clio Manage apps, so there is no wait at this step.
- A Clio account in the United States region. Clio runs four independent deployments, and a token issued in one is not valid against another, so region belongs to the credential. Clio also requires a separate Clio account and Developer Application per region, so firms on the EU, Canadian or Australian deployments need sibling OAuth providers that do not exist yet.
- A decision about which Clio user holds the connection. Every node runs as that user and inherits their role and visibility settings rather than the firm's full access, and unattended automations keep running on it, so a user the firm controls beats an individual's personal login.
- An awareness of what this data is. Matters, notes, communications and documents in Clio are frequently protected by attorney-client privilege, so treat the outputs of these nodes as privileged material and select the fields a workflow needs rather than forwarding whole records into chat, a spreadsheet or an AI step.
- Clio Payments enabled on the firm, if you intend to use Clio Manage: List Clio Payments, Clio Manage: List Payment Links or Clio Manage: Create Payment Link. A firm that takes payment by cheque or bank transfer records it as an allocation instead, which Clio Manage: List Payment Allocations reads.
- A Mattering workspace with access to the Automations app.
Create a Clio Developer Application
Mattering authenticates to Clio with OAuth 2.0, so there is no API key to copy and no credential form to fill in. What you create in Clio is an application, and the decision that carries weight is its permissions, because Clio does not ask for scopes at sign-in time. The permissions on the application are the permissions every consent screen shows and every issued token keeps, and Clio fixes them at authorization even across refreshes. Get them right before anyone connects.
Connect Clio Manage to Mattering
Verify it works
Open any automation canvas and check the palette: a Clio Manage section should list the read and action nodes. Drop Clio Manage: Who Am I onto the canvas and run a test step. It is the integration's natural probe, because it takes no parameters and answers the question that matters before any write: which Clio user this connection acts as. Every node inherits that user's role and visibility settings rather than the firm's full access, so if a later read returns fewer records than you expect, this is where the explanation usually starts.
Now run Clio Manage: List Matters without changing anything. The point of this step is what comes back: real matters with display numbers, clients, practice areas and open dates, rather than a page of objects carrying only an id and an etag. That is the node's default fields value doing its job. If you had called Clio directly without a fields parameter, the bare version is exactly what you would have got, at HTTP 200 with no error to explain it. Note the status filter's trap while you are here: passing a status of open excludes pending and closed matters, while leaving the filter empty returns all three.
Open the Matter picker on a node such as Clio Manage: List Activities and confirm it populates with display numbers and client names rather than raw integers. The pickers are fed by the same default fields values, so a working picker is a second confirmation that the connection and the defaults are both fine. Everything in this verify path is read-only, so it cannot reach any of the delete nodes and is safe to re-run whenever you want to check the connection.
Node reference
60 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 35
Clio Manage: Download Document
clio_manage_download_document
Get a download URL for a document's file. Clio answers this endpoint with a 303 See Other pointing at a short-lived signed URL rather than streaming the bytes, so this node deliberately does NOT follow the redirect: it returns the URL at data.download_url for a following HTTP node, a worker, or a file-handling step to fetch. Two things that follow from that: the URL grants access to a privileged document to anyone holding it, so do not persist it or send it anywhere the document itself should not go; and it expires, so fetch it promptly rather than storing it for later.
Clio Manage: Get Activity
clio_manage_get_activity
Fetch one time entry or expense in full, including which bill it landed on and which billing code it used. Money and hours on time entries are subject to two firm settings. With Billing Rate Visibility set to Own or None, price and total are removed and redacted is set to true. With Activity Hours Visibility restricted, quantity, rounded_quantity, quantity_in_hours, rounded_quantity_in_hours, total and non_billable_total come back NULL and quantity_redacted is set to true. Summing a page that contains redacted rows produces a number that is wrong and looks right, so filter on those flags before aggregating.
Clio Manage: Get Bill
clio_manage_get_bill
Fetch one invoice in full, including its totals, tax, the matters it covers, and available_state_transitions - the list of states Clio will actually accept next, which is what you should read before trying to approve or void a bill rather than guessing.
Clio Manage: Get Calendar Entry
clio_manage_get_calendar_entry
Fetch one calendar entry in full, including attendees, recurrence rule and any linked video meeting. Field visibility on calendar entries is restricted to the event's owners, editors and viewers (API version 4.0.12), so a user outside that set sees a reduced record rather than an error.
Clio Manage: Get Contact
clio_manage_get_contact
Fetch one contact in full, including every email address, phone number and postal address rather than only the primary of each, plus custom field values. The default fields value here is deliberately wide because a single-record read costs one request against a 50-per-minute budget either way.
Clio Manage: Get Document
clio_manage_get_document
Fetch one document's metadata in full, including its latest version, who created it and which matter it is filed on. Metadata only - the file itself comes from Clio Manage: Download Document.
Clio Manage: Get Matter
clio_manage_get_matter
Fetch one matter in full: client, practice area, stage, the three attorney roles, billing configuration and custom field values. Use this when the fields value you want would be too wide to run across the whole firm. Clio strips rather than refuses: a record the caller may not fully see comes back with the forbidden fields removed and redacted set to true, at HTTP 200. Check for redacted before trusting a field is absent.
Clio Manage: Get Note
clio_manage_get_note
Fetch one note in full, including its body and whether it is plain text or rich text. Privileged content: see the notes list node.
Clio Manage: Get Running Timer
clio_manage_get_timer
Read the timer currently running for the authorising user, with its start time, elapsed seconds and the activity it is attached to. Clio runs at most ONE timer per user, so this is a singleton endpoint with no id. Returns 404 when no timer is running, which is a normal answer rather than an error.
Clio Manage: Get Task
clio_manage_get_task
Fetch one task in full, including its description body, its assignee, and the time entries recorded against it.
Clio Manage: List Activities
clio_manage_list_activities
List time entries and expenses. This is the firm's revenue record: filter by matter, by timekeeper, by date range, and by billing status to answer questions like what is unbilled on this matter or how much did this attorney record last month. quantity is in SECONDS for time entries (changed in API version 4.0.4 - it used to be hours), and in units for expense entries. quantity_in_hours carries the hours form. Money and hours on time entries are subject to two firm settings. With Billing Rate Visibility set to Own or None, price and total are removed and redacted is set to true. With Activity Hours Visibility restricted, quantity, rounded_quantity, quantity_in_hours, rounded_quantity_in_hours, total and non_billable_total come back NULL and quantity_redacted is set to true. Summing a page that contains redacted rows produces a number that is wrong and looks right, so filter on those flags before aggregating.
Clio Manage: List Activity Descriptions
clio_manage_list_activity_descriptions
List the firm's billing codes: the reusable activity descriptions that pre-fill a time entry's narrative and rate, including UTBMS task and activity codes for firms that bill insurers. This is the source for the billing-code picker on the activity nodes.
Clio Manage: List Bill Line Items
clio_manage_list_line_items
List the individual lines that make up an invoice, with each line's description, quantity, price, tax and total. This is how a workflow reconstructs a bill in detail - for a client-facing statement, a spreadsheet export, or a reconciliation against the activities that produced it.
Clio Manage: List Billable Matters
clio_manage_list_billable_matters
Work in progress: matters with unbilled hours and unbilled value, plus how much of the client's money is sitting in trust against each. This is the pre-billing worklist - run it at month end to find the matters that are ready to invoice. Clio computes the figures, so this is one request rather than a walk over every activity.
Clio Manage: List Bills
clio_manage_list_bills
List invoices with their totals, what has been paid, and what is still outstanding. balance is the amount still owed, which makes state plus balance the pair an accounts-receivable workflow runs on: state=awaiting_payment with overdue_only is the collections list. This is the source for every bill picker in this connector.
Clio Manage: List Calendar Entries
clio_manage_list_calendar_entries
List calendar events in a time range: hearings, meetings, deadlines. The from and to filters are the pair to use - from matches events ENDING on or after it and to matches events BEGINNING on or before it, so together they catch anything overlapping the window rather than only events wholly inside it. Set expanded to get one row per occurrence of a recurring event instead of one row for the series.
Clio Manage: List Calendars
clio_manage_list_calendars
List the firm's calendars: each user's own calendar, shared firm calendars, and any ad-hoc ones. Filter on writeable to find the calendars the authorising user may actually create events on, which is what you want before wiring a create node. This is the source for the calendar picker.
Clio Manage: List Clio Payments
clio_manage_list_payments
List payments taken through Clio Payments, the card and ACH rail built into Clio, with the amount, currency, state and the bills each one was applied to. Only available to firms that have Clio Payments enabled; a firm that takes payment by cheque or bank transfer records it as an allocation instead, so read Clio Manage: List Payment Allocations for the complete picture.
Clio Manage: List Communications
clio_manage_list_communications
List the communication log: phone calls and emails recorded against a matter, with who sent and received each one. The bodies of these records ARE the privileged communications themselves, which makes this the most sensitive read on the connector - the default fields value deliberately includes subject but not body for that reason.
Clio Manage: List Contacts
clio_manage_list_contacts
List the firm's address book: clients, opposing parties, experts, vendors and everyone else, as either a Person or a Company. This is the source for every contact picker in this connector. From API version 4.0.9 contacts are also filtered and redacted by the firm's Contacts Visibility permission, so two users can legitimately get different counts from the same call. Clio strips rather than refuses: a record the caller may not fully see comes back with the forbidden fields removed and redacted set to true, at HTTP 200. Check for redacted before trusting a field is absent.
Clio Manage: List Custom Fields
clio_manage_list_custom_fields
List the firm's custom field DEFINITIONS - their names, types and whether they apply to matters or contacts. These are not the values: a field definition's id is a plain integer and is what you pass to set a value for the first time, while a stored VALUE has a composite id like text_line-55001 and is read through the custom_field_values association on a matter or a contact. Request picklist_options{id,option} on a picklist field to see the choices, because a picklist VALUE is the option's id rather than its label.
Clio Manage: List Documents
clio_manage_list_documents
List documents stored in Clio, by matter, by contact, by category or by folder. Returns METADATA only - use Clio Manage: Download Document to get a URL for the file itself. Set scope to descendants with a parent_id to walk a whole folder tree rather than one level.
Clio Manage: List Expense Categories
clio_manage_list_expense_categories
List the firm's expense categories, with the default rate and whether each is a hard cost (money the firm actually paid out) or a soft cost (an internal charge such as photocopying). This is the source for the expense-category picker on the activity nodes.
Clio Manage: List Matter Contacts
clio_manage_list_matter_contacts
List every contact attached to one matter - the client plus each related contact - with the RELATIONSHIP each one has to the matter (opposing counsel, expert, insurer, and whatever else the firm has defined). This is the node that answers who is involved in a case, which the plain contacts list cannot.
Clio Manage: List Matter Stages
clio_manage_list_matter_stages
List the workflow stages a firm has defined. Stages are the firm's own steps (intake, discovery, and so on) and are tied to a PRACTICE AREA, so filter by practice area to get the stages valid for a given matter. Stages are not the same thing as a matter's status, which is the fixed open/pending/closed lifecycle.
Clio Manage: List Matters
clio_manage_list_matters
List the firm's matters (cases/files), with the client, practice area, responsible attorney, stage and open/close dates for each. This is the node most Clio workflows start from, and it is the source for every matter picker in this connector. Note the status filter's trap: passing status=open EXCLUDES pending and closed, while omitting it returns all three. Clio strips rather than refuses: a record the caller may not fully see comes back with the forbidden fields removed and redacted set to true, at HTTP 200. Check for redacted before trusting a field is absent.
Clio Manage: List Notes
clio_manage_list_notes
List notes on matters or contacts. A note in Clio is attorney work product as often as not, so treat every field of this output as privileged - and be deliberate about where a workflow sends it. Clio requires the type parameter on this endpoint (Matter or Contact); the node defaults it to Matter.
Clio Manage: List Outstanding Client Balances
clio_manage_list_outstanding_client_balances
The firm's accounts-receivable list, computed by Clio: one row per client with the total still outstanding, any pending payments, when they last paid, and when their oldest unpaid bill fell due. Prefer this over summing bills yourself - Clio does the arithmetic across every invoice, credit and write-off, and it is one request instead of a page-by-page walk against a 50-per-minute rate limit.
Clio Manage: List Payment Allocations
clio_manage_list_allocations
List how money has been applied to bills. An allocation is one payment, credit note or write-off landing on one invoice, with its date, amount and payment type. This is the node that answers what has actually been paid and when - Clio Manage v4 has no separate payments index, so allocations are how payment history is read. voided_at is set when an allocation has been reversed, so filter it out before adding anything up.
Clio Manage: List Payment Links
clio_manage_list_payment_links
List the firm's Clio Payments links: shareable URLs a client can pay through. Each row carries the live payment URL, so treat the output as sensitive even though it is not a credential - anyone with the link can open the payment page for that client's bill.
Clio Manage: List Practice Areas
clio_manage_list_practice_areas
List the firm's practice areas - the categories it organises work into, such as family, corporate or immigration. Matter stages hang off a practice area, so this is the first step in the practice area to stage chain, and it is the source for every practice-area picker here.
Clio Manage: List Task Types
clio_manage_list_task_types
List the task types a firm has defined - its own categories for work such as court filing or client follow-up. This is the source for the task-type picker on the task nodes.
Clio Manage: List Tasks
clio_manage_list_tasks
List tasks, filtered by matter, assignee, status, priority or due date. Two filters worth knowing: statute_of_limitations isolates the deadline tasks a firm cannot afford to miss, and permission distinguishes private tasks from ones the whole firm can see. This is the source for every task picker in this connector.
Clio Manage: List Users
clio_manage_list_users
List the firm's users: attorneys and staff who work in Clio, as distinct from Contacts, who are the people the firm works FOR and against. Every attorney field on a matter references one of these. This is the source for the user pickers throughout this connector.
Clio Manage: Who Am I
clio_manage_who_am_i
Return the firm user the stored credential belongs to. This is the cheapest authenticated call on the whole API and it is what this connector's auth test probes, so run it first when anything looks wrong: a 200 proves the token, the region and the header wiring all at once, and a 401 tells you one of them is off. It also answers the question that matters before any write - every action on this connector runs AS this user and inherits their role and visibility settings, not the firm's full access.
Action nodes 25
Clio Manage: Create Activity
clio_manage_create_activity
Record a time entry or an expense against a matter. quantity is in SECONDS for time entries (changed in API version 4.0.4 - it used to be hours), and in units for expense entries. quantity_in_hours carries the hours form. total is CALCULATED by Clio from quantity and price, which is why the default fields value asks for it back - you get the computed amount in the same call instead of a second read. Reversible: an activity that has not been billed can be deleted.
Clio Manage: Create Calendar Entry
clio_manage_create_calendar_entry
Put an event on a calendar: a hearing, a client meeting, an internal deadline. Setting send_email_notification emails every attendee, including any CONTACT attendees, who are the firm's clients and opposing parties - a bulk workflow with this on sends bulk mail to people outside the firm. Reversible: the entry can be updated or deleted, though a notification already sent cannot be recalled.
Clio Manage: Create Contact
clio_manage_create_contact
Add a person or a company to the firm's address book. For a Person set first_name and last_name; for a Company set name. This is the first step before opening a matter, because a matter's client must be an existing contact. Note that Clio returns 422 Unprocessable Entity when a contact exceeds the association limits introduced in API version 4.0.13.
Clio Manage: Create Matter
clio_manage_create_matter
Open a new matter for a client. The client must already exist as a contact - create it first with Clio Manage: Create Contact. Clio assigns the display number from the firm's numbering scheme unless one is supplied. Classed reversible because a matter created by mistake can be deleted, but read Clio Manage: Delete Matter before relying on that: the delete does not reverse.
Clio Manage: Create Note
clio_manage_create_note
Add a note to a matter or a contact. This is the natural landing place for automated summaries - a call transcript, an AI-drafted summary of an email thread, a status update from another system - because it puts the record where the firm already looks. Set type to match the association you fill in: a Matter note wants a matter, a Contact note wants a contact.
Clio Manage: Create Payment Link
clio_manage_create_payment_link
Create a Clio Payments link a client can pay through. Requires the firm to have Clio Payments enabled and a destination account configured. This is a MONEY-FACING write: the response carries a live URL that will take a real card or bank payment, so treat the node's output as sensitive and be careful about where a workflow sends it. Classed reversible because a link can be deactivated, but a payment already taken through one cannot be un-taken from here.
Clio Manage: Create Task
clio_manage_create_task
Create a task, optionally on a matter and optionally assigned to someone. Setting notify_assignee sends a real notification to a real person, so a workflow that loops over matters sends one email per iteration - think about that before scheduling it. Reversible: the task can be deleted or completed.
Clio Manage: Delete Activity
clio_manage_delete_activity
PERMANENTLY DELETE a time entry or expense. Clio documents no undelete for activities, so the record and its narrative are gone: this is the firm's evidence that work was done, which matters if the bill it supports is ever challenged or audited. The reversible alternative is Clio Manage: Update Activity with non_billable set to true, which keeps the record and takes it off the invoice. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.
Clio Manage: Delete Calendar Entry
clio_manage_delete_calendar_entry
PERMANENTLY DELETE a calendar entry. Clio documents no undelete for calendar entries. On a legal calendar this is the sharpest of the deletes: a hearing date or a court-rules deadline that disappears takes the firm's only reminder with it, and nothing in the API records that it ever existed. Deleting an entry with external attendees does not necessarily withdraw the invitation they already received. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.
Clio Manage: Delete Contact
clio_manage_delete_contact
PERMANENTLY DELETE a contact. Clio documents no undelete and no trash state for contacts, so unlike a Document this cannot be recovered through the API. A contact who is a client on a matter, a bill recipient, or a party on a communication is referenced by records the firm must retain, and Clio will normally refuse the delete rather than orphan them - expect a 422 rather than a silent cascade. There is no archive flag on contacts, so the usual safe alternative is to leave the record in place. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.
Clio Manage: Delete Document
clio_manage_delete_document
Move a document to the trash. This is the ONE delete on this connector that Clio documents as recoverable: the document goes to the trash rather than being purged, and is permanently deleted only after 30 DAYS. Within that window it is still readable through Clio Manage: List Documents with include_deleted set, and restorable from Clio's own UI. Classed Destructive so the endpoint test matrix skips it - running it would trash a real firm's document - but NOT flagged destructive, because the 30-day trash is a genuine undo and saying otherwise would make the flag meaningless. Returns 409 Conflict if the document or an ancestor folder is being modified by another request. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.
Clio Manage: Delete Matter
clio_manage_delete_matter
PERMANENTLY DELETE a matter. Clio documents no undelete for matters: the API has no restore endpoint and no trash state for them, unlike Documents, which Clio explicitly trashes for 30 days first. A matter is the firm's record of a client engagement and is usually under a professional or statutory retention obligation, so deleting one can be a compliance event as well as data loss. The reversible alternative is Clio Manage: Update Matter with status set to closed, which hides the matter from active views and keeps everything attached to it. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.
Clio Manage: Delete Note
clio_manage_delete_note
PERMANENTLY DELETE a note. Clio documents no undelete for notes and keeps no version history, so the text is unrecoverable. A note is frequently attorney work product and part of the file the firm is obliged to retain, so deleting one can be a records-retention problem as well as data loss. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.
Clio Manage: Delete Or Void Bill
clio_manage_delete_bill
Delete or VOID an invoice. Clio chooses which, from the bill's current state: Draft becomes Deleted, Pending Approval becomes Deleted, and Unpaid becomes VOID. A bill can only be deleted or voided when it has NO PAYMENTS RECORDED and is in one of those three states; anything else is refused with a 403. Classed destructive even though the row survives (it stays readable at state=deleted or state=void), because Clio documents no transition back out of either state: voiding an issued invoice is an accounting event, not an edit, and the only way to bill that work again is to raise a new invoice. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.
Clio Manage: Delete Task
clio_manage_delete_task
PERMANENTLY DELETE a task. Clio documents no undelete for tasks. The sharp edge here is the statute-of-limitations flag: deleting a task carrying a real limitation deadline removes the firm's reminder of a date it cannot miss, with no trace that it existed. Completing the task instead (Clio Manage: Update Task, status complete) keeps the record and is reversible. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.
Clio Manage: Log Communication
clio_manage_log_communication
Record a phone call or an email against a matter, so it lands in the firm's communication log. This is the write half of the log: point a phone system, a shared mailbox or a chat channel at it and the matter's file stays complete without anybody retyping. It does NOT send anything - Clio records that a communication happened, it does not place the call or deliver the email.
Clio Manage: Start Timer
clio_manage_start_timer
Start the authorising user's timer on an existing activity. Clio allows ONE running timer per user, so starting a second one is an error rather than a queue. To create the activity and start timing in a single call, use Clio Manage: Create Activity with start_timer set instead. Reversible: stop the timer.
Clio Manage: Stop Timer
clio_manage_stop_timer
Stop the authorising user's running timer and commit the elapsed time onto the activity it was attached to. This is a DELETE by HTTP verb but it is not a destructive one: it ends the timer, not the time entry, and the activity survives with its quantity updated. The activity can then be edited or deleted separately. Takes no parameters - Clio runs one timer per user. Deletes return 204 No Content with an empty body, and the fields parameter does not apply to them.
Clio Manage: Update Activity
clio_manage_update_activity
Edit a time entry or expense: fix the duration, rewrite the narrative, change the rate, or mark it non-billable. quantity is in SECONDS for time entries (changed in API version 4.0.4 - it used to be hours), and in units for expense entries. quantity_in_hours carries the hours form. Two failure modes worth knowing: an entry that is already on a bill may be refused, and a user whose Activity Hours Visibility is restricted gets a 403 when trying to change quantity or user on an entry whose hours are redacted for them.
Clio Manage: Update Bill
clio_manage_update_bill
Edit an invoice, or move it through the billing workflow by setting state (draft to awaiting_approval to awaiting_payment to paid). Read available_state_transitions on the bill first: Clio only accepts the transitions it lists, and a rejected one is a 422 rather than a no-op. Two of the transitions are one-way and are covered by Clio Manage: Delete Bill instead. Classed reversible because ordinary edits and forward transitions are; setting state to void or deleted through this node is NOT, so use the delete node, which says so.
Clio Manage: Update Calendar Entry
clio_manage_update_calendar_entry
Reschedule or edit a calendar entry. On a recurring series this edits the series; Clio's _deleted parameter (single or future) is the mechanism for scoping a change to one occurrence, and it is reachable through extra_body. Setting send_email_notification re-notifies every attendee.
Clio Manage: Update Contact
clio_manage_update_contact
Change a contact's details or write custom field values. Only the fields you fill in are sent. Careful with the collection fields: email_addresses, phone_numbers and addresses are nested-attribute collections, so an entry WITHOUT an id is added, an entry WITH an id is updated, and an entry with an id plus "_destroy": true is removed. Sending a bare list of new values does not replace the existing ones, it appends to them.
Clio Manage: Update Matter
clio_manage_update_matter
Change a matter: move it to a new stage, close it, reassign the responsible attorney, or write custom field values. Only the fields you fill in are sent, so this is a genuine partial update. Setting status to closed deletes nothing and is undone by setting it back to open.
Clio Manage: Update Note
clio_manage_update_note
Edit a note's subject, body or date. Clio keeps no version history on notes, so an edit REPLACES the previous text with no way to read what was there before - which, on a record that may be work product, is worth knowing before automating it.
Clio Manage: Update Task
clio_manage_update_task
Change a task: complete it, reassign it, move its due date, or raise its priority. Setting status to complete is the normal way to close a task and is fully reversible - set it back to pending. Only the fields you fill in are sent.
Using the integration
The fields parameter, and why it is on every read node
This is the single most important thing about the Clio Manage API, and the integration solves it rather than passing it on. Clio's own documentation states that a request without the fields parameter returns a minimal set of default fields, and that for most endpoints id and etag are the only ones returned. So a bare call to the matters endpoint answers HTTP 200 with a page of objects that carry nothing you can use, and there is no error message to lead you to the cause. Every one of the 50 nodes here that returns a Clio record carries fields as a configured value with an authored default chosen for that resource, which is why Clio Manage: List Matters returns matters and Clio Manage: List Bills returns invoices with their balances the moment you drop them on the canvas. The same defaults feed the pickers, which is why a matter field offers display numbers rather than integers. Widen the value whenever a workflow needs more. Three rules when you do: the format is comma separated with no spaces, an association can be expanded with a brace list such as matter{id,display_number}, and nesting goes one level only, so a second level such as matter{client{name}} is refused with a 400 and needs a separate read against the contacts endpoint instead. A field name Clio does not recognise is also a 400, so a typo fails loudly rather than quietly disappearing. The parameter works on creates and updates too, which is how Clio Manage: Create Activity returns the total Clio computed from quantity and price without a second request.
Privileged data, and the defaults that protect it
A matter description is often the legal theory of a case, a note is often attorney work product, and a communication body is the privileged communication itself. Because the caller chooses which fields come back, the integration uses that control deliberately: Clio Manage: List Communications defaults to returning the subject and not the body, Clio Manage: List Calendar Entries leaves out the attendee list, which names clients and opposing parties, Clio Manage: List Users leaves out billing rates, and the Clio Payments nodes leave out payer email addresses. Every one of those is available and documented as available on its node. None is returned unless you ask for it. Build the same habit into your workflows: select the fields a step actually needs rather than forwarding a whole Clio object into a chat window, a spreadsheet or an AI step, because privilege can be waived by disclosure and no redaction afterwards undoes that. Two related behaviours are worth knowing. Clio redacts rather than refusing, returning a record with the forbidden parts stripped and a redacted flag set, at HTTP 200, so an absent field is not proof of an empty field. And the connector blanks any conference_password or shared_secret it sees in a response on every node, because a calendar entry on a legal matter can carry the password to a client meeting and Clio can add new fields to every API version at any time.
One region per credential, and why that is United States today
Clio runs four independent regional deployments, in the United States, the European Union, Canada and Australia, on different hosts, and states that a token issued in one region is not valid against another region's API. Region is therefore a property of the credential rather than something a node can select. Clio goes further: it requires a separate Clio account and a separate Developer Application in each region, with a different application id per region. That is why only the United States deployment is connectable through Connect today. Serving an EU, Canadian or Australian firm means registering sibling OAuth providers backed by Clio accounts and applications in those regions, and those do not exist yet. We are not putting a date on it, and we would rather state the limit here than have you discover it at the consent screen. The runner refuses an unrecognised region value outright rather than coercing it, because silently sending a European firm's token to a United States host produces a 401 that reads exactly like a bad credential.
Rate limits, and building workflows that fit inside them
Clio documents 50 requests per minute per access token at peak hours, with a higher off-peak allowance that varies by region, and states that it does not grant custom increases. The limit is per token rather than per application, every response carries the remaining count and a reset timestamp, and a 429 carries a retry delay. This shapes Clio workflow design more than anything else in this guide. Fetch wide rather than looping: one call to Clio Manage: List Matters with the fields you need beats that call followed by one Clio Manage: Get Matter per row, and a list-then-fetch-each pattern over a mid-sized firm exhausts the budget in under a minute. Where Clio has already done the arithmetic, let it: Clio Manage: List Outstanding Client Balances computes the receivables position across every invoice, credit and write-off in one request, and Clio Manage: List Billable Matters computes unbilled hours and value per matter without walking the activity history. Index calls return up to 200 records per page and this integration deliberately does not auto-paginate, so each node is one request and an unbounded number of calls never hides behind a single canvas step. Following the next page link from a response is a decision you make rather than one the node makes for you.
Recorded time, and the redaction that makes totals wrong
Clio Manage: List Activities is the firm's revenue record, filterable by matter, timekeeper, date range and billing status. Two things about it break arithmetic if you do not know them. Quantity is in seconds for time entries, changed in Clio API version 4.0.4 from hours, and in units for expense entries, with quantity_in_hours carrying the hours form. Sending 1.5 for an hour and a half records 1.5 seconds and Clio accepts it without complaint. And Clio redacts per row according to two firm settings: with Billing Rate Visibility set to Own or None, price and total are removed and a redacted flag is set; with Activity Hours Visibility restricted, quantity, rounded_quantity, quantity_in_hours, rounded_quantity_in_hours, total and non_billable_total come back null and a quantity_redacted flag is set. Both arrive at HTTP 200. A sum over a page containing redacted rows is silently low and looks right, so filter on those flags before aggregating anything. Clio Manage: Start Timer and Clio Manage: Stop Timer work on the authorizing user's single running timer, since Clio allows one per user, and Clio Manage: Get Running Timer returns 404 when none is running, which is a normal answer rather than a failure.
Three kinds of delete, and which is which
The eight delete nodes are not one thing and the integration does not flatten them. Clio Manage: Delete Document is the mild one: Clio moves the file to the trash rather than purging it, permanently deletes it only after 30 days, and it stays readable through Clio Manage: List Documents with deleted records included in the meantime, so this is a genuine undo. Clio Manage: Delete Or Void Bill is not really a delete at all: Clio transitions a Draft or Pending Approval bill to Deleted and an Unpaid bill to Void, chooses which from the bill's current state, and refuses with a 403 unless the bill has no payments recorded against it. The row survives and stays readable, but Clio documents no transition back out of either state, so voiding an issued invoice is an accounting event rather than an edit and the only way to bill that work again is a new invoice. Read available_state_transitions on the bill with Clio Manage: Get Bill before touching it. The remaining six are permanent: Clio Manage: Delete Matter, Clio Manage: Delete Contact, Clio Manage: Delete Activity, Clio Manage: Delete Task, Clio Manage: Delete Calendar Entry and Clio Manage: Delete Note have no trash state and no restore endpoint documented anywhere in Clio's API description. Each names its reversible alternative on the node, and the alternative is usually what was wanted: Clio Manage: Update Matter with a status of closed, Clio Manage: Update Task with a status of complete, Clio Manage: Update Activity marked non-billable. Deleting a task carrying a statute of limitations date is the sharpest of them, because it removes the firm's only reminder of a deadline it cannot miss and leaves no trace it existed.
On the automation canvas
Clio nodes chain with every other node in Mattering. A form submission can run Clio Manage: Create Contact and then Clio Manage: Create Matter, since a matter's client must be an existing contact, with Clio Manage: List Practice Areas and Clio Manage: List Matter Stages supplying a stage that is valid for the practice area, because stages hang off a practice area rather than floating free. A phone system or shared mailbox can call Clio Manage: Log Communication so the matter's file stays complete without retyping, remembering that the node records that a communication happened rather than sending anything. A monthly schedule can read Clio Manage: List Billable Matters into a Mattering database and open a Productivity task for a person to review. The pickers do most of the wiring for you: sixteen fields exist purely to scope a picker by matter, so choosing a matter narrows the activity, task, note, calendar and document pickers to that file rather than offering the firm's entire history, and those fields are never sent to Clio.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter, the assistant built into the platform, can drive the same surface. Clio publishes no MCP server of its own, so there is no vendor alternative to weigh here: its developer documentation covers the Clio Manage API, the Clio Platform, webhooks, SSO and the App Directory process, and does not mention MCP anywhere. Given what is in a Clio account, the sensible split is to hand an assistant the 35 read nodes and keep the writes behind conditions or approval steps, especially the seven flagged destructive. An agent reading Clio Manage: List Tasks and Clio Manage: List Calendar Entries to build a deadline digest is low risk; an agent holding Clio Manage: Delete Matter is not. The advantage of running Clio here rather than in a local assistant config is that the same nodes are canvas steps, so the workflow an agent helps you design then runs on a schedule with nobody present, chains with every other connector, and holds the credential once in a shared workspace rather than in each person's machine.
Notes, communications and documents
Clio Manage: Create Note is the natural landing place for an automated summary, a call transcript or a status update from another system, because it puts the record where the firm already looks. Clio requires a type on notes, either Matter or Contact, and the node defaults it to Matter, so set the association that matches. Be careful with Clio Manage: Update Note: Clio keeps no version history on notes, so an edit replaces the previous text with no way to read what was there, which on a record that may be work product is worth a second thought before automating. On the document side, Clio Manage: List Documents and Clio Manage: Get Document return metadata only. Clio Manage: Download Document is the node that reaches the file, and it deliberately does not follow Clio's redirect: it returns the short-lived signed URL at data.download_url for a following HTTP node, a worker or a file-handling step to fetch. That URL grants access to a privileged document to anyone holding it, so do not persist it or send it anywhere the document itself should not go, and fetch it promptly because it expires. Document upload is not built here: creating a document in Clio is a multi-step file transfer rather than a single call.
Editing contacts without duplicating everything
Clio Manage: Update Contact has one behaviour that surprises people, and it is Clio's design rather than the integration's. Email addresses, phone numbers and postal addresses are nested-attribute collections, which means they append rather than replace. Sending a bare list of email addresses adds them alongside the ones already on the record, producing duplicates. To change an existing entry, send it with its id. To remove one, send its id together with a _destroy value of true. Clio Manage: Get Contact returns every email address, phone number and postal address rather than only the primary of each, which is where those ids come from. Custom fields have their own two-shape trap worth reading Clio Manage: List Custom Fields for: a field definition's id is a plain integer, which is what you pass to set a value for the first time, while a stored value's id is a composite string such as text_line-55001, which is what you pass to update an existing value. Picklist, matter and contact field types store an id as their value rather than a label.
Troubleshooting
A list node returns rows that contain only an id and an etag
The fields value is rejected with a 400
Test Connection fails with a 401
A node fails with a 403 while other nodes work
Requests start failing partway through a run with a 429
A matter list is missing matters that definitely exist
A total calculated from time entries is lower than the figure Clio shows
Updating a contact created duplicate email addresses or phone numbers
A picker on a node stays empty
The connection cannot be created at all, or a Clio account has no API access
Related
The Clio Manage MCP
What connecting Clio Manage unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Clio Manage is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.