
Connectors / Operations · HTTP Connector
Automate Clio with Tray.ai
Create a matter, create a contact and create an activity in Clio, and start a workflow when Clio sends “Record created”.
What can you do with Clio on Tray.ai?
Clio is legal practice management software for law firms, covering matters, clients, time tracking, billing, calendars, tasks and documents. Tray.ai connects to Clio through the HTTP Connector, so your workflows can call the Clio API alongside the rest of your stack.
- When Clio sends “Matter opened”, create a project in your project tracker for the new case.
- Create a contact in Clio when a new client signs your intake form.
- When Clio sends “Matter closed”, tell the billing team in your team chat to send the final invoice.
- Create a matter in Clio when a new engagement is approved in your CRM.
- Connects through
- HTTP Connector
- Authentication
- OAuth 2.0
- Base URL
- https://app.clio.com/api/v4
Set it up
Connect Clio to Tray.ai
Each step uses Clio's own API details, from its documentation.
Step 1
Sign in to Clio with OAuth 2.0
Set up an OAuth 2.0 authentication with the client ID and secret of an OAuth app you register with Clio. Sign in once and every step reads the token from there.
Step 2
Point the HTTP Client at the API
Add an HTTP Client step and use https://app.clio.com/api/v4 as the base URL. Or paste a cURL example from Clio's API docs, and Tray.ai fills in the method, URL, and headers.
Step 3
Start with “List matters”
It's one of 30 documented actions, under Matters. The response comes back as data the next step can map into your other apps.
Step 4
Start workflows from Clio events
Give Clio the URL of a Tray.ai webhook trigger. “Record created” can then start a workflow, and so can 5 other events.
Give your AI agents Clio tools
Build an MCP server on Clio in Agent Gateway and choose which actions your agents can call. Every call runs with access control and an audit trail. How Agent Gateway works
- List matters
- List contacts
- List activities
- List bills
- List calendar entries
- List tasks
- List documents
- Get a matter
What the Clio API covers
7 resources and 30 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.
Matters
- List matters
- Get a matter
- Create a matter
- Update a matter
- Delete a matter
Contacts
- List contacts
- Get a contact
- Create a contact
- Update a contact
- Delete a contact
Activities
- List activities
- Create an activity
- Update an activity
- Delete an activity
Bills
- List bills
- Get a bill
- Update a bill
- Delete or void a bill
Calendar entries
- List calendar entries
- Create a calendar entry
- Update a calendar entry
- Delete a calendar entry
Tasks
- List tasks
- Create a task
- Update a task
- Delete a task
Documents
- List documents
- Create a document
- Update a document
- Delete a document
Events Clio can send to a Tray.ai webhook trigger
- Record created
- Record updated
- Record deleted
- Matter opened
- Matter pended
- Matter closed
Checked against Clio's own documentation on 2026-10-22
How Tray.ai makes this work
Clio plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 10,000+ apps, databases, APIs, and services with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Clio — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose Clio actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on Clio data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More operations apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every operations connector →
Frequently asked questions
What can a Tray.ai workflow do in Clio?
+
The Clio API documents 30 actions across 7 resources (Matters, Contacts, Activities, Bills, Calendar entries, Tasks, Documents). For example: List matters; List contacts; List activities. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with Clio?
+
The Clio API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.
Which Clio events can start a Tray.ai workflow?
+
Clio sends 6 events to a webhook URL, for example: Record created; Record updated; Record deleted; Matter opened; Matter pended; Matter closed. A Tray.ai webhook trigger receives them and starts a workflow.
See Clio working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.