---
title: Clio Grow API Integration on Truto
slug: cliogrow
category: CRM
canonical: "https://truto.one/integrations/detail/cliogrow/"
---

# Clio Grow API Integration on Truto



**Category:** CRM  
**Status:** Beta

## MCP-ready AI tools

Truto exposes 26 tools for Clio Grow that AI agents can call directly.

- **create_a_clio_grow_contact_note** — Create a note for a contact. Creates a new note for a contact. Required: contact_id, data.
- **list_all_clio_grow_contact_notes** — List notes for a contact. Returns a paginated list of notes for a contact. Required: contact_id. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **get_single_clio_grow_contact_by_id** — Get a contact. Returns a single contact by ID. Required: id.
- **list_all_clio_grow_contacts** — List contacts. Returns a paginated list of contacts. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **list_all_clio_grow_current_users** — Get current user. Returns the currently authenticated user.
- **create_a_clio_grow_custom_action** — Create a custom action. Creates a new custom action. Required: data.
- **delete_a_clio_grow_custom_action_by_id** — Delete a custom action. Deletes a single custom action by ID. Required: id.
- **list_all_clio_grow_custom_actions** — List custom actions. Returns a paginated list of custom actions. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **create_a_clio_grow_inbox_lead** — Create an inbox lead. Creates a new inbox lead. Required: data.
- **get_single_clio_grow_inbox_lead_by_id** — Get an inbox lead. Returns a single inbox lead by ID. Required: id.
- **list_all_clio_grow_inbox_leads** — List inbox leads. Returns a paginated list of inbox leads filtered by state. Required: state. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **create_a_clio_grow_location** — Create a location. Creates a new location for the account. Required: data.
- **get_single_clio_grow_location_by_id** — Get a location. Returns a single location by ID. Required: id.
- **list_all_clio_grow_locations** — List locations. Returns a paginated list of the account's locations. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **get_single_clio_grow_marketing_campaign_by_id** — Get a marketing campaign. Returns a single marketing campaign by ID. Required: id.
- **list_all_clio_grow_marketing_campaigns** — List marketing campaigns. Returns a paginated list of the account's marketing campaigns. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **create_a_clio_grow_matter_note** — Create a matter note. Creates a new note for a matter. Required: matter_id, data.
- **list_all_clio_grow_matter_notes** — List matter notes. Returns a paginated list of notes for a matter. Required: matter_id. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **create_a_clio_grow_matter_type** — Create a matter type. Creates a new matter type for the account. Required: data.
- **get_single_clio_grow_matter_type_by_id** — Get a matter type. Returns a single matter type by ID. Required: id.
- **list_all_clio_grow_matter_types** — List matter types. Returns a paginated list of the account's matter types. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **get_single_clio_grow_matter_by_id** — Get a matter. Returns a single matter by ID. Required: id.
- **list_all_clio_grow_matters** — List matters. Returns a paginated list of matters. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **create_a_clio_grow_source** — Create a lead source. Creates a new lead source for the account. Required: data. Clio documents no OAuth scope for Sources; the app's permissions decide access.
- **list_all_clio_grow_sources** — List lead sources. Returns a paginated list of the account's lead sources. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2. Clio documents no OAuth scope for Sources; the app's permissions decide access.
- **list_all_clio_grow_users** — List users. Returns a paginated list of users in the current account. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.

## How it works

1. **Link your customer's Clio Grow account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach Clio Grow.** The Proxy API is a 1-to-1 mapping of the Clio Grow API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Push Leads Into Clio Grow's Intake Pipeline** — Marketing platforms, chatbots, web forms, and virtual receptionist services can drop prospect data directly into the Lead Inbox so law firms can triage new matters without manual data entry. Offering this integration eliminates the biggest friction point for legal customers evaluating your product.
- **Prove Marketing ROI Down to Retained Clients** — Ad analytics and marketing attribution SaaS can map campaigns and sources in Clio Grow to actual Matters that reach the Hired stage. This lets your platform report true Cost-Per-Retained-Client instead of surface-level clicks or form fills.
- **Log Calls, SMS, and Transcripts to the Right Matter** — VoIP, SMS, and virtual receptionist platforms can identify a Clio Grow contact by phone number and attach call summaries, transcripts, or recording links as Contact or Matter notes. Attorneys walk into every consultation with full context.
- **Trigger Pipeline-Stage Workflows from External Tools** — Project management, document automation, and intake automation platforms can create Custom Actions tied to a prospect's stage in Clio Grow. This keeps the firm's intake process synchronized with whatever system the team actually works in.
- **Sync Intake Data Into Downstream Legal Tools** — Document generation, e-signature, and client portal SaaS can pull Matters, Contacts, and Matter Types from Clio Grow to pre-fill engagement letters and intake packets. Your product becomes a seamless extension of the firm's intake process.

## What you can build

- **Lead Inbox Push from Any Source** — Capture prospects from your product and create them as Clio Grow Inbox Leads with full source attribution so intake teams can vet and convert them.
- **Campaign and Source Attribution Sync** — List existing Marketing Campaigns and Sources, and programmatically create new Sources so every lead entering Clio Grow carries a trackable origin tag.
- **Retained-Client ROI Dashboard** — Poll Matters to detect pipeline-stage transitions and join them against your campaign data to surface cost-per-hired-client metrics for each law firm customer.
- **Automated Call and Message Logging** — Look up Contacts by identifier, then post rich-text Contact Notes or Matter Notes containing transcripts, summaries, or recording URLs after every communication event.
- **Custom Action Triggers** — Create and delete Custom Actions on prospect files when events happen in your app, giving law firms a bespoke task layer tied to their intake pipeline.
- **Matter Type and Location Setup** — Create and read Matter Types and Locations during onboarding so your product can route new leads into the correct practice area and office automatically.

## FAQs

### How does authentication to Clio Grow work through Truto?

Truto handles the full OAuth flow with Clio Grow on your behalf. Your end users click Connect in your app, authorize access to their Clio Grow account, and Truto manages token storage and refresh so you never touch credentials.

### Can we create leads without immediately creating a Contact or Matter?

Yes. Clio Grow separates the Lead Inbox from Contacts and Matters specifically to support conflict-of-interest triage. Use create_a_clio_grow_inbox_lead to drop prospect data into the inbox, where the firm's intake team can vet and convert it on their terms.

### How do we attribute leads to specific marketing campaigns or channels?

You can list existing Marketing Campaigns and Sources via list_all_clio_grow_marketing_campaigns and list_all_clio_grow_sources, and create new Sources with create_a_clio_grow_source. Attach source context when creating Inbox Leads to maintain end-to-end attribution.

### How do we detect when a lead becomes a hired client?

Poll list_all_clio_grow_matters and inspect the matter's pipeline state. You can correlate matters back to the original lead or contact to determine which campaigns produced retained clients.

### Can we attach call recordings, SMS transcripts, or meeting notes to a prospect's file?

Yes. Use create_a_clio_grow_contact_note to log activity against a Contact or create_a_clio_grow_matter_note for a specific Matter. Both accept rich text, so you can embed summaries, transcripts, and links to external recordings.

### What Clio Grow objects can we read and write today?

Through Truto you can work with Inbox Leads, Contacts, Matters, Matter Types, Matter and Contact Notes, Marketing Campaigns, Sources, Locations, Custom Actions, and Users. Reads cover list and get-by-id operations, with create support for leads, notes, sources, matter types, locations, and custom actions.
