Skip to main content
Grow CRM emits three webhook event keys for the Team resource: 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 payload is a deliberate, fixed whitelist of profile fields. Credentials and security material — password hashes, session and password-reset tokens, two-factor secrets, last-known IP address, and payment-gateway customer ids — are never included and cannot be exposed by a future change to the underlying record. Personal preferences such as theme, language, and notification settings are also excluded.

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.
Compare role and status in the payload against your own copy if you need to react specifically to a permission change or a suspension.
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.
Deletion is a soft delete: the account row is kept for referential integrity, its status set to deleted, and its email, password, role, and avatar cleared. Treat team.deleted as final — the member cannot log in again and will not appear in the team list.