Configure access
In Organization → Workforce → Integrations, configure the connection and its provider mapping. An administrator rotates or issues the webhook secret through the existing connection settings. Use the organizationId and connectionId of that connection.
Cabinet route: /organizations/:organizationId/workforce/integrations. Required permission: workforce.integrations.manage; viewing requires workforce.integrations.view. A configured connection and enabled release/provider capabilities are prerequisites.
First successful workflow
Follow these steps in order. Open each method for its exact body, required headers and response schema.
- Create an external event identifier, provider event type and structured payload.
- Sign the stable recursively key-sorted JSON with an RFC3339 timestamp and the connection secret.
- POST the event; retain eventId, accepted and duplicate from the receipt.
State, retries and recovery
The same event identity with different content returns a replay conflict. Respect 413 size failures and Retry-After on 429. Acceptance records a verified provider event; it does not by itself promise every downstream HR field was synchronized.