GenHealth Workflow Developer API

Build workflow automations

Discover supported integrations and actions, validate canonical workflow JSON, manage drafts and immutable versions, inspect graphs, publish viable workflows, and operate organization-scoped workflow runs.

Workflow runs, integrations, and events

These terms describe what starts a workflow, how it works with other systems, and how its step attempts are modeled.

Workflow run

One run begins each time a workflow is triggered—by a person, schedule, API request, file upload, or webhook—and ends when it completes, fails, or is canceled. Branches, waits, loops, and step retries remain part of that run; a child workflow starts a separate run.

Integration

An integration connects a workflow to another system or exposes a GenHealth capability. It provides actions—tools such as finding a record, extracting data, or sending an update—that can be used as workflow steps. Some integrations require a configured connection or credentials.Browse available integrations and actions

Modeled internal event

A planning unit for work performed inside a run. In the historical benchmark, each event represents one successful or failed attempt to execute a workflow step, after replay duplicates are removed. Loops and retries can add events; an event does not map one-to-one to a visible block, tool call, or external request.

Contract summary

Organization isolation

Workflow definitions, versions, graphs, webhook endpoints, and runs are resolved within the organization carried by the authenticated credential. An identifier from another organization does not grant access.

Operations