Webhooks

Webhooks let WhosOff automatically send real-time updates to other systems whenever key events happen in your account. They're ideal if you want your HR tools, scheduling systems, internal dashboards, or automation platforms to stay perfectly in sync with staff leave and overtime activity - without manual work.

Full details of Webhooks within WhosOff are available at www.whosoff.com/features/webhooks/. 

If you've ever received an email notification after someone books leave or overtime, you already understand the basic idea. A webhook works the same way, except instead of sending an email to a person, WhosOff sends structured data to another application so it can react instantly.
 

HOW WEBHOOKS WORK

When an event occurs in WhosOff - such as a leave request being created, approved, declined or cancelled - WhosOff sends a secure message (a "payload") to a URL you specify.

Your receiving system can then use that data to:

• Update a rota or resource plan
• Trigger a workflow in tools like Zappier, Make, or custom internal systems
• Notify a team channel
• Sync absence data into HR or payroll software
• Mark someone as unavailable in a project management tool

What happens next is entirely up to the system receiving the webhook.
 

WHO WEBHOOKS ARE FOR

Webhooks are typically setup by someone with technical knowledge - such as a developer, IT admin, or anyone familiar with APIs and automation tools.

That said, many modern platforms make webhook setup straightforward, so even non-technical users can often configure them with clear instructions from the receiving system. 
 

SETTING UP WEBHOOKS IN WHOSOFF

1. Go to Administration > Company Settings
   You'll find the Webhooks section inside of your company settings section, under the Webhooks tab
    
2. Add your Webhook address
   Most third-party systems that support webhooks will provide you with a unique URL (sometimes called an "endpoint").
   Copy that URL and paste it into the Webhook URL field in WhosOff.
   If you're unsure where to find it, check the documentation for the system you're connecting to - or contact their support team.
    
3. Use your Headerkey and Secret (Optional but recommended)
   Choose a Header Key name and Secret to send with  every webhook event so your server can verify the request really came from WhosOff.
   Your technical team or receiving system will know how to validate this.
    
4. Security Method
   Choose whether to send payloads using standard security, or Sha256 with Payload
     
5.  Enable or Disable Webhooks anytime
   You can toggle your webhook on or off without deleting the configuration - useful for testing or maintenance.
    

 EVENTS WHOSOFF SENDS

WhosOff sends webhook events for key actions, including (but not limited to):

• Leave request created
• Leave request approved
• Leave request declined
• Leave request cancelled
• Overtime request created
• Overtime request approved
• Overtime request declined
• Overtime request cancelled

You'll also see a log of recent webhook events in the Company Log area of Reports within your account, including timestamps and delivery status.
 

TESTING YOUR WEBHOOK

WhosOff allows you to send a test event to your configured URL. This helps you confirm your receiving system is working before going live.

Example webhook event 

{ "event_id": "20",
   "event_type": "leave.created",
   "created_At": "2026-02-27 11:46:41",
   "data": {
   "id": "10049172",
              "name": "Holiday",
               "staff": "Hugh Zoff",
              "approver": "",
              "status": "pending",
              "start_date": "2026-03-28 00:00",
              "end_date":"2026-03-29 00:00"
          }
}

TROUBLESHOOTING AND SUPPORT

If you're unsure hwo to configure your receiving system, your best first step is to check that system's documentation.

If you need help with the WhosOff side of things, our support team is always happy to assist.