Features by connector
Pick a connector to see exactly what Claude can read and write — and filter by plan tier to see which capabilities are included in Solo or unlock at Team+. Every tool is a slice of real work you can hand off in plain English and review before it lands in the system of record.
The full Clio Manage workflow, hand-off-able to Claude
Cohesive360 exposes your Clio Manage tenant to Claude through 98 purpose-built tools across 12 capability areas. Matters, contacts, time, tasks, calendar, notes, documents, billing, trust accounting, secure messaging, firm admin — plus the Personal Injury add-on (medical records, damages, lien tracking) for PI practices. All in one OAuth grant, all writable as drafts you approve before they commit.
One ask instead of twelve tabs
Catching up on a matter, pulling the trust balance, logging time, drafting a bill, replying through Clio Connect — the full Clio surface collapses into plain-English requests Claude handles while you stay in the review seat.
Native OAuth — no passwords leave Clio
We connect through Clio's OAuth 2.0 flow. Your Clio password never reaches our servers; the tenant decides the scope. Revoke the OAuth grant in Clio Manage's Connected Apps panel and the connector is shut down instantly.
Writes inherit your seat's permissions
Claude acts as your Clio user. If your seat can't create a bill, draft a trust request, or edit another user's time, neither can Claude through the connector — the same role boundary Clio applies in the UI.
Plan tiers gate capability areas, not API access scope. For pricing, see the Pricing page.
Capabilities
4 workflow areas in Team plan+. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.
Draft, edit, and send invoices. Record expenses, flat fees, and client payments. Manage credit notes and review outstanding balances across the firm.
Draft, edit, and send invoices. Record expenses, flat fees, and client payments. Manage credit notes and review outstanding balances across the firm.
What you can ask Claude
- “Create a draft bill for everything unbilled on Garcia”
- “Add a $325 filing-fee expense to Smith”
- “Email this draft bill to the client”
- “Record a $5,000 payment from Johnson against their July invoice”
Underlying tools (15)
list_billsget_billcreate_billupdate_billsend_billlist_bill_line_itemslist_bill_themeslog_expense_entrylog_flat_feerecord_paymentlist_paymentslist_outstanding_balanceslist_credit_notescreate_credit_notelist_expense_categoriesView per-matter trust balances, request retainer top-ups from clients, and apply trust funds to bills as work bills out.
View per-matter trust balances, request retainer top-ups from clients, and apply trust funds to bills as work bills out.
What you can ask Claude
- “What's the trust balance on Garcia”
- “Send a $2,500 trust-replenishment request to the Lopez client”
- “Apply $1,800 from Johnson's trust to invoice #4421”
Underlying tools (5)
list_trust_line_itemslist_trust_requestscreate_trust_requestapply_trust_to_billlist_bank_accountsRead and send messages through Clio Connect — the encrypted client portal — so privileged client conversations stay inside Clio rather than ordinary email.
Read and send messages through Clio Connect — the encrypted client portal — so privileged client conversations stay inside Clio rather than ordinary email.
What you can ask Claude
- “Any new portal messages from the Garcia client”
- “Send the Lopez client a portal message asking for her updated insurance card”
Underlying tools (2)
list_secure_messagessend_secure_messageFull coverage of Clio's Personal Injury add-on: per-provider medical records and bills, treatment timeline, damages (economic, general, punitive), lien flags. Requires the firm to have purchased Clio's PI add-on (US-only paid SKU).
Full coverage of Clio's Personal Injury add-on: per-provider medical records and bills, treatment timeline, damages (economic, general, punitive), lien flags. Requires the firm to have purchased Clio's PI add-on (US-only paid SKU).
What you can ask Claude
- “Add Dr. Patel as a medical provider for this matter and request their records”
- “Log the $4,200 MRI bill from Coastal Imaging and mark the unpaid balance as a lien”
- “What's the current Damages summary on the Whitfield matter”
Underlying tools (10)
list_medical_records_detailsget_medical_records_detailcreate_medical_records_detailupdate_medical_records_detailupdate_medical_recordupdate_medical_billmark_medical_bill_as_lienlist_damagescreate_damageupdate_damageLimits and roadmap
What the Clio Manageconnector can't do today, and why. We update this when things change.
Not in the vendor's API
Capabilities the vendor handles through admin UI or internal endpoints rather than the documented public API.
- Clio Grow (intake) endpoints. The intake/CRM product (Clio Grow) is a separate platform with its own API. The Manage connector doesn't cross that boundary — for Grow workflows, use the Grow product directly or ask us to scope a Grow connector.
- Bill voiding / destructive deletes. Voiding an issued bill, deleting a payment, and permanent deletes of communications all stay in Clio Manage's UI — too dangerous for a chat-driven workflow.
- User & group administration. Adding/removing users, changing role membership, and editing groups are admin-only in Clio Manage. The connector reads the user roster but doesn't modify it.
On the roadmap
Technically possible but not yet prioritised. Email product@cohesive360.com if any of these would change your decision to roll out.
- Clio Payments processing. Recording an external payment is supported; running a card through Clio Payments is not yet wired. On the roadmap if customers ask.
- Document generation from templates. The Clio document-automation endpoints are read-only in our adapter — we list templates but don't yet trigger a merge.
- Reports and saved-search execution. Custom reports are firm-specific and need careful UX before chat exposure. Use Clio Manage's Reports tab.
Safeguards built into the connector
Defensive behaviours we put in the client because the underlying systems don't.
OAuth 2.0 grant — revocable from Clio
We connect through Clio's published OAuth flow. The grant is visible in Clio Manage → Settings → Connected Apps, where any firm admin can revoke it; the connector picks up the revocation on the next call and stops authenticating.
Encrypted refresh-token vault
We never see your Clio password — only the OAuth refresh token. That token lives in our credential vault: AES-256-GCM encrypted, master key in Azure Key Vault, ciphertext bound to your user ID, never logged in plaintext.
Per-seat permissions inherited
The connector acts as your Clio user. Your seat's role and group membership govern what's reachable — a paralegal seat can't draft bills through Claude if it can't draft bills in Clio Manage.
Rate-limit backoff
Clio's API caps each tenant at a moving daily/burst budget. The connector reads Clio's rate-limit response headers, queues requests when approaching the cap, and falls back to exponential backoff on 429 with up to three retries.
Write-with-review on money + comms
Bills, payments, trust requests, and Clio Connect messages all draft for review by default — Claude never auto-sends. You see the draft in chat; one nod commits it through the API.
What Clio Manage via Cohesive360 is not
Honest boundaries — what Claude through this connector cannot guarantee.
Cohesive360 is a facilitation channel between Claude (Anthropic) and your Clio Managetenant. Claude's responses are Anthropic's output; the underlying data is the vendor's system of record. We transport requests and responses; we do not generate, review, or validate Claude's output, and we do not operate the vendor's API.
Claude can be wrong. It can misread a record, misinterpret a date, draft against the wrong matter, or summarise incorrectly. Treat every draft as a draft — review it before you accept it, particularly anything that affects a deadline, a client communication, or a matter already in motion.
The vendor can be unavailable. The API can rate-limit, return errors, or reject requests for reasons specific to your tenant configuration. When that happens, Claude will tell you — but we have no control over when or why the vendor refuses a call.