Connector library

Implemented source Enterprise, ERP & HR APIs

Duro PLM connector.

Read Duro Design organization library references and exact component ID/name/revision metadata through two named scoped GraphQL actions.

Connector download

Download Duro PLM

Versioned ZIP for your CXFabric tenant.

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
Connection settings
Library Slug, Organization Slug
Package size
8 KB
SHA-256
a1c27ba0fed01b3362a116385a596b943f9fa21c160b644493e7500a1bf4e743

Version history

What's new

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

    Read Duro Design organization library references and exact component ID, name and revision metadata through two named scoped GraphQL actions.

  2. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Historical readable HTTP scaffold; original bytes and identity are preserved.

Included in this version

Included actions

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

List library references

Read bounded selected library IDs, names and slugs in the organization scope.

Get component

Read selected exact component ID/name/revision metadata in the explicit organization/library scope.

Vendor API

API and access

Implementation considerations
  • Library references: Read organization-scoped library IDs, nullable names and bare slugs.
  • Exact component lookup: Read an exact component ID, nullable name and revision label in an explicit organization/library scope.
  • Scoped no match: Keep a native nullable component result distinct from API failure or global absence.
  • Caller-managed reads; no writes, BOM traversal or document downloads are included.
  • Store only the issued Design integration API key in a managed Bearer Token credential; this container supplies x-api-key without an Authorization header. Organization Slug uses the exact @organization form, retaining case and zeroes. A component lookup additionally sends x-library: @organization/library using the bare Library Slug. Key issuance, rotation, RBAC and permission scope remain external.
  • Fixed read queries use https://api.durohub.com/graphql and the current Design/v2 namespaces. Maximum References is a local array cap of 1–1000, default 100; no paging, total or full-coverage claim is invented. IDs and slugs must be unique. The declared ASCII slug and component-ID subsets preserve exact spelling without UUID or numeric assumptions.
  • Native findOne: null means no match only in the selected organization/library/key scope. Any GraphQL error, including partial data, remains failure; HTTP 404 is not a no-match shortcut. Nullable names and revision labels retain null and empty strings. Revision labels do not establish lifecycle state or revision ordering. Missing selected fields fail.
  • Request Budget is 1000–8000 ms shared by transport and validation, default 7000, with strict UTF-8 JSON and a 1 MiB response cap. Normal TLS verification stays enabled, redirects and environment proxies are disabled, and failures are not replayed. Older v1, dedicated/ITAR hosts and account Bearer authentication require a separate contract. Hosted import, dependencies and live key/org/library checks remain untested.
  • Two packaged Duro Design/v2 GraphQL reads discover organization libraries and selected exact component metadata. Current integration guides establish queries and scope headers; live key/org/library/RBAC and hosted dependencies require validation.

Support

Need help with Duro PLM?

Tell us what you need to connect or change.