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 register one or more webhooks that fire when every approval in the bundle has been accepted. That helps when several downstream systems each need part of the result.

​
Features

  • Create: opens the workflow for immediate editing; rename it before using it in a request
  • Add approvals: attach documents, forms, consents, and mandates to the workflow
  • Add webhooks: register one or more endpoints to notify when the workflow concludes; each endpoint receives the same signed payload independently, so unrelated downstream systems do not need to share infrastructure
  • 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
  • Consent: 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
When the patient accepts the request, the workflow’s webhooks fire in parallel:
  • 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

Webhook completion: webhooks attached to a workflow fire only when every approval in the bundle is accepted. If any approval is rejected or the request expires, the workflow webhooks are not sent; per-approval events on the underlying request still deliver as usual.

​
API access

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