integration-webhooks
Facilitates cross-platform messaging integration webhooks for serverless environments, ensuring reliable task processing and response handling.
Install this skill
Security score
The integration-webhooks skill was audited on Jun 10, 2026 and we found 29 security issues across 2 threat categories, including 1 high-severity. Review the findings below before installing.
Categories Tested
Security Issues
Template literal with variable interpolation in command context
| 196 | `${baseUrl}/_agent-native/integrations/<platform>/webhook`. For platforms |
Webhook reference - potential data exfiltration
| 2 | name: integration-webhooks |
Webhook reference - potential data exfiltration
| 4 | Cross-platform pattern for handling messaging integration webhooks (Slack, |
Webhook reference - potential data exfiltration
| 7 | work into a webhook handler. |
Webhook reference - potential data exfiltration
| 12 | # Integration Webhooks |
Webhook reference - potential data exfiltration
| 16 | Integration webhooks (Slack, Telegram, WhatsApp, email, Google Docs, etc.) must |
Webhook reference - potential data exfiltration
| 23 | Do not run agent loops inside the webhook handler itself. Do not rely on |
Webhook reference - potential data exfiltration
| 49 | function execution to do it.** SQL is the queue, a self-webhook is the trigger, |
Webhook reference - potential data exfiltration
| 55 | ┌──────────┐ 1. POST /integrations/:platform/webhook |
Webhook reference - potential data exfiltration
| 57 | └──────────┘ │ Webhook handler │ |
Webhook reference - potential data exfiltration
| 88 | The webhook handler does as little as possible. The fresh function execution |
Webhook reference - potential data exfiltration
| 97 | | `packages/core/src/integrations/webhook-handler.ts` | Verifies signature, parses, enqueues task, fires processor | |
Webhook reference - potential data exfiltration
| 109 | | POST | `/:platform/webhook` | Platform pings this. Verifies, enqueues, returns 200 quickly. | |
Webhook reference - potential data exfiltration
| 110 | | POST | `/_process-task` | Self-webhook target. Claims a task and runs the agent loop. | |
Webhook reference - potential data exfiltration
| 115 | | POST | `/:platform/setup` | Platform-specific setup (e.g. Telegram webhook registration). | |
Webhook reference - potential data exfiltration
| 166 | async verifyWebhook(event) { |
Webhook reference - potential data exfiltration
| 188 | 2. **Register it** in `getDefaultAdapters()` inside `plugin.ts`. The webhook, |
Webhook reference - potential data exfiltration
| 195 | 4. **Update the platform's webhook URL** to point at |
Webhook reference - potential data exfiltration
| 196 | `${baseUrl}/_agent-native/integrations/<platform>/webhook`. For platforms |
Webhook reference - potential data exfiltration
| 199 | Never hardcode bot tokens, signing secrets, verification tokens, webhook URLs, |
Webhook reference - potential data exfiltration
| 214 | loop. Those are handled by the shared webhook handler. |
Webhook reference - potential data exfiltration
| 241 | - **No persistent in-memory state.** The dedup map in the webhook handler is |
Webhook reference - potential data exfiltration
| 246 | - **Self-webhook URL resolution.** The processor URL is built from |
Webhook reference - potential data exfiltration
| 247 | `WEBHOOK_BASE_URL`, `APP_URL`, or `URL` env vars (with `localhost:3000` as |
Webhook reference - potential data exfiltration
| 253 | Even though the webhook handler does `fetch(processorUrl, ...)` without |
Webhook reference - potential data exfiltration
| 274 | 1. **Platform sent the webhook?** Check the platform's delivery logs (Slack |
Webhook reference - potential data exfiltration
| 275 | admin, Telegram `getWebhookInfo`). |
Webhook reference - potential data exfiltration
| 276 | 2. **Webhook handler returned 200?** If not, the platform retries — look for |
Webhook reference - potential data exfiltration
| 293 | - `actions` — When to use an action vs a webhook |