Connector library

Implemented source CX & Support APIs

System Surveyor connector.

Read selected System Surveyor v3 account seat usage and exact site reference metadata through two named actions.

Download connector See all connectors

Connector download

Download System Surveyor

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
1394e0213d751d0b488ccb97596add65117a8fe1dd51f6228c5c208dc199a215

Version history

What's new

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

    Two named v3 reads return selected account seat usage and verified exact site references on the current OpenAPI server, using a managed administrator-issued Bearer token. Replaces the generic scaffold; hosted/live validation remains pending.

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

    Historical configurable HTTP scaffold; not a vendor-specific implementation.

    View download

Included in this version

Included actions

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

Get account usage

Requested native account integer in the local safe nonnegative subset; account-management access required.

Get site reference

Exact issued site UUID v4; preserve case, no whitespace; read access required.

Vendor API

API and access

Vendor API documentation Vendor website
Implementation considerations
  • Account seat usage: Read active/disabled member, invitation and guest counts plus maximum and signed available seats.
  • Exact site references: Verify the returned site ID and select name, label, version, activity flag, team ID and survey count.
  • Caller-managed reads; no site edits, survey contents, personal profiles, documents or writes are included.
  • An entitled Enterprise account and administrator-created API access_token are required. Store only that token in a managed Bearer Token credential; the native header is Authorization: Bearer. Key lifecycle, entitlement and permissions remain external; user login, refresh and share-token schemes are separate unsupported contracts.
  • The fixed target is openapi2.systemsurveyor.com, the current OpenAPI Production Server. Introductory prose still names openapi.systemsurveyor.com; the connector follows the machine-readable server without silent host fallback. Verify live deployment/token compatibility. Account usage requires account-management permission; the requested account ID is path context, not response-verified identity.
  • Site ID is the exact issued UUID v4 and must match the native returned ID. Names and labels preserve empty strings with a local 1024-byte UTF-8 cap. Selected integer magnitudes are capped locally at 99999999999999; available seats retains negative values, while other count/ID/version fields are nonnegative. Missing, unsafe or excessive metadata fails. Activity and survey counts do not establish operational health or survey completeness.
  • Addresses, users, timestamps, tags and survey contents are omitted. The survey-detail endpoint, which can trigger background preview generation, is excluded. Request Budget is 1000–8000 ms shared by transport and validation, default 7000; strict JSON/UTF-8 has a 1 MiB cap. Normal TLS verification remains enabled; redirects/proxies and replay are disabled. HTTP 404 remains failure. Hosted import, mappings, dependencies and live server/token/permissions remain untested.
  • Two packaged v3 reads return selected account seat usage and verified site reference metadata. The current OpenAPI establishes paths, jwt Bearer authentication and the production server; live target/token/entitlement/permissions and hosted dependencies need validation.

Support

Need help with System Surveyor?

Tell us what you need to connect or change.

Contact us Back to connectors