Webhook automation templates
Every template solves a real automation problem — duplicate webhooks, provider timeouts, silent failures, rate limits. Study the setup, then clone it into your account free.
ecommerce
monitoring
Uptime monitor with Slack alerts
Checks your endpoint every 5 minutes. Healthy responses stay silent; a failure (after 2 retries) pings Slack with the error. A free UptimeRobot on your own terms.
Watch any API for changes
Polls an API every 15 minutes, extracts one value (price, stock, version — your pick), and posts to Discord only when the value actually changes. Change detection is a dedup gate: same value = silence.
marketing
ai
AI error summaries your team actually reads
Raw error webhooks become one plain-English sentence plus the most likely cause, posted to Slack. Filters out non-errors first so the channel stays quiet.
GitHub release → AI-written announcement
When you publish a release, AI drafts a short friendly announcement from the release notes and posts it to Discord with the link. Signature-verified.
AI lead scoring — hot leads straight to Slack
AI classifies every inbound lead as hot, warm, or cold. Hot pings sales in Slack immediately, warm goes to the nurture sheet, cold is just logged. No SDR tooling required.
payments
Stripe failed-payment recovery (dunning-lite)
invoice.payment_failed → wait an hour for card retries to settle → email the customer a payment-update nudge → count failures and escalate to finance on the 3rd. Recovered revenue, zero dunning SaaS.
Duplicate-proof Stripe payment processing
Stripe delivers at-least-once — duplicates will happen. Verify the signature, drop events you have already seen (24h window on body.id), keep only successful payments, deliver with retries.
reliability
n8n safety net — never miss a webhook again
Point providers at Requex instead of n8n directly. Every event is archived first, then forwarded to n8n with retries. If your n8n instance is down, you get a Slack alert and the payload waits safely for replay.
Never lose a failed delivery
The silent failure is the expensive one. When delivery fails after all retries, the error path alerts your team in Slack and archives the full payload to a Requex inbox so you can replay it later.
Respond instantly, process in the background
Providers retry when you respond slowly (Slack: 3s, Shopify: 5s) — and retries mean duplicates. This ACKs with 200 immediately, then does the slow work with retries, and alerts Slack only if everything fails.
integrations
notifications
Error burst alert, not error spam
Alerting on every error trains everyone to ignore alerts. This counts errors in workflow state and pings Slack once, on the 10th — one signal instead of ten pages.
Email me only when it matters
The simplest automation done right: filter on body.status = failed, then email. Everything else passes through silently.
scheduled
delivery
chatops
data
Process array payloads item by item
Your webhook delivers a list; your API wants one call per item. The iterator walks body.items one at a time, keeps going on individual failures, and each item gets retry-protected delivery.
CSV webhook → Google Sheets rows
Reports arrive as CSV strings; Sheets wants rows. Parse the CSV (header-aware), iterate row by row, append each to a sheet.