Bed events, delivered and signed.
Outbound webhooks for bed status events are on the EnaBed roadmap. Join early access — we will notify you when HMAC-signed delivery opens for your tenant.
Planned capability: EnaBed outbound webhooks will push real-time JSON for bed status changes and occupancy updates to HTTPS endpoints with HMAC-SHA256 signatures, automatic retries, and per-organization endpoints.
Built for reliable delivery
HMAC-SHA256 Signing
Every payload is signed so your receiver can verify it genuinely came from EnaBed.
Automatic Retries
Failed deliveries retry with exponential back-off, then surface in the delivery log.
Per-Organization Endpoints
Each tenant's endpoints are fully isolated, with their own URL and signing secret.
Multiple Endpoints
Configure several endpoints to fan out bed events to different systems independently.
Payload Presets
Generic JSON plus Slack, Microsoft Teams, and Discord presets — no manual mapping.
Secret Rotation
Rotate an endpoint's signing secret at any time, with a grace period to avoid disruption.
Delivery Logs
Inspect every attempt, see failure reasons, and re-trigger deliveries manually.
Automation-Ready
Connect to n8n, Make, Zapier, or your EHR/ADT endpoint to build any downstream workflow.
How to set up a webhook
- 1
Open Global Settings → Integrations in the EnaBed admin panel.
- 2
Create a new webhook endpoint and paste your receiver URL.
- 3
Select bed event types and choose a payload preset (Generic, Slack, Teams, or Discord).
- 4
Copy the signing secret and verify the X-Ena-Signature header on incoming requests.
Webhooks FAQ
See EnaBed in your facility.
Contact us — we'll walk through facility modeling, bed workflows, live updates, and your enterprise configuration together.