Learn how to use GHL Customer Care user lifecycle webhook events including user.created, user.updated, and user.deleted for real-time integrations and automation.
Assistants need to reach this page over the internet. While it is only running on your machine, these two buttons will not be able to load it.
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
GHL Customer Care now supports webhook events for user lifecycle activity, allowing developers to receive real-time notifications whenever users are created, updated, or deleted.
These webhook events help external systems stay synchronized without relying on polling or manual checks.
These events are triggered whenever a user is created, updated, or removed inside GHL Customer Care.
Available Webhook Events
user.created
Triggered when a new user is created.
Common use cases:
Provisioning external accounts
Syncing users to third-party systems
Triggering onboarding workflows
user.updated
Triggered when user information changes.
Common use cases:
Syncing profile updates
Updating permissions or roles
Keeping external CRMs synchronized
user.deleted
Triggered when a user is deleted.
Common use cases:
Removing external access
Revoking permissions
Cleaning up downstream systems
Event Delivery Behavior
Webhook events are delivered in real time whenever supported user lifecycle actions occur.
Additional delivery features include:
Automatic retry attempts for failed deliveries
Event IDs for idempotency handling
Delivery logs for troubleshooting and diagnostics
Event Delivery Behavior (image 1 of 1)What this shows Automatic retry attempts for failed deliveries Event IDs for idempotency handling Delivery logs for troubleshooting and diagnosticsWhat this showsIllustrates the "Event Delivery Behavior" section of "User Lifecycle Events via Webhooks".This screenshot appears in the "Event Delivery Behavior" section of "User Lifecycle Events via Webhooks". The text alongside this image reads: Automatic retry attempts for failed deliveries Event IDs for idempotency handling Delivery logs for troubleshooting and diagnostics. This part of the guide covers 4 fields, listed below. Immediately after, the guide continues: Inbound webhook flow Real-time event delivery Third-party integration flow Webhook-triggered automation behavior.Image 1 of 1What this coversAutomatic retry attempts for failed deliveries Event IDs for idempotency handling Delivery logs for troubleshooting and diagnostics
Fields in this part of the guideInbound webhook flowReal-time event deliveryThird-party integration flowWebhook-triggered automation behavior
Next stepInbound webhook flow Real-time event delivery Third-party integration flow Webhook-triggered automation behaviorAll 4 steps in this procedure
Inbound webhook flow
Real-time event delivery
Third-party integration flow
Webhook-triggered automation behavior
This screenshot demonstrates:
Inbound webhook flow
Real-time event delivery
Third-party integration flow
Webhook-triggered automation behavior
Webhook Security
User lifecycle webhooks use signed requests to help verify event authenticity.
Security features include:
HMAC request signing
Event identifiers for duplicate prevention
Retry handling for failed webhook deliveries
Always validate webhook signatures before processing incoming webhook events.
Common Use Cases
Developers commonly use these events to:
Sync users across multiple platforms
Automate onboarding and offboarding
Maintain analytics and reporting pipelines
Trigger provisioning workflows
Keep external systems updated in real time
Frequently Asked Questions
Q: What user events are supported? A: GHL Customer Care currently supports user.created, user.updated, and user.deleted.
Q: Are webhook deliveries retried if they fail? A: Yes. Failed webhook deliveries are automatically retried automatically.
Q: Are webhook requests signed? A: Yes. User lifecycle webhooks support HMAC request signing.
Q: Can webhook events be used for external user synchronization? A: Yes. These events are designed to support real-time synchronization across external systems.
Q: Do webhook events include unique event IDs? A: Yes. Event IDs are included to support idempotent processing and duplicate prevention.
