Skip to main content
Workflows let you bundle approvals that are commonly requested together, so a single request delivers them to a user in one go. A workflow can also notify one or more of your configured webhook origins every time a decision is made on its approvals.

​
Features

  • Create: opens the workflow for immediate editing; rename it before using it in a request
  • Add approvals: attach documents, forms, and policies to the workflow
  • Add webhooks: pick one or more origins configured in your Webhooks settings to notify on every decision on the workflow’s approvals
  • Active: toggle visibility when generating new requests. A workflow cannot be saved as active until at least one approval has been added.

​
Example: hospital pre-admission

A pre-admission workflow for a surgical patient bundles three approvals into a single request:
  • Form: medical history questionnaire covering allergies, current medications, and prior conditions
  • Document: HIPAA notice of privacy practices, plus data-sharing consent with the patient’s insurer
  • Document: surgical consent and financial responsibility PDF, signed by the patient
As the patient accepts each approval, the workflow’s webhook origins are notified:
  • EMR endpoint: ingests the form responses into the patient’s medical record
  • Billing endpoint: uses the data-sharing consent to start insurance claim processing
  • Compliance endpoint: archives the signed PDF for regulatory retention
The hospital configures the bundle and its webhooks once; every new patient request reuses the same workflow.

​
Glossary

Workflow webhooks: the origins attached to a workflow receive a credential event for every decision, accept or reject, on its approvals. They must already be configured in Webhooks settings.

​
API access

Workflows are listed with GET /approvals/workflow and referenced by id when creating requests with POST /request.