Connector library

Implemented source CX & Support APIs

PDQ connector.

Read bounded PDQ Connect device, group, package and deployment pages, plus exact selected device/deployment results through six native GET actions using a managed scoped API key.

Download connector See all connectors

Connector download

Download PDQ

Versioned ZIP for your CXFabric tenant.

Sign in to download Using connectors

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.0 Choose version
Release
2026-10-04
Package
Implemented source
Schema credentials
Bearer token
Package size
8 KB
SHA-256
d15eaba86a34e8097975d0ee12dafac7e78fa593eece2fba248e03ef8e2a00f2

Version history

What's new

  1. v0.2.0.0Latest · 2026-10-04 · Implemented source

    Six named PDQ Connect GET reads replace the generic scaffold: bounded device/group/package/deployment metadata pages and exact device/deployment observations with scoped keys and checked server pagination.

    Full release notesView download
  2. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Historical configurable HTTP scaffold without implemented vendor actions.

    View download

Included in this version

Included actions

Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.

List devices

Read one checked selected device metadata page.

List groups

Read one checked selected group reference page.

List packages

Read one checked selected package reference page.

List deployments

Read one checked selected deployment task metadata page.

Get device

Read selected metadata for an exact device ID.

Get deployment

Read selected task counts for an exact deployment ID; nullable status is not completion.

Vendor API

API and access

Vendor API documentation Vendor website
Implementation considerations
  • Device observations: Read selected device pages or an exact device, including online/reboot flags without network-quality or freshness claims.
  • Group and package references: Read checked ID/name/source/type/count or version references from one native page.
  • Deployment results: Read selected deployment pages or an exact ID with nullable reported task counts without terminal-remediation inference.
  • Caller-managed metadata reads; no deployment initiation, reboot or webhook trigger is included.
  • Use the fixed PDQ Connect app.pdq.com v1 API with a managed bearer-token credential carrying the issued scoped API key. Grant devices:read, groups:read, packages:read or deployments:read as required. Key creation/rotation/revocation stays external; write scopes do not imply read scopes. PDQ Deploy/Inventory APIs are unsupported.
  • Page Size is locally limited to 1–100 despite the current OpenAPI maximum 250; Page Number is bounded. Native pageSize/page and server meta.page/pageSize/totalPages are checked. Excess rows, repeated IDs and mismatched metadata fail without truncation. Caller owns consistency, pacing, iteration and completeness; no next page or complete inventory is inferred.
  • Exact resource IDs preserve case and leading zeroes in the supported local string subset. Nullable/empty/future metadata, false flags and zero counts remain distinct. Deployment taskStatus: null reflects no reported/initiated task status; missing counts stay null, without aggregation or terminal-success conclusions. Raw last-seen text is retained without timestamp/freshness interpretation.
  • No writes, deployment initiation, reboot, package changes, custom fields, software/vulnerability inventory, user/IP/MAC/serial/directory details or arbitrary filters are included. Hosted import, executor dependencies and live subscription/API key/scopes/fields/paging require validation.
  • Six packaged PDQ Connect reads use scoped managed API keys and checked server pagination. Current vendor OpenAPI establishes routes and selected metadata; live organization access, fields and paging require validation.

Support

Need help with PDQ?

Tell us what you need to connect or change.

Contact us Back to connectors