Healthie Connector

Connect Healthie so Applied can work with Healthie scheduling and client data through Healthie’s GraphQL API.

Use this Connector when a healthcare support workflow needs appointment, availability, patient, provider, or related operational context from Healthie.

Common use cases

Look up Healthie users or client context.
Create appointments after a customer confirms the details.
Check provider availability.
Use Healthie scheduling results in a Flow.

Healthie data can be sensitive. Scope the connected account carefully and test workflows before using them with live patients.

Before you begin

Before connecting Healthie, make sure:

Your Healthie team approves the API use case.
You know whether to use an admin or service account API key.
The Healthie user behind the key has the permissions Applied needs.
You know whether your Healthie data uses an authorization shard.
You have a test patient or appointment available for validation.

Healthie API keys inherit the permissions and behavior of the connected user account.

Get a Healthie API key

Healthie API keys are tied to Healthie user accounts. Healthie documents API key creation through the createApiKey GraphQL mutation.

Work with your Healthie admin or Healthie solutions contact to create the API key for the right user account. For backend or data-focused workflows, use an admin or service account only if that matches your compliance and audit model.

If Healthie tells you your data is in a shard, collect the shard authorization ID. Applied sends it as the AuthorizationShard header.

Connect Healthie in Applied

Open Connectors.
Click New.
Choose Healthie.
Paste the Healthie API key into the API token field.
If your setup uses a shard, enter the shard ID if Applied asks for it.
Create the connection.

Applied sends Healthie requests with Authorization: Basic <api key> and AuthorizationSource: API.

Configure Healthie access

Because Healthie API keys inherit user permissions, confirm the connected user can access only the objects your workflows need.

For example:

Use read access for lookups and availability checks.
Add scheduling permissions only when Applied should create appointments.
Avoid using a personal clinician account when a service account is more appropriate.
Review Healthie audit behavior for actions done through the API key.

Validate the connection

After setup:

Run a lookup against a test user or appointment.
Confirm the returned Healthie record matches the expected organization.
If scheduling actions are enabled, create a test appointment.
Confirm Healthie audit and notification behavior matches your expectations.

Common issues

Healthie rejects the API key

Confirm the key is active and copied without extra spaces. Healthie expects the key in the Basic authorization header with AuthorizationSource: API.

Requests fail only for one dataset

Ask Healthie whether the data requires an AuthorizationShard value and add the shard ID if needed.