team.created, team.updated, and team.deleted. Use these events to provision accounts in connected systems, detect role and status changes, and clean up access when a team member is removed. There is no .sundry or .activity key — every change to a team member arrives as team.updated, and team members carry no child records. These events cover team members only; client contacts are not included.
The webhook envelope structure, delivery behaviour, and retry logic are documented in Introduction. Signature verification is covered in Verification. Those conventions apply to every event on this page and are not repeated here.
The team member object
team.created and team.updated carry this shape — flat inside data for .created, or nested under data.team_member for .updated.
team.created
Fires when a team member is added. data is the full team member object.
The new member is also emailed a generated password at this point. That password is never included in the payload.
team.updated
Fires on any change to a team member. Read data.change to determine what changed; data.team_member contains the full team member object reflecting the new state.
A team member changing their own preferences does not fire an event.
team.deleted
Fires after a team member is removed. Because the record no longer exists at delivery time, data contains only the member’s id.
