Guide, 8 Nov 2026, read 8 Nov 2026
Webhooks from your HRIS to the rest of the stack
Three webhooks every People team needs
- Starter created: to the IT tool that provisions the laptop and the accounts, with the start date and the role.
- Leaver dated: to the same tool, with the last day, so access is removed at close of business rather than when the ticket is read.
- Field changed: manager, location, title, to the systems that hold a copy of the org chart.
A webhook as a workflow step
The difference between a webhook in the API and a webhook as a step is who can add it. Shapes's automations send webhooks and webhooks are workflow steps, on Plus; Rippling's webhooks are triggers and actions inside automations; on HiBob, BambooHR, Gusto and Workday the webhook is in the API or the changelog, which means an engineer wires it. A People partner building the leaver flow needs the step, not the endpoint.
What the receiving end needs
A webhook is only half a flow. The IT tool, the payroll and the finance system need to accept it and do something, and the HRIS should show whether they did: Shapes's integration sync log shows what every sync did (release note); on the other rows the evidence lives in the receiving tool. Test the pair with a fake leaver before the first real one.
Sources
- Shapes: automations can send webhooks, read 8 Nov 2026
- Shapes: see what every integration sync did, read 8 Nov 2026
- BambooHR: platform, read 8 Nov 2026
Last reviewed 8 Nov 2026.