Integration
Connect Clio to DocsBot AI
When Matter Status Updated fires in Clio, your agent runs Add lead in DocsBot AI. 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 DocsBot AI to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 can start in DocsBot AI
When Matter Status Updated in Clio
then Add lead in DocsBot AI
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 DocsBot AI
Triggers and actions 8 triggers · 51 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.
- Add bot
Creates a new DocsBot bot in a team, optionally copying sources from an existing bot.
- Add lead
Captures or updates a lead for a DocsBot conversation, merging the supplied contact details (email, name, company and so on) into the lead record.
- Add source
Creates a new training source (URL, sitemap, document, Q&A and more) on a DocsBot bot.
- Ask Question (Legacy)
Asks a DocsBot bot a question using the legacy Chat API and returns the answer, its sources and the updated chat history.
- Chat Agent Message (Recommended)
Sends a message to a DocsBot bot in a stateful conversation and returns the agent's answer, sources and conversation history.
- Create Web Source
Adds a web-based training source (a page URL, sitemap, RSS feed or YouTube video) to a DocsBot bot and returns the created source.
- Delete bot
Permanently deletes a bot from a DocsBot team.
- Delete lead
Deletes one captured lead record from a DocsBot bot.
- Delete source
Deletes a training source from a DocsBot bot. The source may still appear in chat answers for a few minutes afterwards.
- Get bot
Returns one DocsBot bot with its settings, model, status and source counts.
- List bots
Returns the bots in a DocsBot team, optionally filtered by text or privacy and sorted.
- Semantic Search
Searches a bot's trained content and returns the most relevant source chunks for a natural-language query.
- Update bot
Updates the settings of an existing DocsBot bot, such as its name, description, prompt, model, privacy and widget appearance. Only the fields you fill in are changed.
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 DocsBot AI
Questions
Clio and DocsBot AI, 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 DocsBot AI when something happens in Clio?
Any of DocsBot AI's 13 actions, including Create Web Source, Update bot, Add bot and Add lead. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from DocsBot AI to Clio?
DocsBot AI has no triggers in the catalog today, so automations start in Clio. If you need the other direction, ask: your agent reads DocsBot AI's API documentation and adds it.
Do I have to build a connector for Clio or DocsBot AI?
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.
Can my AI client use Clio and DocsBot AI without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.