📄️ Set up a webhook
To set up a webhook in Cue you will need the Workspace Owner role. Then you can open your workspace and navigate to Settings > Webhooks > Create Webhook.
📄️ Verifying requests
You can verify inbound requests from our webhooks using HMAC SHA256 verification. Once you've created a webhook you'll see a notice showing you the secret value that you can use for for verifying requests from us. If you need to find the secret again at a later stage you can also find it on the edit page of the webhook.
📄️ Message events
For a WhatsApp customer who has hidden their phone number, from on inbound messages and to on outbound messages and status updates contain a BSUID such as GB.13491208865530274191 instead of a phone number. See WhatsApp usernames and BSUIDs for the scenarios, and for the contacts and requestcontact_info message types.
📄️ Ticket events
Below is an overview of the different webhook payloads that customers can receive for ticket events from the Cue platform. The key ticket events include ticketcreated, ticketclosed, and ticketupdated_. Each event provides a specific payload that contains relevant information about the ticket's status and associated data.
📄️ WhatsApp usernames and BSUIDs
WhatsApp users can choose a username and hide their phone number from businesses. When a user does this, Meta identifies them to your business with a Business-Scoped User ID (BSUID) instead of a phone number. A BSUID looks like GB.13491208865530274191: a two-letter country code, a dot, and up to 125 letters and digits. It is unique to the user and your business, and Meta issues a new one if the user changes their phone number.