FAfactorialhr
Webhooks

Teams > Membership > Creates

Subscription_type: teams/membership/create. Triggered when a direct membership is created — one placing the employee on that team itself, as opposed to a row they get through a sub-team. Fires whether the membership is created through the API or from Factorial. Inherited rows created afterwards in ancestor teams (nested teams) do not trigger this event; read the memberships endpoint if you need to track them. Nor is this a complete feed of additions, and which event an addition produces depends on the side it is made from. Adding people to a team emits teams/membership/bulk_upsert and not this event; adding a team to a person emits both, so bulk_upsert is the wider of the two feeds. For companies with nested teams there is a third shape: the employee profile and imports set the complete set of teams the employee belongs to, which emits nothing at all, so those rows are only observable by reading the memberships endpoint.

postWebhookWebhooks > Teams > Membership > Creates

Payload

idstring required

Membership ID

company_idstring

Company ID of the membership

employee_idstring required

Employee ID of the membership

team_idstring required

Team ID of the membership

leadboolean required

Whether the employee is a lead of the team or not

source_team_idsstring[] required

IDs of the teams this membership originates from (nested teams). In a company with nested teams, a direct membership includes the team itself; an inherited one, the sub-team(s) where the employee is a direct member. Only populated on reads that compute source attribution — reads filtered by a single team, or by a single employee with with_source_attribution enabled. Empty otherwise, including create, update and delete responses, and always empty for companies without nested teams. An empty array does not distinguish "computed and genuinely empty" from "not computed for this read" or "could not be computed", so only apply attribution-dependent logic to a read you explicitly shaped for it. A team-anchored read stops attributing above roughly a thousand members of the filtered team: past that the attribution is not computed at all and every row comes back empty, behind a normal 200.

parent_team_idsstring[] required

IDs of the ancestor teams that receive an inherited membership through this row (nested teams) — the teams this membership rolls up into. Populated under the same conditions as source_team_ids; empty otherwise.

directboolean

Whether the employee is a direct member of the team (nested teams). Always present. true means direct member; false means the row exists only through inheritance from a sub-team; null means not computed for this read. Only computed on reads filtered by a single employee with with_source_attribution enabled — always null otherwise, including create, update and delete responses and companies without nested teams. null is also returned when directness could not be resolved for a transient reason, even with with_source_attribution enabled, so never treat null as false — retry the read instead.

Example payload

{
  "id": "1",
  "company_id": "1",
  "employee_id": "12",
  "team_id": "3",
  "lead": true,
  "source_team_ids": [
    "3"
  ],
  "parent_team_ids": [
    "2"
  ]
}

Response

Return a 200 status to indicate that the data was 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.