Integration
Connect PDQ Connect to Fergus
When New Deployment fires in PDQ Connect, your agent runs Add Contact in Fergus. 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 Fergus 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 Fergus
When New Deployment in PDQ Connect
then Add Contact in Fergus
When New Device in PDQ Connect
then Add Task in Fergus
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 Fergus
Triggers and actions 9 triggers · 48 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 Calendar EventCreates a new calendar event/booking.
Action
Add ContactCreates a new contact.
Action
Add NoteCreates a new note against a record.
Action
Add QuoteCreates a new draft quote on a Fergus job. Supported for jobs whose job type is Quote or Estimate.
Action
Add TaskCreates a new task in Fergus, optionally linked to a job and assigned to employees.
Action
Archive SiteArchives a site in Fergus. The site can later be restored.
Action
Create CustomerCreates a new customer.
Action
Create JobCreates a job in Fergus — an active job, a draft job, or a variation of an existing job.
Action
Create SiteCreates a new site.
Action
Delete CustomerDeletes a Fergus customer by ID.
Action
Edit Draft JobUpdates a draft job in Fergus. Only draft jobs can be edited; leave a field blank to keep its current value.
Action
Finalize Draft JobFinalises a draft job in Fergus, turning it into an active job.
Action
Find All QuotesReturns up to 100 quotes from across all jobs that match the specified status and date criteria.
Action
Find CustomerReturns the customers whose name, or main or billing contact's name, email or phone, contains the search text.
Action
Find SiteFinds sites by name, city, postal code, or free-text search. Returns the first page of matches (up to 10).
Action
Get Calendar EventReturns a single Fergus calendar event by its ID, including title, start/end times, event type, assigned user, linked job/job phase and recurrence details.
Action
Get ContactReturns a single Fergus contact (customer or site contact) by its ID, including name, position, company and contact items.
Action
Get Customer by IDReturns a Fergus customer by its ID.
Action
Get Customer InvoiceRetrieves a customer invoice by ID.
Action
Get Job by IDRetrieves a specific job using its unique ID.
Action
Get Quotes for JobReturns all quotes for a Fergus job, optionally filtered by status.
Action
Get Site by IDRetrieves a specific site using its unique ID.
Action
List ContactsLists contacts, with optional filtering.
Action
List Customer InvoicesLists customer invoices, with optional filtering.
Action
List NotesReturns the notes (with their replies) attached to a Fergus record.
Action
List TasksLists the company's tasks, optionally filtered by status, assigned employee, job, due date range or overdue state.
Action
Update ContactUpdates an existing customer contact or site contact in Fergus.
Action
Update CustomerUpdates an existing customer's details.
Action
Update QuoteUpdates a draft quote on a Quote or Estimate job in Fergus: title, description and its sections with line items.
Action
Update SiteUpdates an existing site's details.
Action
Update TaskUpdates a task's description, due date, or assigned employees in Fergus. The job a task is linked to cannot be 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 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 Fergus
Outlook to FergusOutlook is Microsoft's email and calendaring platform integrating contacts and scheduling, enabling users to...
HubSpot to FergusHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to FergusSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to FergusSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to FergusGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to FergusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
PDQ Connect and Fergus, 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 Fergus when something happens in PDQ Connect?
Any of Fergus's 31 actions, including Create Customer, Create Job, Create Site and Update Contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fergus to PDQ Connect?
Fergus has no triggers in the catalog today, so automations start in PDQ Connect. If you need the other direction, ask: your agent reads Fergus's API documentation and adds it.
Do I have to build a connector for PDQ Connect or Fergus?
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 Fergus 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.