Webhook Alerting — Forward Events Anywhere
Receive webhooks from Stripe, GitHub, Shopify, or any provider and instantly route them as alerts to Slack, Discord, SMS, or email.
Quick Answer
Use Requex as a webhook receiver and configure forwarding rules to route incoming events to any destination — Slack incoming webhooks, Discord bots, Twilio SMS endpoints, or email relay APIs. No custom server code required; set up in minutes.
Why Route Webhooks Through Requex
Many webhook providers — Stripe, GitHub, Shopify, Twilio — send events to a single URL. If you want to route those events to multiple destinations (Slack for the team, your database, a monitoring dashboard), you'd normally need to build a custom server that receives the webhook and fans out the delivery.
Requex's forwarding rules do this without any code. Configure up to multiple forwarding destinations per webhook, and Requex delivers to all of them in parallel — with automatic retries, delivery logs, and real-time payload inspection for debugging.
Alert Destinations
| Destination | How to Connect | Best For |
|---|---|---|
| Slack | Slack incoming webhook URL | Team alerts, on-call notifications |
| Discord | Discord channel webhook URL | Community alerts, dev team notifications |
| SMS (Twilio) | Twilio messaging REST API | Critical alerts, on-call escalation |
| Email (SendGrid) | SendGrid Mail Send API | Customer notifications, audit logs |
| PagerDuty | PagerDuty Events API v2 | Production incident management |
| Custom HTTP endpoint | Any HTTPS URL | Internal microservices, databases, Zapier |
Setting Up Slack Alerting — Step by Step
- 1
Create a Slack incoming webhook
Go to your Slack workspace → Apps → Incoming Webhooks → Add to Slack. Choose a channel and copy the webhook URL — it looks like
https://hooks.slack.com/services/T.../B.../... - 2
Get your Requex endpoint
Open requex.me and copy the unique HTTPS URL. This is the URL you'll register with your webhook source (Stripe, GitHub, etc.).
- 3
Add a forwarding rule
In Requex, open the Forwarding tab. Add a new rule with the Slack webhook URL as the destination. Set the method to POST and enable body pass-through so Requex forwards the original payload.
- 4
Register your Requex URL with the source
Add your Requex URL as the webhook endpoint in Stripe, GitHub, or whichever provider you're using. When an event fires, Requex receives it, shows you the payload, and forwards it to Slack.
Example Slack Forwarding Rule Config
Note: Slack's incoming webhook API expects a specific JSON format with a text or blocks field. If your original webhook payload doesn't match this format, you'll need a small transformation layer (a serverless function or Zapier) to reshape the body before it reaches Slack.
For Discord, the incoming webhook API expects content or embeds. The same transformation consideration applies. For simpler alerting pipelines, consider forwarding to a lightweight serverless function that reshapes the payload and then calls Slack or Discord.
Filtering by Event Type
If you only want to alert on specific events — for example, only Stripe payment_intent.payment_failed events rather than all payment events — you have two options:
- →Filter at the source — Register multiple Stripe webhook endpoints, one per event type, each pointing to a different Requex URL with its own forwarding rule.
- →Filter in a serverless function — Forward everything from Requex to a small function that checks the event type field and only calls Slack for the events you care about.
Related Resources
Start Testing Webhooks Now
Generate your unique URL and test webhooks instantly. Free, no signup.
Open Webhook Tester →