Added
Employee data Webhooks: Immediate access revocation
about 5 hours ago
You can now subscribe to a Webhooks v2 event that fires when a termination flow completes with Revoke access immediately selected. Use it when you need to know that the employee’s access to Bob has been revoked, without waiting for the termination effective date.
What’s new
- New webhook event:
employee.access.revoked.immediately(listed in Bob as Employee immediate access revocation). - The event is triggered when the termination flow completes, including all required approvals, with Revoke access immediately selected. If no approvals are required, it triggers when the flow completes. You don’t wait until the employee’s future termination date.
- Revoke access immediately appears only when it is enabled in that termination flow’s Additional steps settings, and the termination date is today or in the future. It is not available for past-dated terminations, where access is already removed immediately.
- Once all approvals are complete, access to Bob is revoked. The termination effective date and lifecycle timing stay the same:
employee.leftandemployee.inactivatedstill fire on the effective date as usual.
Why this matters
- Integrations can react as soon as Bob access is revoked, instead of waiting for midnight on the lifecycle effective date.
- Payroll and other effective-date processes can keep using lifecycle events. This event does not replace them.
How does this affect you
- Additive. No action is required unless you want to handle immediate access revocation.
- Do not use this event as the signal to terminate someone in payroll. Continue to rely on lifecycle events that are activated on the effective date.