Integration
Connect Clio and Request Tracker (RT)
When Matter Status Updated fires in Clio, your agent runs Update Ticket Status in Request Tracker (RT), or Ticket Created in Request Tracker (RT) to Create Company Contact in Clio. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Clio and Request Tracker (RT) to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Clio and Request Tracker (RT) can do together
From Clio to Request Tracker (RT)
When Matter Status Updated in Clio
then Update Ticket Status in Request Tracker (RT)
From Request Tracker (RT) to Clio
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Clio and Request Tracker (RT)
Triggers and actions 11 triggers · 57 actions
- Matter Status Updated
Triggers when the status of a matter has changed.
- New Activity
Triggers when a new activity is created.
- New Calendar Entry
Triggers when a new calendar entry is created.
- New Communication
Triggers when a new communication is created.
- New Contact
Triggers when a new contact is created.
- New Matter
Triggers when a new matter is created.
- New Task
Triggers when a new task is created.
- Task Status Updated
Triggers when the status of a task has changed.
- Create Calendar Entry
Creates a new calendar entry.
- Create Communication
Creates a new communication.
- Create Company Contact
Creates a company contact.
- Create Expense Entry (Activity)
Creates a new expense entry.
- Create Matter
Adds a new matter to Clio Manage.
- Create Matter Folder
Creates a new folder in a matter.
- Create Matter Note
Creates a new matter note.
- Create Person Contact
Creates a person contact.
- Create Task
Creates a new task.
- Create Time Entry (Activity)
Creates a new time entry.
- Delete activity
Delete an activity.
- Delete calendar entry
Delete a calendar entry.
- Delete contact
Delete a contact.
- Delete matter
Delete a matter.
- Delete task
Delete a task.
- Find Company Contact
Returns the company contacts that match the search text.
- Find Matter
Returns the matters that match the specified search text and optional filters
- Find Newest Matter by Client Email
Returns the most recently created matter for the client with the given email address.
- Find Person Contact
Find a person contact by ID, name, title, email address, address, phone number, web site, instant messenger, custom fields, related matter name, or company name matching a given string.
- Find User
Find a user by name.
- Get activity
Fetches an activity (time or expense entry) by ID. An error occurs if the activity is not found.
- Get calendar entry
Returns one calendar entry by id, including summary, start and end times.
- Get communication
Returns one communication by id.
- Get contact
Retrieve a contact (person or company) by id.
- Get document
Retrieve document metadata by id.
- Get matter
Retrieve a matter by id.
- Get task
Retrieve a task by id.
- List activities
List all activities.
- List contacts
List all contacts.
- List practice areas
List practice areas.
- List tasks
List all tasks.
- List users
List firm users.
- Update activity
Update an activity.
- Update calendar entry
Update a calendar entry.
- Update Matter
Update an existing matter.
- Update Person Contact
Updates an existing person contact.
- Update Task
Updates a task.
- Upload Document to Matter
Uploads a file from a URL into a Clio matter's documents and marks it fully uploaded.
- Ticket Correspondence
Triggers when a ticket is replied to (that is, corresponded with).
- Ticket Created
Triggers when a new Request Tracker ticket is created.
- Ticket Status Changed
Triggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.
- Add asset
Create an asset.
- Add user
Create a user.
- Comment on a Ticket
Add an internal comment to a ticket and send to any internal watchers.
- Create Ticket
Create a new ticket in Request Tracker.
- Find Attachment
Locate an attachment by ID.
- Find Ticket
Locate a ticket by ID.
- Find Tickets
Issue a query to find matching tickets.
- Find Transaction
Find a transaction by ID
- Get asset
Retrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.
- Get queue
Get a queue by id or name.
- Get user
Get a user by id or name.
- List queues
List all queues visible to user.
- List ticket history
List transactions of a ticket.
- Reply to a Ticket
Reply to the requestor and any internal or external watchers of a ticket.
- Update ticket
General ticket update (Owner, Priority, Queue, custom fields).
- Update Ticket Due Date
Update the due date of a ticket.
- Update Ticket Status
Update the status of a ticket.
- Update Ticket Subject
Update the subject of a ticket.
- Update user
Update a user.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Clio
Clio to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Clio to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Clio to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Clio to Google SheetsGoogle Sheets
Clio to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Clio to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Request Tracker (RT)
Google Drive to Request Tracker (RT)Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to Request Tracker (RT)Mailchimp marketing automation and email platform.
Questions
Clio and Request Tracker (RT), answered
What can start an automation from Clio?
Any of Clio's 8 triggers in the catalog, including Matter Status Updated, New Activity, New Calendar Entry and New Communication. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Request Tracker (RT) when something happens in Clio?
Any of Request Tracker (RT)'s 19 actions, including Create Ticket, Update ticket, Update Ticket Due Date and Update Ticket Status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Request Tracker (RT) to Clio?
Yes. When something happens in Request Tracker (RT), your agent can act in Clio too. This page covers both directions: Request Tracker (RT)'s triggers and Clio's actions are listed here as well.
Do I have to build a connector for Clio or Request Tracker (RT)?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.