Teams > Team > Moves

webhook

Webhooks > Teams > Team > Moves

Subscription_type: teams/team/move. Triggered when a team is moved under a different parent team (or to the root of the hierarchy), whether the move is made through the API or from Factorial. This event belongs to the 2026-10-01 contract, where the payload carries the public team fields plus the resulting position — parent_team_id is the new parent (null when moved to the root) and depth its new level. A subscription pinned to an earlier version still receives the event, but without those two fields, and the hierarchy is absent from the teams read on those versions too, so upgrading is the only way to obtain the new position rather than infer it. The memberships re-propagated to the new ancestors are created afterwards and emit no membership events of their own, so a subscriber tracking who belongs where has to read the affected sub-tree.

Payload

Callback payload

string

required

Unique identifier of the team

name

string

required

Human-readable name of the team (e.g. "Engineering")

description

string

Free-text description of the team

avatar

string

URL of the team's avatar image (null when the team has none)

employee_ids

array of strings

IDs of the employees who are members of this team

employee_ids

lead_ids

array of strings

IDs of the employees who are leads of this team (subset of employee_ids)

lead_ids

company_id

string

required

ID of the company this team belongs to

depth

integer

Depth of this team in the nested-team hierarchy: 1 for a top-level team, 2 for its children, and so on. Returned by read, create and move; null on update and delete, which do not change the hierarchy, and always null for companies without nested teams.

parent_team_id

string

ID of the parent team this team is nested under (null for a root team). Returned by read, create and move; null on update and delete, which do not change the hierarchy, and always null for companies without nested teams.

Response

200

Return a 200 status to indicate that the data was received successfully