Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 03:37 UTC
| 1 | --- |
| 2 | title: "Webhook V3 Now Default for New Organizations" |
| 3 | description: "All newly created organizations will now use Webhook Payload V3 by default" |
| 4 | date: "2026-02-15" |
| 5 | --- |
| 6 | |
| 7 | As announced in our [Webhook Payload V3 lookahead](/docs/changelog/2025/12/30), **Webhook Payload V3 is now the default for all newly created organizations**. |
| 8 | |
| 9 | ## What's Changed? |
| 10 | |
| 11 | Starting today, every new organization created on Composio will automatically use **Webhook Payload V3** for all webhook and Pusher deliveries. This means new organizations benefit from the improved webhook structure out of the box, with no additional configuration needed. |
| 12 | |
| 13 | ### For New Organizations |
| 14 | |
| 15 | - Webhook payloads follow the [Standard Webhooks specification](https://github.com/standard-webhooks/standard-webhooks/blob/main/spec/standard-webhooks.md) |
| 16 | - Trigger data is cleanly separated from Composio metadata via the `metadata` and `data` fields |
| 17 | - The `x-composio-webhook-version: V3` header is included in all webhook deliveries |
| 18 | |
| 19 | ### For Existing Organizations |
| 20 | |
| 21 | Nothing changes for existing organizations. If your organization was created before today: |
| 22 | |
| 23 | - You will continue to receive webhooks in your current format (V1 or V2) |
| 24 | - You can opt-in to V3 at any time through your [project settings](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=changelog-02-15-26-webhook-v3-default-new-orgs) |
| 25 | |
| 26 | ## V3 Payload Recap |
| 27 | |
| 28 | ```json |
| 29 | { |
| 30 | "id": "msg_a1b2c3d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d", |
| 31 | "timestamp": "2026-02-15T12:00:00.000Z", |
| 32 | "type": "composio.trigger.message", |
| 33 | "metadata": { |
| 34 | "log_id": "log_TpxVOLXYnwXZ", |
| 35 | "trigger_slug": "GMAIL_NEW_GMAIL_MESSAGE", |
| 36 | "auth_config_id": "ac_aCYTppZ5RsRc", |
| 37 | "connected_account_id": "ca_cATYssZ5RrSc", |
| 38 | "trigger_id": "ti_JZFoTyYKbzhB", |
| 39 | "user_id": "your-user-id" |
| 40 | }, |
| 41 | "data": { |
| 42 | // Clean trigger data without Composio metadata |
| 43 | } |
| 44 | } |
| 45 | ``` |
| 46 | |
| 47 | ## How to Switch to V3 (Existing Organizations) |
| 48 | |
| 49 | 1. Go to your project settings in the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=changelog-02-15-26-webhook-v3-default-new-orgs) |
| 50 | 2. Navigate to the Webhooks section |
| 51 | 3. Select **Webhook Payload Version: V3** |
| 52 | 4. Update your webhook handlers using the [migration guide](/docs/changelog/2025/12/30#migration-guide) |
| 53 | 5. Test thoroughly before enabling in production |
| 54 | |
| 55 | <Callout type="info"> |
| 56 | We strongly recommend all organizations migrate to V3 for a better developer experience, standards compliance, and access to new features like [connection expiry events](/docs/changelog/2026/02/06#new-event-composioconnectedaccountexpired). |
| 57 | </Callout> |