# Clio integrations: matters and contacts

> Create a matter, create a contact and create an activity in Clio, and start a workflow when Clio sends “Record created”.

**Canonical page:** https://tray.ai/connectors/clio-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

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.

## Use cases

### Matters

Read, create, update, and delete matters in Clio from any Tray.ai workflow. The Clio API covers calls such as list matters and get a matter.

- List matters
- Get a matter
- Create a matter

### Contacts

Read, create, update, and delete contacts in Clio from any Tray.ai workflow. The Clio API covers calls such as list contacts and get a contact.

- List contacts
- Get a contact
- Create a contact

### Activities

Read, create, update, and delete activities in Clio from any Tray.ai workflow. The Clio API covers calls such as list activities and create an activity.

- List activities
- Create an activity
- Update an activity

### Bills

Read, update, and delete bills in Clio from any Tray.ai workflow. The Clio API covers calls such as list bills and get a bill.

- List bills
- Get a bill
- Update a bill

### Calendar entries

Read, create, update, and delete calendar entries in Clio from any Tray.ai workflow. The Clio API covers calls such as list calendar entries and create a calendar entry.

- List calendar entries
- Create a calendar entry
- Update a calendar entry

### Tasks

Read, create, update, and delete tasks in Clio from any Tray.ai workflow. The Clio API covers calls such as list tasks and create a task.

- List tasks
- Create a task
- Update a task

## Challenges Tray.ai solves

### Keeping Clio credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Clio credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Clio API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Clio API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Clio?

Yes. Tray.ai connects to Clio through the HTTP Connector, which calls the Clio API directly. Any call the Clio API documents can run as a step in a Tray.ai workflow.

### 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.

### Can I get a dedicated Clio connector?

Clio runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Clio connector from the Clio API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/