Integration
Connect PDQ Connect to Hippo
When New Deployment fires in PDQ Connect, your agent runs Create Summary of Ticket History in Hippo. 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 PDQ Connect and Hippo 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 PDQ Connect can start in Hippo
When New Deployment in PDQ Connect
then Create Summary of Ticket History in Hippo
When New Device in PDQ Connect
then Create Ticket in Hippo
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 PDQ Connect and Hippo
Triggers and actions 9 triggers · 30 actions
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.
Action
Add custom eventCreate a custom event for a user (Automation/Create custom event in Hippo Postman docs): app_secret_key, user_unique_key, event_type, etc.
Action
Create ConversationCreates a new conversation in the system
Action
Create or Update UserCreate a new user or update an existing one
Action
Create Summary of Ticket HistoryCreates a summary of all notes and comments added in the ticket
Action
Create TicketCreates a new ticket in the system
Action
Get ticketGet ticket details by ticket_id. POST to Hippo ticketing API (Ticketing/Get Ticket Details in the Postman docs) with ticket_id, app_secret_key.
Action
List conversationsFetch a customer's conversation list (Chat/Fetch customer conversation list): email, app_secret_key, start, limit.
Action
List messagesFetch messages and chat details for a channel (Chat/Fetch messages and chat details): channel_id, app_secret_key, start, limit.
Action
Send Broadcast to UsersSends broadcast messages through hippo
Action
Send MessageSends a message in an existing chat
Action
Update Due Date of TicketUpdates due date of an existing ticket
Action
Update Ticket PriorityUpdates the priority of a ticket
Action
Update Ticket StatusUpdate status of a ticket
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 PDQ Connect
PDQ Connect to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
PDQ Connect to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
PDQ Connect to StripeStripe is a payment processing platform for online businesses.
PDQ Connect to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
PDQ Connect to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
PDQ Connect to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Hippo
Outlign to HippoOutlign is a simple Project Management tool for Creative Teams
HubSpot to HippoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to HippoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to HippoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to HippoGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to HippoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
PDQ Connect and Hippo, answered
What can start an automation from PDQ Connect?
Any of PDQ Connect's 9 triggers in the catalog, including New Deployment, New Device, New Group and New Package. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Hippo when something happens in PDQ Connect?
Any of Hippo's 13 actions, including Create Conversation, Create or Update User, Create Summary of Ticket History and Create Ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hippo to PDQ Connect?
Hippo has no triggers in the catalog today, so automations start in PDQ Connect. If you need the other direction, ask: your agent reads Hippo's API documentation and adds it.
Do I have to build a connector for PDQ Connect or Hippo?
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 PDQ Connect and Hippo 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.