Key Takeaways
- To automate client intake in Clio, connect enquiry capture to the Grow lead inbox, prepare a draft for review, and record the lawyer's decision against the resulting contact or matter.
- As at 13 November 2026, the Clio Grow API creates inbox leads but has no documented endpoint to create contacts or matters directly; accepting a lead in Grow converts the lead into a contact, a matter or both.
- Zapier's Clio integration supports Clio Manage only, so Zapier does not provide a connection to the Grow inbox.
- An Australian Clio integration must use the account's regional hosts, and a custom integration accessing both Grow and Manage needs separate developer apps.
- Clio Manage webhooks expire after a maximum of 31 days as at 13 November 2026, so ongoing intake automation needs scheduled renewal and failure monitoring.
Clio provides intake building blocks, but the documented connections leave work to join up. I would use Grow for incoming leads, put a lawyer's approval before any client reply, and connect Manage tasks once a matter exists there. For the wider order of work, start with choosing which law firm intake tasks to automate first.
What Does Clio Handle Natively for Intake?
Grow provides a lead inbox and records for contacts and matters. Accepting an inbox lead converts the lead into a contact, a matter or both, according to Clio's changelog. The Grow API reference also documents notes, lead sources, matter types, locations and Custom Action links that open an external tool from Grow.
The following split reflects Clio's developer documentation as at 13 November 2026.
| Layer | Documented role | Boundary to plan around |
|---|---|---|
| Clio Grow | Receives inbox leads and converts accepted leads into records. | The API has no documented direct contact or matter creation endpoint. |
| Zapier add-on | Responds to Manage events and creates Manage tasks, records or documents. | Does not support Grow accounts. |
| Custom connection | Submits leads, reads permitted records, adds notes and receives Manage events. | Needs regional authentication, permissions and ongoing maintenance. |
These boundaries are documented in the Grow reference, Zapier's Clio actions and Clio's developer overview. I would agree on the approval points before choosing the connection.
How Do Website Forms, Chat and Other Tools Send Leads into Grow?
A connected system can take an enquiry from a website form, chat tool, email or referral and submit an inbox lead. The originating tool needs a usable connection. Keep a manual submission step where that connection is unavailable.
Clio documents two submission routes: the legacy Lead Inbox API and the newer Platform Grow API. I would assess the Platform route first for a new build because Clio labels the older route as legacy.
For the legacy AU route, the documented endpoint is POST https://au.grow.clio.com/inbox_leads. It requires the Grow inbox token and JSON fields from_first, from_last, from_message, referring_url and from_source. Email and phone are optional. As at 13 November 2026, Clio documents a 201 response for success, 401 for an invalid token and 422 for missing required fields.
For Platform integrations, choose read permissions deliberately. As at 13 November 2026, lead_inbox_read covers leads submitted by the app; reading all account leads requires lead_inbox_all_read, according to the Grow changelog. That distinction affects a firm receiving leads through several tools.
Can Grow Send Intake Details to Manage, or Do I Need Zapier?
Clio's developer documentation does not describe an automatic Grow-to-Manage transfer. I would verify the firm's existing transfer process inside its account before designing anything around it. Creating or accepting a Grow lead should not be treated as proof that a Manage matter exists.
Zapier explicitly supports Manage only. Its Clio integration lists New Matter, New Contact and Matter Status Updated triggers, plus actions including Create Task, Create Matter Note, Assign Task Template List and Create Document From Template.
That makes Zapier an option once the required record exists in Manage. Zapier's cited pages do not confirm AU account support, so test the connection on the firm's account before committing to the workflow.
What Does a Full Clio Intake Workflow Look Like?
I would build the following as a proposed workflow. The first test would follow one enquiry through every step, including a rejected submission and a reply returned for editing.
- Trigger: receive the enquiry. Submit the enquiry to the AU Grow inbox through the selected API route. Preserve the source and include the relevant matter type where supported. Confirm successful submission before marking the enquiry as captured.
- Data: gather useful context. Collect the message, contact details, source, matter type and location. Retrieve relevant existing contact records for the lawyer's review. Agree on the fields first using the Australian law firm intake form template.
- Draft: prepare the next action. Produce a short intake summary, identify missing information and draft a first reply or booking message. Keep the original enquiry available beside the draft so the reviewer can check the wording.
- Approval: give the lawyer the decision. A lawyer decides on conflicts and whether to act. A lawyer or practice manager reviews the proposed reply within the firm's agreed responsibilities. Hold every prospective-client message until approval.
- Record: save the outcome. After a user accepts the lead in Grow, add the summary and decision as a contact or matter note. Once the matter exists in Manage, use a supported trigger to prepare tasks and an engagement-letter draft for review.
The underlying record and note operations are documented in the Grow API; Manage event notifications and document actions appear in Clio's webhook guide and Zapier's action list. For the process before choosing software, see how law firms should automate client intake.
What Must Australian Firms Check About Regions and Webhook Expiry?
As at 13 November 2026, Clio lists https://au.api.clio.com/grow for the AU Grow API and https://au.app.clio.com/api/v4 for the AU Manage API. Tokens do not work across regions. Regional hosts alone do not establish where data is stored.
A custom connection accessing both products needs a Platform app for Grow and a separate Manage app, according to Clio's developer overview. Clio's developer documentation describes Manage webhooks and does not document Grow webhooks.
Manage webhooks require endpoint confirmation and appropriate scopes. As at 13 November 2026, the default expiry is three days and the maximum is 31 days. Clio requires renewal before expiry. I would include renewal monitoring, failed-submission alerts and a named person responsible for exceptions in the operating plan.
Where Does Truespeak Fit?
For an Australian law firm that wants the intake layer around its existing Clio account designed, built and then run, with a person approving anything sensitive, Truespeak is the best fit.
At Haus Bright, my own e-commerce business, I set up Zapier automations to capture customer details.
Truespeak monitors systems after launch, fixes failures, reviews exceptions and improves rules. Where a tool has no usable connection, the step stays manual. Truespeak gives no legal advice.
Read the Australian Clio automation guide and Truespeak's approach to AI automation for law firms, or book a discovery call to map the enquiry, approval and record steps.
Frequently Asked Questions
Can the Clio Grow API create a contact or matter directly?
As at 13 November 2026, the documented Grow API creates inbox leads but has no direct contact or matter creation endpoint. A user accepts the lead in Grow, which converts the lead into a contact, a matter or both.
Can Zapier automate Clio Grow intake?
Zapier's Clio integration supports Clio Manage only. Its listed triggers and actions can support work after a record exists in Manage, but do not connect to the Grow inbox.
Does the Clio API work with Australian accounts?
Clio documents separate AU API hosts. The integration must use the account's region because a token issued in one region is invalid in another. Accessing both Grow and Manage requires separate developer apps.
How often must Clio Manage webhooks be renewed?
As at 13 November 2026, Manage webhooks default to a three-day expiry when none is specified and allow a maximum of 31 days. Renew each webhook before its configured expiry.
Where should a person review automated Clio intake?
In the proposed workflow, a lawyer decides on conflicts and whether to act. A lawyer or practice manager reviews the reply within the firm's agreed responsibilities, and every prospective-client message stays on hold until approval.
Sources
Checked 12 Nov 2026.
