Creating a webhook
Describe the inbound event:“Create a webhook so our EHR system can notify us when a patient’s chart is updated.”or
“Add a webhook endpoint for Stripe payment events.”The system creates the webhook and assigns a URL under your org’s runtime subdomain:
Connecting a webhook to a workflow
Once the webhook exists, a workflow can listen to it:“When the EHR webhook fires, extract the patient ID, look up the record in our entities, and run the PHI-aware chart update workflow.”The system compiles a workflow with a webhook trigger, wires the payload schema, and sets up the lookup step.
Payload schema
The system infers payload schema from your description or from a sample payload you provide:
“The EHR sends JSON like this: {"patient_id": "...", "event": "chart_updated", "updated_fields": [...]}.”
Paste the sample payload in chat. The system extracts the schema, makes it part of the workflow contract, and validates incoming payloads against it at runtime. Payloads that don’t match the schema are rejected with a 400 before the workflow fires.
Authentication
Webhooks support:| Method | Description |
|---|---|
| HMAC signature | The sender signs the payload; HASP verifies before the workflow fires |
| Shared secret header | A shared token in a custom request header |
| Bearer token | Authorization: Bearer <token> |
| None (not recommended) | Open endpoint — appropriate only for internal systems on private networks |