Hr/people/created

event hr/people/created

Group: People Management › People · Operation ID: hr_people_created

A person was added. Carries the person id only; read the person for everything else.

Delivered when a person record is created, whether through POST people, the create-employee flow in the app, or an integration syncing people from a payroll or HR system.

A person is created together with their first job, so this event is normally followed by one or more hr/people/updated for the same business action. Both describe the same new person; read the person back and take the current state from there.

It fires for people whose employment has not started yet as well as for those already working: read status and startDate rather than assuming a new person is employed today.

The payload carries the identifier only. Read the person for names, employment dates, job, compensation and external identifiers.

There is no deleted event, and none is missing: people are never removed. Employment ends by setting endDate and status, which arrives as an update with the person still readable.

A delivery may be retried, so deduplicate on event.uuid, the id of the emission itself. Do not confuse it with event.data.id, which is the person.

Open in the interactive reference

Delivered as POST to the webhook endpoint of a subscription to hr/people/created.

Payload

Required, application/json: object.

Field	Type	Required	Description
`subscription`	object	yes	The subscription this delivery was made for.
`subscription.uuid`	string	yes	Stable identifier of the subscription.
`subscription.type`	string	yes	Transport the subscription delivers through; `webhook` for deliveries carried by this request.
`subscription.name`	string	yes	Authored name of the subscription.
`event`	object	yes	The emitted event being delivered.
`event.uuid`	string	yes	Stable identifier of this emission — the idempotency key for a receiver, since a delivery may be retried.
`event.identifier`	`"hr/people/created"`	yes	Public identifier of the event type.
`event.emittedAt`	string (date-time)	yes	When the event was emitted (ISO 8601).
`event.data`	hr_people_createdPayload	yes
`event.data.id`	string	yes

Example:

{
  "subscription": {
    "uuid": "<uuid>",
    "type": "<type>",
    "name": "<name>"
  },
  "event": {
    "uuid": "<uuid>",
    "identifier": "hr/people/created",
    "emittedAt": "2026-01-15T09:30:00.000Z",
    "data": {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
    }
  }
}