HIhibob
Tasks Webhooks

Task triggered webhook

Sent when a task list is triggered and one or more general tasks are created. The payload includes requestedForEmployeeId (the employee the tasks are for), workflowId, pivotDate, and toDoIds (task IDs).

Best practice: Treat the event as a notification. Call the <a href="https://apidocs.hibob.com/reference/get_tasks-people-id" target="_blank">Read tasks of a specific employee</a> endpoint with requestedForEmployeeId to retrieve full task details. For request and response examples, see <a href="https://apidocs.hibob.com/reference/api-calls-for-webhook-events#task-events" target="_blank">API call for Task events</a>.

In the right panel, open Examples and select Payload Example to see a real payload.

postWebhooktaskAssign

Headers

bob-signaturestring required
Example:EQScIBkAtTKFW0ictgt5zzOsqIc2+xGEsM88jOdLuW4CM/a3gLEfrKV+IC5IHx0xbirzLKPIfaZjCGwzuiyI8w==

Base64-encoded signature sent with each webhook request. Use it to verify that the request came from Bob. To verify webhook authenticity, see <a href="https://apidocs.hibob.com/reference/getting-started-webhooks#how-does-bob-calculate-the-signature" target="_blank">How does Bob calculate the signature</a>.

Payload

companyIdnumber required

The company ID

type'todo.assign' required

The event type for task assignment

triggeredBystring required

The backend-id of the employee that triggered the event or 'system' for events triggered automatically by the system

triggeredAtstring date-time required

The timestamp when the event occurred

versionstring required

The webhook version

Response

Webhook received successfully

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.