A8gent
Build guide - Clio Grow

Clio Grow intake follow-up: building it on the API

The Clio Grow API documents no webhooks, so intake follow-up means polling. Here are the endpoints, permissions, rate limit and a three-touch sequence.

A8gent

What you get from this guide

  • What Clio already offers for intake follow-up, so you do not build a duplicate
  • The two Clio Grow APIs and why the legacy one is not enough
  • The fact that shapes the whole build: no documented webhooks, so you poll
  • Permissions, token lifetime and the rate limit, from Clio's developer docs
  • A three-touch sequence that stops the moment a person at the firm takes over

What Clio offers first

A potential client fills in your form on a Tuesday evening. The firm that replies first, clearly and politely, usually gets the consultation. Intake follow-up exists to make that reply, and the two or three after it, happen without relying on someone remembering.

Clio has moved into this space itself. Its client acquisition page describes Grow AI as responding to new inquiries, sending the right intake form with reminders until it comes back complete, and following up unsigned agreements. Clio says you pay when Grow AI helps turn a lead into a hired client, with a monthly cap you can set. Clio Grow also has automated workflow features documented in its help centre.

Check before you build

Look at what your Clio Grow subscription already includes and price Grow AI for your volume. If the native tools cover your follow-up, use them. This guide is for firms that want their own wording, their own channels, a fixed cost, or steps that reach beyond Clio.

Two APIs, and which to use

Clio documents two ways into Clio Grow, and they do very different things.

The two Clio Grow integration routes
RouteWhat it doesUse it for
Lead Inbox endpoint (legacy)A POST to grow.clio.com/inbox_leads with a lead capture token. Creates a lead. Nothing else.Pushing leads in from a web form or phone service
Grow API on the Clio PlatformOAuth 2.0. Reads inbox leads, matters and contacts, and writes notes.Follow-up, because you need to read state

Clio's Lead Inbox guide says plainly that it documents a legacy approach and points to the Clio Platform for the fuller API. It requires from_first, from_last, from_message, referring_url and from_source, returns 201 on success, 401 for an invalid token and 422 when required fields are missing. It is still handy for getting leads into Clio, but it cannot tell you what happened to them.

The Grow API reference lists the endpoints follow-up needs: GET /inbox_leads, GET /matters, GET /contacts, and POST /matters/{matter_id}/notes. The US base URL is https://api.clio.com/grow, with eu., au. and ca. prefixes for other regions.

Access is by OAuth. The permissions page names the Grow scopes, including grow_lead_inbox_read, grow_lead_inbox_all_read, grow_matter_read, grow_matter_note_write and grow_contact_read, and advises choosing the smallest set that works. It also notes that once a user has authorised your application their permissions are fixed, so adding a scope later means authorising again. The authorisation guide shows a sample token response with expires_in of 86400 seconds and a refresh token.

No webhooks: you poll

The Grow API reference documents no webhooks. This single fact decides the architecture. You cannot be told when a lead arrives; you have to ask.

Polling is fine here. Clio's rate limits page gives a default of 3 requests per second, applied per OAuth application across all users, with a 429 response when you exceed it. A poll every five minutes is two or three requests. The trade-off is delay: a lead can wait up to five minutes before the workflow sees it, which is acceptable for a follow-up sequence and one reason to keep an instant on-page confirmation on the form itself.

Two fields make polling workable. Inbox leads carry a state, which the reference filters as untriaged or ignored, plus converted_to_matter. Matters carry status, status_category, first_appointment_created_at and hired_date. Between them you can tell a lead nobody has touched from one the firm is already working.

The intake follow-up sequence

Three administrative touches, then a person
TouchTimingJob of the message
1Within minutes of the lead appearingAcknowledge the enquiry and give the booking link
2Next working day, if no appointmentShort reminder that the firm is ready to talk, link again
3Day 4Close out politely and say how to get in touch later
ThenDay 5Task for the intake lead: call or close

Three is deliberate. A person looking for a lawyer is often under stress, and repeated automated contact from a firm they have not hired reads badly. After three, a human decides.

The build

Written for n8n with a Schedule trigger and the HTTP Request node. There is nothing here that Make cannot also do.

1

Create the developer application

Create an application on the Clio Platform developer portal. Select the read permissions for the lead inbox, matters and contacts, and the matter note write permission. Request the all-read lead inbox permission if leads arrive from sources other than your own application.

2

Authorise and store tokens

Run the authorisation code flow as a firm user with access to Grow. Store both tokens in your automation platform's credential store, not in a sheet, and let it refresh the access token.

3

Poll for leads and matters

Every five minutes, list untriaged inbox leads and recent matters, and compare the ids with those already in your table.

Poll - new leads

GET https://api.clio.com/grow/inbox_leads?state=untriaged
Authorization: Bearer <access token>

For each lead id not already stored:
  first_name, last_name, email, phone_number,
  matter_type, created_at, converted_to_matter
4

Write the follow-up record

One row per lead: lead id, matter id once it exists, contact details, matter type, status = open, step = 0, next_touch = now. Skip any lead without an email address or phone number and flag it for a person instead.

5

Check for the stop on every poll

For each open record with a matter id, read the matter. If first_appointment_created_at or hired_date is set, or the status has changed, set the record to stopped. Do the same on any inbound reply, and give intake staff a manual stop.

6

Send the due touch

Re-read the record status, apply business hours in the firm's timezone, send the approved template for the step and advance the record. No model writes these messages. They are fixed text with a name and a link.

7

Write a note to the matter

After each send, POST /matters/{matter_id}/notes with what was sent and when. The firm then sees the automation's activity inside Clio Grow, next to everything else on the matter.

8

Hand over

After touch three, close the record and create a task for the intake lead. Report weekly on leads received, touches sent and consultations booked.

Message copy

Touch 1 - email, within minutes

Subject: We have received your enquiry

Hi {first_name},

Thank you for contacting {firm_name}. We have received
your enquiry and a member of our team will be in touch.

If you would like to choose a time for an initial
consultation now, you can do so here: {booking_link}

Please do not send confidential details or documents
by reply until we have confirmed we can assist you.

{firm_name}
{phone}

Touch 3 - email, day 4

Subject: Your enquiry to {firm_name}

Hi {first_name},

We have not been able to reach you, so we will not
contact you again about this enquiry.

If you would still like to speak with us, you can book
a time here: {booking_link} or call {phone}.

{firm_name}

Note what is absent: any comment on the matter, any suggestion the firm is acting, any urgency about legal deadlines. Those belong in a conversation with a lawyer.

Rules for law firms

  • Templates are approved by the responsible lawyer before they go live, and changed only with approval.
  • No legal advice, no view on merits, and no wording that implies an engagement, in any automated message.
  • Conflict checks happen before anyone at the firm discusses substance. The automation only schedules.
  • Keep message content minimal. Do not repeat what the person wrote about their situation back to them by email or text.
  • Advertising and solicitation rules differ by jurisdiction. Check yours before adding texts or repeated contact.
  • Texting in the US needs consent and A2P 10DLC registration for the sending number.

The registration step is covered in the A2P 10DLC guide.

Testing and measuring it

Test against a developer account, not the firm's live data. Clio's developer documentation describes signing up for a free developer account on the Clio Platform developer portal for building on Clio Grow.

  1. Create a lead with your own email address and confirm the poll picks it up once, within one polling interval.
  2. Let the poll run several more times and confirm the same lead does not create a second record or a second message.
  3. Book an appointment on the test matter and confirm the next poll stops the record before touch two.
  4. Create a lead with no email and no phone number and confirm it is flagged for a person, not dropped.
  5. Revoke and re-authorise the application, and confirm the workflow recovers with fresh tokens.
  6. Confirm each send writes a note to the matter, and read the note as intake staff would. It should say what was sent and when, in plain words.
  7. Force a 429 by looping requests and confirm the workflow backs off.

Before go-live, have the responsible lawyer read every template once more in the form the recipient will see it, on a phone. Then run for two weeks with touch one only. An immediate acknowledgement is the lowest-risk message and the one with the clearest benefit. Add touches two and three once the firm is comfortable with how the first behaves.

Measure four numbers monthly: enquiries received, enquiries acknowledged within ten minutes, consultations booked, and enquiries that reached the day-five task with no contact. The second number should be close to the first. The fourth is the one to watch. A long list of leads nobody reached is a sign that the firm needs more intake capacity or a tighter form, and no sequence fixes that.

Review access as well as results. The application holds permission to read the firm's leads, matters and contacts. Keep the permission set as small as the workflow needs, store tokens only in the automation platform's credential store, restrict who can open the workflow, and remove the application's access in Clio if the workflow is ever retired. For a law firm, that discipline is part of the build, not an extra.

Where these builds go wrong

  • Building on the legacy Lead Inbox endpoint and discovering it cannot read anything back.
  • Requesting the narrower lead inbox read permission and seeing only the leads your own app created.
  • Waiting for a webhook that the Grow API does not document.
  • Forgetting that adding a permission later needs the user to authorise again.
  • No stop on a booked appointment, so a person with a consultation tomorrow gets a reminder to book one.
  • Letting a language model draft messages to potential clients.
  • Never writing notes back, so intake staff do not know what the lead was told.
  • Polling every few seconds for no benefit and running into the rate limit.

If consultations are booked through a scheduling link, the Calendly no-show follow-up guide covers what happens when the person books and does not attend. The law firms page sets out which workflows to build in which order, and what an automation build costs covers pricing.

Sources checked

FAQ

Does Clio Grow have an API?
Yes. Clio documents a Grow API on the Clio Platform, with a US base URL of https://api.clio.com/grow and regional equivalents for the EU, Australia and Canada. The reference lists endpoints for inbox leads, matters, contacts, notes, matter types, sources, locations, marketing campaigns, custom actions and users. There is also an older Lead Inbox endpoint that only creates leads, which Clio's own guide labels a legacy approach.
Does the Clio Grow API have webhooks?
None are documented in the Grow API reference as of November 2026. That means a follow-up workflow has to poll: call the list endpoints on a schedule and work out what is new or changed. With a documented default rate limit of 3 requests per second per OAuth application, polling every few minutes is comfortably within bounds.
Can I read every lead in the Lead Inbox through the API?
It depends on the permission. Clio's permissions page lists grow_lead_inbox_read and a separate grow_lead_inbox_all_read. The API changelog records that the plain read permission was narrowed to return only leads your own application submitted, so a workflow that needs to see leads from web forms and other sources has to request the all-read permission. Check the changelog before you build, because this changed recently.
Can the API send emails or texts from Clio Grow?
The Grow API reference does not list an endpoint for sending messages. It lets you read leads, matters and contacts and write notes. So your follow-up messages go out from the firm's own email account or messaging provider, and the workflow writes a note back to the matter so the history is visible in Clio.
Is Grow AI a better answer than building this?
It may be. Clio describes Grow AI as responding to new inquiries, sending intake forms with reminders until they come back, and following up unsigned agreements, priced on leads that become hired clients with a monthly cap you set. If that covers your need and the pricing suits you, a native feature inside the tool your team already uses is hard to beat. A custom build makes sense when you want your own wording and channels, fixed costs, or steps that reach outside Clio.
How do I stop the sequence once the lead engages?
Read the matter on each poll. The matter record includes a status, a status category, a first appointment created timestamp and a hired date. Any of those changing means a person at the firm is now dealing with the lead, so the automation stops. Add inbound replies and a manual stop on top.
Is it safe to automate messages to potential clients?
It is safe when the messages are administrative and nothing else: we received your enquiry, here is how to book, here is the form. An automated message must never give legal advice, comment on the merits of a matter or imply that the firm has agreed to act. Rules on client communication and advertising vary by jurisdiction, so have the responsible lawyer approve every template before it goes live.
What does it cost to have this built?
The polling and state logic are modest. The work is in the OAuth setup, the permission review, template approval and the write-back. We quote a fixed price in writing per scoped workflow after a free consult, and the automation build cost page explains what drives it.

Done for you

Want every enquiry acknowledged and followed up, with the history in Clio?

We build intake follow-up on the Clio Grow API for firms that want their own wording and a fixed cost: the polling, the stop rules, approved templates and notes written back to the matter. The audit that scopes it is free.

The consult is free, and you keep whatever we build.

Keep building

The rest of the cluster