Webhooks

Events are sorted into groups: Contacts, Conversations, Messages, Handovers to your team, AI agent, Bookings, Reminders, Orders, Products, Calls, Campaigns, Forms, Account and channels, and Workspace settings. Open a group and tick single events, or press Select all to take the whole group. Not sure where something lives? Type in the search box, for example "booking" or "tag". Tap any event to see an example of exactly what Entagl will send. Some events also let you choose where they come from, so you could get only the bookings your AI made and skip the ones your team typed into the calendar.

Incoming message and Outgoing message fire for every single message. On a busy account that can be thousands a day. That's why Select all skips them: you have to tick each one yourself, next to a warning. Turn them on only if the tool on the other end can handle that many. If you just want to know when a chat starts or ends, Conversation opened and Conversation closed are much quieter.

Two switches decide how much customer information leaves Entagl. Include message content adds what customers wrote: messages, notes and call summaries. Include contact details adds the customer's name, phone number and email. Both start off. You still get every event without them, with a contact ID where the details would be. Only the workspace owner or an admin can turn them on, and only do it if the receiving tool is allowed to store customer data. On a HIPAA workspace customer data is never sent, whatever the switches say.

Tools and developers can register their own webhooks through the Entagl API, and they show up under Connected apps by themselves. For each one you see how many events it listens to and when it last got one. You can open its Recent deliveries, Pause and Resume it, or Remove it. Make scenarios have their own page: Channels → Make.

Press Recent deliveries to see the last 50 events Entagl tried to send, newest first. Each one shows whether it arrived, the answer your tool gave (like 200 or 500), how many tries it took, and when the next try is due. When a delivery has failed for good, fix the problem on your side and press Send again. Entagl sends it within a few seconds.

If your tool is down or answers with an error, Entagl tries again after 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours and 24 hours. That's about 31 hours before a delivery is marked as failed. If a connected app keeps failing for 3 days straight, Entagl pauses it and sends the workspace owner a notification. Fix the tool, then press Resume. If Make reports that a scenario's webhook no longer exists, Entagl stops sending to it right away.

Every request carries a signature in the X-Entagl-Signature header, made with your signing secret. Your developer uses it to prove the request came from Entagl and that nobody changed it on the way.

• Connected apps and webhooks created through the API send t=1767225600,v1=5257a869…. The t part is when it was sent, in seconds. Each v1 is an HMAC-SHA256 of the text timestamp.body (the t value, a dot, then the raw request body), made with your secret. Reject any request whose t is more than 5 minutes old, so an old request can't be replayed. Right after a secret change you may see two v1 values: accept the request if either one matches.
• The webhook you set up on this page sends sha256= followed by an HMAC-SHA256 of the raw request body.