Integration
Connect Grist and PDQ Connect
When New or Updated Record fires in Grist, your agent runs Add group in PDQ Connect, or New Deployment in PDQ Connect to Create or Update Record in Grist. 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 Grist 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 Grist and PDQ Connect can do together
From Grist to PDQ Connect
When New or Updated Record in Grist
then Add group in PDQ Connect
When New Record in Grist
then Create Custom Field in PDQ Connect
From PDQ Connect to Grist
When New Deployment in PDQ Connect
then Create or Update Record in Grist
When New Device in PDQ Connect
then Create Record in Grist
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 Grist and PDQ Connect
Triggers and actions 13 triggers · 38 actions
Trigger
New or Updated RecordTriggered when a row in a Grist table is created or updated.
Trigger
New or Updated Record (Instant)Triggers when a Record is updated, or a new Record is added.
Trigger
New RecordTriggered when a new row is added to a Grist table.
Trigger
New Record (Instant)Triggers when a new Record is created
Action
Add ColumnAdds a column to a table in a Grist document.
Action
Add TableCreates a new table in a Grist document, optionally with a starting set of columns.
Action
Create DocumentCreates a new document in a Grist workspace and returns its document ID.
Action
Create or Update RecordAdds a row to a Grist table, or updates the existing row when the match column already holds the match value. Returns the row ID.
Action
Create RecordAdds a new row to a Grist table and returns its row ID.
Action
Create WorkspaceCreates a new workspace in a Grist organization and returns its ID.
Action
Delete DocumentDeletes a Grist document permanently.
Action
Delete RecordsDeletes one or more rows from a Grist table by row ID.
Action
Delete WorkspaceDeletes a Grist workspace along with every document inside it.
Action
Find RecordSearches a Grist table for a row whose column holds a given value and returns that row's ID and column values.
Action
Get DocumentReturns the details of one Grist document — its name, web address, workspace, and organization.
Action
Get OrgReturns the details of one Grist organization (team site) — its name, subdomain, owner, and your access level.
Action
Get WorkspaceReturns the details of one Grist workspace, including the documents it contains.
Action
List ColumnsReturns the columns of a Grist table, with each column's ID, label, and type.
Action
List OrgsReturns every Grist organization (team site) this connection can reach.
Action
List TablesReturns the tables in a Grist document.
Action
List WorkspacesReturns the workspaces in a Grist organization, each with the documents it contains.
Action
Run SQL QueryRuns a read-only SELECT statement against a Grist document and returns the rows.
Action
Update DocumentRenames a Grist document or changes whether it is pinned. Anything left blank stays as it is.
Action
Update RecordChanges the column values of one row in a Grist table. Columns left blank keep their current values.
Action
Update WorkspaceRenames a Grist workspace.
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 Grist
Grist to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Grist to ClickhouseColumn-oriented database for real-time analytical SQL queries at petabyte scale.
Grist to Mistral AIMistral AI is a platform for building, customizing, and deploying advanced AI models and agents for...
Grist to OpusClipOpusClip is a AI video tool that turns long videos into viral shorts with captions and transcripts.
Grist to PostmanPostman is a platform for building and testing APIs.
Grist to RuneScapeThe RuneScape Wiki API exposes data for RuneScape and Old School RuneScape.
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
Grist and PDQ Connect, answered
What can start an automation from Grist?
Any of Grist's 4 triggers in the catalog, including New or Updated Record, New or Updated Record (Instant), New Record and New Record (Instant). 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 Grist?
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 Grist?
Yes. When something happens in PDQ Connect, your agent can act in Grist too. This page covers both directions: PDQ Connect's triggers and Grist's actions are listed here as well.
Do I have to build a connector for Grist 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 Grist 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.