Objective
Sending every Conversations event to your server adds noise, and pre-event webhooks add latency to each event you subscribe to. This article helps you pick exactly which events Twilio delivers to your global webhook targets.
Product
Twilio Conversations
Environment
Twilio Console
Procedure
- In the Twilio Console, select Communications in the left sidebar.
- Select Conversations (classic), then Settings.
- Select the Global webhooks tab, then Webhook filtering.
- Under Pre-webhooks, select the events you want to be able to intercept, grouped by Conversations, Messages, Participants, and Users, for example onMessageAdd or onConversationUpdate.
- Under Post-webhooks, select the events you want delivered after they are committed, grouped by Conversations, Messages, Participants, Deliveries, and Users, for example onMessageAdded, onConversationStateUpdated, or onDeliveryUpdated.
- Select Save. A confirmation message reads Webhook filtering saved.
Additional Information
- Pre-webhooks let your services intercept events: any response other than HTTP 200 cancels the event. Post-webhooks are invoked asynchronously, after the event has been committed.
- Events you do not select here are assumed to have returned a 200 OK response, so they are never sent to your server.
- Pre-event and post-event names differ by tense, the pre-event is onMessageAdd while the matching post-event is onMessageAdded. Each checkbox describes what fires it.
- Some events are post-only. onDeliveryUpdated and onUserAdded cannot be intercepted with a pre-event webhook, and a user's reachability status update only triggers a post-event webhook.
- If your account is set up for more than one region, use the region selector on the page to change which region's filtering you are editing.
- If the configuration cannot be loaded, the page shows Unable to load webhook filtering and asks you to reload the page before saving, so your existing selections are not replaced.
This content was generated by AI and reviewed, edited, and verified by a human.