Webhooks
Overview
Webhooks allow Welkin to send real-time HTTP notifications to external systems when specific events occur in your environment. Common use cases include syncing data to an EHR, triggering workflows in external platforms, or alerting data pipelines when patient records are updated.
How Webhooks Work
An event occurs in Welkin (e.g., patient created, assessment completed, CDT record updated).
Welkin sends an HTTP POST request to your configured webhook endpoint.
The endpoint receives the payload and processes it.
The payload contains event details including the event type, timestamp, and relevant record data in JSON format.
Configuring Webhooks in the Designer
See How to Create Webhooks for step-by-step setup.
Managing Webhooks in the Admin Portal
Active webhooks can be viewed and managed in Admin Portal → Integrations → Webhooks. See Webhooks (Admin).
Webhook Security
Welkin supports webhook signature verification to ensure payloads are authentic:
Each webhook payload includes a signature header
Your endpoint can verify the signature using your shared secret
This prevents spoofed requests from malicious sources
Configure the webhook signature secret in the webhook setup. See Mobile App Signature and Webhook Event Signature settings.
Retry Behavior
If your endpoint returns a non-2xx response, Welkin will retry the webhook delivery. Ensure your endpoint is idempotent (i.e., processing the same event twice produces the same result).
Publishing
After creating or modifying webhooks in the Designer, create a draft and publish. The webhook is then visible in the Admin Portal for activation.
Related Topics
How to Create Webhooks – webhook configuration guide
Webhooks (Admin) – managing webhooks in Admin
Integrations Overview – integration setup
API Clients – API authentication
Last updated
Was this helpful?