# User Lifecycle Events via Webhooks

> 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.

- Source: https://docs.ghlcustomercare.com/docs/workflows/webhooks-workflow-actions/user-lifecycle-events-via-webhooks
- Section: Workflows / Webhooks Workflow Actions
- Reading time: 2 min
- Images: 1, each explained below

---
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.

---

**TABLE OF CONTENTS**

-   User Lifecycle Events via Webhooks
-   [Frequently Asked Questions](#frequently-asked-questions)
-   [Related Articles](#related-articles)

---

## **Supported User Lifecycle Events**

The following webhook events are now available:

-   `user.created`
-   `user.updated`
-   `user.deleted`

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)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155070955665/original/Q_ZgzvkBG3qQAWScA5DlmrlcvbCe9Xo8IQ.png)

**Event Delivery Behavior (image 1 of 1)**

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.
- What this covers: Automatic retry attempts for failed deliveries Event IDs for idempotency handling Delivery logs for troubleshooting and diagnostics
- Fields: Inbound webhook flow, Real-time event delivery, Third-party integration flow, Webhook-triggered automation behavior
- Next: Inbound webhook flow Real-time event delivery Third-party integration flow Webhook-triggered automation behavior

Full procedure:

1. Inbound webhook flow
2. Real-time event delivery
3. Third-party integration flow
4. 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.

---

## **Related Articles**

-   [Webhook: New SaaS Plan Created](https://docs.ghlcustomercare.com/docs/saas-configurator/saas-mode/webhook-new-saas-plan-created)

---

Documentation for GHL Customer Care. Support: support@ghlcustomercare.com