Integration
Connect PDQ Connect to CORE
When New Deployment fires in PDQ Connect, your agent runs Discover full text links in CORE. 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 CORE 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 CORE
When New Deployment in PDQ Connect
then Discover full text links in CORE
When New Device in PDQ Connect
then Recommend similar outputs in CORE
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 CORE
Triggers and actions 9 triggers · 27 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
Discover full text linksFinds a link to the full text of a research paper from its DOI, searching CORE and other external sources for the best match.
Action
Find data providersSearches CORE's data providers (repositories and journals that supply research papers) and returns the matching providers.
Action
Find outputsSearches CORE research outputs (papers and other repository records) by title, author, DOI or a field query and returns the matching outputs.
Action
Find worksSearches CORE works (deduplicated research papers grouped across repositories) and returns the matching works.
Action
Get data providerReturns the details of one CORE data provider (repository or journal), looked up by its CORE id or OpenDOAR id.
Action
Get journalReturns a single CORE journal, looked up by its CORE identifier or by ISSN.
Action
Get outputReturns a single research output (paper) from CORE by its CORE ID, including its metadata, authors, abstract and links.
Action
Get workReturns a single research work from CORE, including its title, authors, abstract, DOI, download link and full text.
Action
List outputs of data providerReturns the research outputs harvested from a CORE data provider, optionally narrowed by a search query.
Action
Recommend similar outputsReturns research outputs in CORE similar to a given paper, identified by its CORE ID or DOI, or described by its title, abstract, authors or free text.
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 CORE
Stripe to COREStripe is a payment processing platform for online businesses.
Notion to COREA new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.
Calendly to CORECalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Qwilr to COREQwilr is reimagining the way you communicate with your clients.
HubSpot to COREHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to CORESalesforce is a leading enterprise customer relationship management (CRM) platform.
Questions
PDQ Connect and CORE, 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 CORE when something happens in PDQ Connect?
Any of CORE's 10 actions, including Discover full text links, Find data providers, Find outputs and Find works. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from CORE to PDQ Connect?
CORE has no triggers in the catalog today, so automations start in PDQ Connect. If you need the other direction, ask: your agent reads CORE's API documentation and adds it.
Do I have to build a connector for PDQ Connect or CORE?
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 CORE 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.