YourMedSoft LogoYourMedSoft
Pricing
Log in
App Integrations4 min read
AdminManager / Coordinator

How do I configure outbound HTTPS webhooks and HMAC secrets for real-time event automation?

Register secure HTTPS webhook endpoints for your organization to stream real-time shift, timesheet, invoice, and credential events into Zapier, Make, or custom hospital middleware.

Direct Operational Answer

To configure outbound webhooks in YourMedSoft, register an HTTPS endpoint URL under your organization’s webhook configuration (/api/webhooks), select the event subscriptions to stream, and store the auto-generated HMAC signing secret. You can trigger a test ping (/api/webhooks/test) and inspect HTTP response codes in the webhook delivery history.

What You Need Before Starting

  • Admin or Manager permissions in your organization workspace.
  • A secure `https://` receiver URL (such as Zapier Webhooks, Make, n8n, or your internal API gateway).

Clinical & Regulatory Compliance Standards

  • Enforces TLS/HTTPS transport encryption and per-tenant isolation on all outbound webhook deliveries.

Step-by-Step Instructions

1

Prepare Your HTTPS Receiver Endpoint

Copy the destination `https://` webhook URL from your automation tool (e.g., `https://hooks.zapier.com/...`) or internal hospital integration server. Non-HTTPS URLs are rejected for security.

2

Register the Webhook & Select Events

Provide a descriptive endpoint name (e.g., "Zapier Approved Timesheet Sync"), enter the HTTPS URL, and select at least one event subscription (such as shift assigned, timesheet approved, or invoice generated).

UI: Webhook Configuration > Name, HTTPS URL & Event Subscriptions
Operational Automation

Automate Bidirectional Sync with 60+ Healthcare Platforms

Connect YourMedSoft directly to Gusto, ADP, Epic, PointClickCare, QuickBooks, and Bullhorn. Eliminate double entry with 1-click two-way sync.

3

Save Your HMAC Signing Secret

Upon creation, YourMedSoft generates a unique cryptographic signing secret for the endpoint. Use this secret on your receiving server to verify that incoming webhook payloads originated from YourMedSoft.

4

Send a Test Ping and Inspect Delivery Logs

Trigger a test webhook ping (/api/webhooks/test) to verify connectivity, and inspect recent deliveries (/api/webhooks/[id]/deliveries) to check the HTTP status code, timestamp, and delivery status.

Pro-Tips & Best Practices

  • Each webhook endpoint is strictly scoped to `/organizations/{orgId}/webhooks`—it only receives events triggered within your organization tenant.

Frequently Asked Questions & Troubleshooting

Why does YourMedSoft require an https:// webhook URL?

To protect operational staffing metadata in transit, plain `http://` endpoints are blocked by validation.

Authored by: YourMedSoft Product Engineering Team•Medically & Operationally Reviewed by: Marcus Chen, Lead Systems Architect
Last Updated: October 2026• Verified

Was this guide helpful?

Your feedback helps us continuously improve our documentation.