Integration
Connect Mojo Helpdesk and PDQ Connect
When New Ticket fires in Mojo Helpdesk, your agent runs Add group in PDQ Connect, or New Deployment in PDQ Connect to Add Comment to Ticket in Mojo Helpdesk. 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 Mojo Helpdesk 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 Mojo Helpdesk and PDQ Connect can do together
From Mojo Helpdesk to PDQ Connect
When New Ticket in Mojo Helpdesk
then Add group in PDQ Connect
When New Ticket With Due On in Mojo Helpdesk
then Create Custom Field in PDQ Connect
From PDQ Connect to Mojo Helpdesk
When New Deployment in PDQ Connect
then Add Comment to Ticket in Mojo Helpdesk
When New Device in PDQ Connect
then Add Staff Note to Ticket in Mojo Helpdesk
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 Mojo Helpdesk and PDQ Connect
Triggers and actions 13 triggers · 40 actions
Trigger
New TicketTriggers when a new ticket is created in Mojo Helpdesk.
Trigger
New Ticket With Due OnTriggers when a new Mojo Helpdesk ticket that has a due date is created.
Trigger
New Ticket With Scheduled OnTriggers when a new Mojo Helpdesk ticket that has a scheduled date is created.
Trigger
New UserTriggers when a new user is created in Mojo Helpdesk.
Action
Add assetCreates a new asset in Mojo Helpdesk Asset Management and returns the created asset.
Action
Add Comment to TicketAdds a public comment to a Mojo Helpdesk ticket.
Action
Add Staff Note to TicketAdds an internal staff-only note to a Mojo Helpdesk ticket.
Action
Add Tag to TicketAdds a tag to a Mojo Helpdesk ticket, creating the tag if it does not exist.
Action
Add task to ticketCreates a task on a ticket, with optional notes, due date, assignee and completion status.
Action
Create TicketCreates a new ticket in Mojo Helpdesk and returns it.
Action
Create UserCreates a new user in Mojo Helpdesk.
Action
Delete ticketPermanently deletes a ticket, including its comments and attachments.
Action
Delete userPermanently deletes a user from Mojo Helpdesk. This cannot be undone.
Action
Find assets by criteriaReturns the assets that match a search query, such as a name, tag, serial number, location or assigned user.
Action
Find User by EmailFinds a Mojo Helpdesk user by email address.
Action
Get assetReturns the details of a single asset, including its status, location, assigned users and attached files.
Action
Get TicketReturns one Mojo Helpdesk ticket by its ID, including title, description, status, priority and assignee.
Action
Get UserReturns one Mojo Helpdesk user by ID.
Action
List commentsReturns the comments on a Mojo Helpdesk ticket, including staff notes.
Action
List ticket queuesReturns the ticket queues in your Mojo Helpdesk account, with each queue's id, name and email settings.
Action
List ticketsReturns the tickets in your Mojo Helpdesk, sorted by the field and order you choose.
Action
List usersReturns the users (end users and agents) in your Mojo Helpdesk account.
Action
Remove tag from ticketRemoves a tag from a ticket, identified by the tag's ID or label, and returns the ticket's remaining tags.
Action
Search TicketsFinds Mojo Helpdesk tickets matching a search query (same syntax as the web app's advanced search).
Action
Update assetUpdates an existing asset in Mojo Helpdesk, changing only the fields you supply.
Action
Update TicketUpdates an existing Mojo Helpdesk ticket; only the fields you supply change.
Action
Update UserUpdates a Mojo Helpdesk user's details; only the fields you supply change (email cannot be changed here).
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 Mojo Helpdesk
Mojo Helpdesk to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Mojo Helpdesk to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mojo Helpdesk to StripeStripe is a payment processing platform for online businesses.
Mojo Helpdesk to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Mojo Helpdesk to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Mojo Helpdesk to PipedrivePipedrive is a sales CRM and pipeline management tool.
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
Mojo Helpdesk and PDQ Connect, answered
What can start an automation from Mojo Helpdesk?
Any of Mojo Helpdesk's 4 triggers in the catalog, including New Ticket, New Ticket With Due On, New Ticket With Scheduled On and New User. 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 Mojo Helpdesk?
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 Mojo Helpdesk?
Yes. When something happens in PDQ Connect, your agent can act in Mojo Helpdesk too. This page covers both directions: PDQ Connect's triggers and Mojo Helpdesk's actions are listed here as well.
Do I have to build a connector for Mojo Helpdesk 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 Mojo Helpdesk 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.