Trigger downstream workflows from HiBob Time Off webhook events
domain: hr-payroll · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Subscribe to Time Off module webhooks in Bob and select the events you need (timeoff.request.updated, .approved, .declined, .cancelled, .deleted, .imported, .setEndDate)
Note that timeoff.request.setEndDate fires only on Webhooks v2 and notifies you when an end date is added manually or automatically
Use the Time Off API's request/balance endpoints to pull full details, since the webhook payload carries only identifiers and change metadata
Route by policy or employee ID from the payload to update payroll or leave-tracking systems
Handle duplicate/out-of-order delivery, since webhook retries can resend events
Known gotchas
Webhooks v1 and v2 have different event names/payloads for the same underlying change - confirm which version a listener was built against
Events are retained for at least two working days (Fri/Sat/Sun excluded) to survive a temporary listener outage
The Time Off API can also adjust balances directly - webhooks tell you something changed, they don't replace polling for balance-adjustment audits
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?