Table of Contents
Once created, keeping your data in sync with Gladly will help optimize your systems. This guide has information on sync maintenance and Customer Profile edits.
Keeping your data in sync with Gladly #
We recommend this optional step for customers who wish to keep their main data in sync with Gladly.
Gladly provides a variety of webhooks that allow applications to be notified when a particular event occurs in Gladly.
For each webhook, Gladly requires:
- An endpoint Gladly can send a POST request to upon an event.
- Payload is in JSON format.
- Ability to process the event (store in your data warehouse).
Customer Profile edits #
To manage and integrate these, we recommend setting up the following webhooks in Gladly.
- CUSTOMER_PROFILE/UPDATED
- Receive a notification when there are updated Customer Profiles in Glady.
- You will need to use the GET customer API for further information on the Customer Profile object.
- CUSTOMER_PROFILE/CREATED
- Receive a notification when there are new Customer Profiles in Gladly.
- You will need to use the GET customer API for further information on the Customer Profile object.
- CUSTOMER_PROFILE/DELETED
- Receive a notification when there are deleted Customer Profiles in Glady.
- Gladly will send the deleted Customer ID in the webhook payload.
- CUSTOMER/MERGED
- Receive a notification when Customer Profiles are merged in Glady.
- You will need to use the GET customer API for further information on the Customer Profile object the Customer was merged to (represented as destinationCustomerId in the JSON payload).
