24
25
## How do I set up Slack event webhooks?
26
27
-Enable Event Subscriptions in your Slack app. Set the Request URL to `https://backend.composio.dev/api/v3.1/trigger_instances/slack/default/handle`. Add events (e.g., `reaction_added`) to Subscribe to Bot Events and save. If using the Slackbot integration, add the bot to the channels you want to monitor.
27
+**If you use Composio-managed Slack credentials**, nothing to set up — the webhook endpoint is already provisioned for your project. Create the trigger and you're done.
28
+
29
+**If you bring your own Slack OAuth app**, configure a webhook endpoint once per OAuth app. Step-by-step:
30
+
31
+1. **Create the endpoint:**
32
+
33
+ curl -X POST "https://backend.composio.dev/api/v3.1/webhook_endpoints" \
34
+ -H "x-api-key: <YOUR_COMPOSIO_API_KEY>" \
35
+ -H "Content-Type: application/json" \
36
+ -d '{ "toolkit_slug": "slack", "client_id": "<YOUR_SLACK_CLIENT_ID>" }'
37
+
38
+ Save the `id` and `webhook_url` from the response.
39
+
40
+2. **Store your signing secret on the endpoint** (Slack app → Basic Information → App Credentials → Signing Secret):
41
+
42
+ curl -X PATCH "https://backend.composio.dev/api/v3.1/webhook_endpoints/<ENDPOINT_ID>" \
43
+ -H "x-api-key: <YOUR_COMPOSIO_API_KEY>" \
44
+ -H "Content-Type: application/json" \
45
+ -d '{ "data": { "webhook_signing_secret": "<SIGNING_SECRET>" } }'
46
+
47
+3. **For DMs, private channels, and reactions, also store an app-level token** (Slack app → Basic Information → App-Level Tokens, scope `authorizations:read`):
48
+
49
+ curl -X PATCH "https://backend.composio.dev/api/v3.1/webhook_endpoints/<ENDPOINT_ID>" \
50
+ -H "x-api-key: <YOUR_COMPOSIO_API_KEY>" \
51
+ -H "Content-Type: application/json" \
52
+ -d '{ "data": { "app_token": "xapp-..." } }'
53
+
54
+4. **Set Slack app → Event Subscriptions → Request URL** to the `webhook_url` from step 1. Composio responds to Slack's `url_verification` challenge automatically.
55
+
56
+5. **Subscribe to the events you need** under Event Subscriptions and save.
57
+
58
+If you're using the Slackbot integration, add the bot to the channels you want to monitor.
59
+
60
+For the full reference (PATCH vs POST update semantics, listing endpoints, troubleshooting), see [Configuring the webhook endpoint](https://docs.composio.dev/docs/setting-up-triggers/creating-triggers#configuring-the-webhook-endpoint).
61
62
## Why am I getting scope errors on Slack?
63
69
70
## Why aren't my Slack triggers working?
71
39
-Provide the Verification Token or signing secret in the auth config so Composio can validate incoming events.
72
+If you bring your own Slack OAuth app, the most common cause is a missing or wrong **signing secret on the webhook endpoint** — every inbound request fails signature verification with `400`, and Slack auto-disables the URL after about 36 hours of consecutive failures. Confirm the endpoint is set up correctly:
73
+
74
+ curl "https://backend.composio.dev/api/v3.1/webhook_endpoints" \
75
+ -H "x-api-key: <YOUR_COMPOSIO_API_KEY>"
76
+
77
+Look for an endpoint with your `client_id` and a populated `verified_at`. If `verified_at` is null, the URL hasn't completed Slack's `url_verification` handshake yet — re-save the URL on Slack app → Event Subscriptions. If you don't see an endpoint at all, follow [How do I set up Slack event webhooks?](#how-do-i-set-up-slack-event-webhooks) above.
78
+
79
+For DMs, private channels, or reactions, also confirm the endpoint has an `app_token` set. See [Triggers troubleshooting](https://docs.composio.dev/docs/troubleshooting/triggers) for the full list of failure modes.
80
81
---