Connector library

Implemented source Scheduling, Booking & Practice Systems

Dentrix Ascend connector.

Read selected Dentrix Ascend organization and exact location reference metadata using named bounded REST actions and a managed issued OAuth token.

Download connector See all connectors

Connector download

Download Dentrix Ascend

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
Connection settings
Environment, Organization ID
Package size
7 KB
SHA-256
023f871f792993da4e1617297b48681159ea00384ac5496b40193cb4c1605917

Version history

What's new

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

    Replaces the generic scaffold with two exact organization/location reference reads using issued OAuth tokens, explicit organization context, native numeric identities and bounded failure handling. No patient data or writes.

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

    Historical readable HTTP scaffold; immutable archive retained.

    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 location reference

Read selected numeric ID, optional name, abbreviation and time zone for an exact location.

Get organization reference

Read selected exact numeric organization record ID, required name and optional time zone in the supplied context.

Vendor API

API and access

Vendor API documentation Vendor website
Implementation considerations
  • Store only the approved environment-specific issued OAuth token in a managed Bearer Token credential. Requests send Authorization: Bearer and the exact Organization-ID header. Token lifecycle and permission assignment remain external.
  • Sandbox and production use test.hs1api.com/ascend-gateway/api and prod.hs1api.com/ascend-gateway/api with separate credentials. Dentrix desktop, arbitrary hosts and other HS1 products are excluded.
  • Organization ID is issued context retained in a declared local ASCII subset; it is distinct from the numeric Organization Record ID and is not echoed proof of tenant ownership. Positive numeric reference IDs use a local 14-digit subset and must match returned identities.
  • Integer/int64 schemas and numeric model examples ground this release; inconsistent string-ID/warning operation examples are rejected without guessed aliases. Optional text stays absent or empty; organization name is required. Live responseFields and ID types need validation.
  • Errors, warnings, null/missing results and inaccessible HTTP 404 remain failures. There is no enumeration, pagination, patient data, appointments, contacts, billing/clinical data, links, files or writes. References imply no availability, health, full visibility or stable snapshot.
  • Strict JSON/media/UTF-8, a 1 MiB response cap, normal TLS trust and shared 1–8 second budget fail without redirects, proxies or replay. Hosted import, dependencies and live token/header/permission/response behavior remain untested.
  • Two exact organization/location reference reads use the current public OpenAPI, environment-specific issued OAuth tokens and Organization-ID context. Numeric schemas conflict with some operation examples; hosted and live responseFields/ID acceptance need validation.

Support

Need help with Dentrix Ascend?

Tell us what you need to connect or change.

Contact us Back to connectors