Product Updates

Integrate HealthTasks with Salesforce via our REST API

Register the HealthTasks OpenAPI spec in Salesforce External Services, authenticate with Named Credentials, and pull clinical education data into Flow Builder without writing Apex for standard callouts.

HealthTasks

Jul 15, 2026 — 2 min read

When we introduced the HealthTasks REST API, the goal was to connect clinical education data to the systems your institution already runs.

For many nursing and allied health programs, that includes Salesforce as the SIS, or as a hybrid CRM/SIS for student success and institutional ops.

Integrate HealthTasks with Salesforce via our REST API

HealthTasks publishes a documented OpenAPI REST API. Salesforce External Services can register that spec, then expose HealthTasks operations as actions in Flow Builder. Your Salesforce admin can pull clinical education data into SIS workflows without writing Apex for standard callouts.

That means students, placements, compliance status, clinical logs, and related records can move from HealthTasks into Salesforce on a schedule or as part of an existing Flow. HealthTasks stays the system of record for clinical education. Salesforce stays where institutional teams already work. This is an OpenAPI-backed integration path, not an AppExchange listing or managed package.

How Salesforce admins connect it

1. Authenticate with Named Credentials

Create an API key in HealthTasks under Settings → REST API.

In Salesforce, store that key in an External Credential and attach it to a Named Credential pointed at:

https://app.healthtasks.ai/api/v1

HealthTasks accepts the key as the x-healthtasks-api-key header (or as Authorization: Bearer). Configure the Named Credential to send that header at runtime so the key never lives in Flow logic or Apex.

2. Register the OpenAPI spec as an External Service

In Setup → External Services, create a new service from the HealthTasks OpenAPI document. Link it to the Named Credential above, then upload the OpenAPI file from the API docs or point Salesforce at the published schema.

Salesforce parses the paths, parameters, and response shapes and turns them into invocable Flow actions. No custom HTTP callout class required for that registration path.

3. Pull data in Flow Builder

Add those actions to a Flow, map the JSON fields you need, and write them into Salesforce objects.

Common patterns:

Scheduled sync: A nightly Flow pulls /students, /site_placements, /compliance_statuses, or /clinical_logs and updates Salesforce records.
On-demand refresh: A screen or record-triggered Flow fetches the latest HealthTasks data when a coordinator or mentor needs current clinical status.
Declarative mapping: Loop through returned arrays and update Contacts or custom objects without maintaining Apex serializers.

Most of the API is read-oriented, which is what this pull path needs. Salesforce calls HealthTasks, receives the latest records, and updates the Salesforce side.

Why this beats file drops

Legacy handoffs often depend on overnight CSVs or SFTP jobs. Column drift, missed files, and delayed refreshes create reconciliation work for program teams.

An OpenAPI-backed REST API lets Salesforce pull exactly what it needs, when it needs it. IT gets a standard integration surface. Salesforce architects can stay in External Services and Flow for many use cases instead of owning brittle batch pipelines.

When MuleSoft is already in the picture

Some campuses run Salesforce as the SIS or hybrid CRM/SIS and use MuleSoft Anypoint as the broader integration layer next to Education Cloud. In that model, HealthTasks still publishes the same OpenAPI. MuleSoft can pull clinical education data and orchestrate it alongside other campus APIs, while Salesforce Flow remains the right path for in-org declarative sync.

Both paths use the same HealthTasks API. Choose External Services and Flow when Salesforce admins own the integration. Choose MuleSoft when enterprise IT already routes campus systems through Anypoint. See Connect HealthTasks through your campus integration platform for MuleSoft, Power Automate, Boomi, and related stacks.