Integration
Connect Clio and PDQ Connect
When Matter Status Updated fires in Clio, your agent runs Add group in PDQ Connect, or New Deployment in PDQ Connect 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 PDQ Connect 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 PDQ Connect can do together
From Clio to PDQ Connect
When Matter Status Updated in Clio
then Add group in PDQ Connect
When New Activity in Clio
then Create Custom Field in PDQ Connect
From PDQ Connect to Clio
When New Deployment in PDQ Connect
then Create Company Contact in Clio
When New Device in PDQ Connect
then Create Person Contact in 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 PDQ Connect
Triggers and actions 17 triggers · 55 actions
Trigger
Matter Status UpdatedTriggers when the status of a matter has changed.
Trigger
New ActivityTriggers when a new activity is created.
Trigger
New Calendar EntryTriggers when a new calendar entry is created.
Trigger
New CommunicationTriggers when a new communication is created.
Trigger
New ContactTriggers when a new contact is created.
Trigger
New MatterTriggers when a new matter is created.
Trigger
New TaskTriggers when a new task is created.
Trigger
Task Status UpdatedTriggers when the status of a task has changed.
Action
Create Calendar EntryCreates a new calendar entry.
Action
Create CommunicationCreates a new communication.
Action
Create Company ContactCreates a company contact.
Action
Create Expense Entry (Activity)Creates a new expense entry.
Action
Create MatterAdds a new matter to Clio Manage.
Action
Create Matter FolderCreates a new folder in a matter.
Action
Create Matter NoteCreates a new matter note.
Action
Create Person ContactCreates a person contact.
Action
Create TaskCreates a new task.
Action
Create Time Entry (Activity)Creates a new time entry.
Action
Delete activityDelete an activity.
Action
Delete calendar entryDelete a calendar entry.
Action
Delete contactDelete a contact.
Action
Delete matterDelete a matter.
Action
Delete taskDelete a task.
Action
Find Company ContactReturns the company contacts that match the search text.
Action
Find MatterReturns the matters that match the specified search text and optional filters
Action
Find Newest Matter by Client EmailReturns the most recently created matter for the client with the given email address.
Action
Find Person ContactFind 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.
Action
Find UserFind a user by name.
Action
Get activityFetches an activity (time or expense entry) by ID. An error occurs if the activity is not found.
Action
Get calendar entryReturns one calendar entry by id, including summary, start and end times.
Action
Get communicationReturns one communication by id.
Action
Get contactRetrieve a contact (person or company) by id.
Action
Get documentRetrieve document metadata by id.
Action
Get matterRetrieve a matter by id.
Action
Get taskRetrieve a task by id.
Action
List activitiesList all activities.
Action
List contactsList all contacts.
Action
List practice areasList practice areas.
Action
List tasksList all tasks.
Action
List usersList firm users.
Action
Update activityUpdate an activity.
Action
Update calendar entryUpdate a calendar entry.
Action
Update MatterUpdate an existing matter.
Action
Update Person ContactUpdates an existing person contact.
Action
Update TaskUpdates a task.
Action
Upload Document to MatterUploads a file from a URL into a Clio matter's documents and marks it fully uploaded.
Trigger
Matching Custom FieldTriggers for each PDQ custom field matching your filters on each poll, including ones that already exist.
Trigger
Matching DeploymentTriggers for each PDQ deployment matching your filters on each poll, with its status counts as first seen.
Trigger
Matching DeviceTriggers for each PDQ device matching your filters on each poll, including devices that already exist.
Trigger
Matching GroupTriggers for each PDQ group matching your filters on each poll, including groups that already exist.
Trigger
Matching PackageTriggers for each package in your PDQ library matching your filters on each poll, including existing ones.
Trigger
New DeploymentTriggers when a new deployment is created in PDQ.
Trigger
New DeviceTriggers when a new device is enrolled in PDQ.
Trigger
New GroupTriggers when a new device group is created in PDQ.
Trigger
New PackageTriggers when a new package is added to your PDQ library.
Action
Add groupCreates a static device group in PDQ Connect, optionally adding devices to it.
Action
Clear device custom field valueClears the value of a custom field on a device. The custom field itself is not deleted.
Action
Create Custom FieldCreates a new custom field definition in PDQ that devices can hold a value for.
Action
Delete custom fieldDeletes a custom field definition and removes its values from all devices.
Action
Delete groupDeletes a static group in PDQ Connect. The devices in the group are kept; only their membership is removed.
Action
Deploy PackageDeploys a package version to the PDQ devices and/or groups you list.
Action
Find Deployment by IDReturns one PDQ deployment by its ID with its current task status counts.
Action
Find DeviceFinds the first device in your PDQ organization whose name or hostname matches. Use ^value for starts-with or ~value for contains.
Action
Find Device by IDReturns one device in your PDQ organization by its ID, with its hardware, OS, user and network details.
Action
Find Device GroupFinds the first device group in PDQ whose name matches.
Action
Find Device VulnerabilitiesReturns the vulnerabilities detected on one PDQ device, optionally filtered by status or risk score.
Action
Find PackageFinds the first package in your PDQ library whose name or publisher matches.
Action
Find Package by IDReturns one package from your PDQ library by its ID, including its latest version.
Action
List device softwareReturns the software installed on a PDQ Connect device, with name, publisher, version and install details.
Action
Set Device Custom Field ValueSets the value of a custom field on one PDQ device.
Action
Update custom fieldRenames an existing custom field definition in PDQ Connect.
Action
Update groupRenames a static device group and/or replaces its device membership.
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 PandaDocPandaDoc helps you build and deliver sales quotes and proposals and track presentations and close deals...
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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Clio to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into PDQ Connect
HubSpot to PDQ ConnectHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PDQ ConnectGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PDQ ConnectGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PDQ ConnectGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PDQ ConnectGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PDQ ConnectMailchimp marketing automation and email platform.
Questions
Clio and PDQ Connect, 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 PDQ Connect when something happens in Clio?
Any of PDQ Connect's 17 actions, including Create Custom Field, Update custom field, Update group and Add group. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PDQ Connect to Clio?
Yes. When something happens in PDQ Connect, your agent can act in Clio too. This page covers both directions: PDQ Connect's triggers and Clio's actions are listed here as well.
Do I have to build a connector for Clio or PDQ Connect?
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 PDQ Connect 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.