How to receive webhooks in Express Node.js receiver + reliable processing
A minimal Express endpoint is easy to add.
Production reliability (verification, retries, idempotency, backpressure) is the hard part — and Hooque makes that part simple.
Prefer the “no framework” version? Read receive webhooks in Node.js.
TL;DR
- Treat “receive webhooks in Express (Node.js)” as an ops problem, not just a route handler.
- Verify the request before parsing/side effects (use a verifySignature(...) stub, then implement provider verification).
- Return 2xx quickly; move work to a worker/queue to avoid timeouts and retries.
- Assume retries and design idempotency (dedupe by event id + unique constraints).
- Log + store raw payloads for replayable debugging.
- If you need one workflow across many providers, centralize ingest + standardize consumption.
Want the standard-library version and shared pitfalls? Read receive webhooks in Node.js .
Anti-patterns
- Doing business logic inline in the Express (Node.js) request handler.
- Parsing/transforming the body before verification (breaks signing inputs).
- Returning 2xx before authenticity is proven.
- Skipping idempotency (retries become double side effects).
Need deeper implementation details? Start with Webhook API.
Table of contents
Why it's hard in production
Frameworks help you build endpoints. They don’t solve retries, replay attacks, or backpressure by default.
Verify authenticity + stop replays
Use a verifySignature(...) stub here, then implement real verification + replay defense for each provider.
Assume retries (duplicates are optional)
Treat every delivery as at-least-once and make side effects idempotent (DB constraints, dedupe keys).
Don’t do work in the request path
Ack fast, process async. Otherwise timeouts, deploys, and spikes turn into missed webhooks.
Debug with real payloads
Save the exact body + headers so you can replay deterministically after a fix.
Add monitoring + alerts early
Track delivered vs rejected, processing latency, queue depth, and error rates.
Iterate locally without losing events
Tunnels help, but durable capture + replay removes the “my laptop was asleep” problem.
Minimal receiver (Express)
Keep verification as a stub here, then implement provider-specific verification + replay protection in the webhook security guide . For the standard-library version and shared pitfalls, see receive webhooks in Node.js .
import express from "express";
function verifySignature(_headers, _body) {
// don't compromise on security
// TODO: implement provider-specific signature verification
}
function processData(_body) {
// TODO: your business logic (DB writes, external API calls, etc.)
}
const app = express();
app.use(express.raw({ type: "*/*" })); // keep raw bytes for verification
app.post("/webhooks", (req, res) => {
verifySignature(req.headers, req.body); // Buffer
// What happens if it fails or times out?
// Most providers retry -> duplicates unless you designed idempotency.
processData(req.body);
// IMPORTANT: ack fast to avoid timeouts and duplicate deliveries.
res.status(200).send("ok");
});
app.listen(3000);Hooque turns any webhook into a reliable queue.
Non-obvious scenario: you can’t expose a port
In real deployments, the hardest part is often “where does this endpoint run?” (NAT, corporate networks, locked-down environments, short-lived preview deployments). Hooque decouples inbound receiving from processing so your Express app doesn’t need to be the public receiver.
The easy path: receive with Hooque + consume forever
Receive once (durably), then process from a queue. Your Express app doesn’t have to be the public receiver.
- Centralize provider-specific verification and reduce “raw body” pitfalls.
- Buffer spikes and deployments so you don’t drop deliveries.
- Use explicit Ack / Nack / Reject to control retries.
- Replay from the UI after a fix (no guessing what payload was sent).
Want the generic patterns? Read Webhook API and migrate to queue-based processing.
Hooque REST polling loop (runs forever)
Poll the queue forever and handle each event outside the provider’s request path.
// Node 18+ (fetch built-in)
const NEXT_URL = process.env.HOOQUE_QUEUE_NEXT_URL ?? "https://app.hooque.io/queues/<consumerId>/next";
const TOKEN = process.env.HOOQUE_TOKEN ?? "hq_tok_replace_me";
const headers = { Authorization: `Bearer ${TOKEN}` };
const sleep = (ms) => new Promise((r) => setTimeout(r, ms));
async function main() {
while (true) {
const msg = await getNextMessage();
if (!msg) {
await sleep(1000);
continue;
}
try {
await processData(msg.payload, msg.meta);
await ack(msg);
} catch (err) {
await nack(msg, err);
}
}
}
async function getNextMessage() {
try {
const resp = await fetch(NEXT_URL, { headers });
if (resp.status === 204) return null;
if (!resp.ok) {
console.error("next() failed:", resp.status, await resp.text());
return null;
}
const meta = JSON.parse(resp.headers.get("X-Hooque-Meta") ?? "{}");
const contentType = (resp.headers.get("content-type") ?? "").toLowerCase();
const raw = await resp.text();
const payload = contentType.includes("json") ? JSON.parse(raw) : raw;
return { payload, meta };
} catch (err) {
console.error("Worker connection err:", err);
return null;
}
}
async function processData(payload, meta) {
// Example real-life task: run a script on webhook events.
console.log("event:", meta?.messageId ?? meta?.deliveryId);
}
async function ack(msg) {
if (msg.meta.ackUrl) {
fetch(msg.meta.ackUrl, { method: "POST", headers }).catch(e => console.error("ack err", e));
}
}
async function nack(msg, err) {
const reason = err instanceof Error ? err.message : String(err);
const url = msg.meta.nackUrl ?? msg.meta.rejectUrl;
if (url) {
fetch(url, {
method: "POST",
headers: { ...headers, "Content-Type": "application/json" },
body: JSON.stringify({ reason }),
}).catch(e => console.error("nack err", e));
}
}
main();Hooque SSE stream consumer (runs forever)
Stream events in real time and reconnect forever on disconnects.
// Node 18+ — SSE consumer (no extra packages)
const STREAM_URL = process.env.HOOQUE_QUEUE_STREAM_URL ?? "https://app.hooque.io/queues/<consumerId>/stream";
const TOKEN = process.env.HOOQUE_TOKEN ?? "hq_tok_replace_me";
const headers = { Authorization: `Bearer ${TOKEN}`, Accept: "text/event-stream" };
const sleep = (ms) => new Promise((r) => setTimeout(r, ms));
async function main() {
for await (const msg of getMessageStream()) {
try {
await processData(msg.payload, msg.meta);
await ack(msg);
} catch (err) {
await nack(msg, err);
}
}
}
async function* getMessageStream() {
while (true) {
try {
const resp = await fetch(STREAM_URL, { headers });
if (!resp.ok) throw new Error(`stream failed: ${resp.status} ${await resp.text()}`);
if (!resp.body) throw new Error("missing response body");
const reader = resp.body.getReader();
const decoder = new TextDecoder();
let buf = "", event = null, dataLines = [];
while (true) {
const { value, done } = await reader.read();
if (done) break;
buf += decoder.decode(value, { stream: true });
while (true) {
const idx = buf.indexOf("\n");
if (idx < 0) break;
const line = buf.slice(0, idx).replace(/\r$/, "");
buf = buf.slice(idx + 1);
if (line.startsWith(":")) continue;
if (line === "") {
if (event === "message" && dataLines.length) {
try {
const rawMsg = JSON.parse(dataLines.join("\n"));
yield { payload: decodePayload(rawMsg), meta: rawMsg.meta ?? {} };
} catch { /* invalid json payload */ }
}
event = null;
dataLines = [];
continue;
}
if (line.startsWith("event:")) event = line.slice(6).trim();
if (line.startsWith("data:")) dataLines.push(line.slice(5).trimStart());
}
}
} catch (err) {
console.error("stream dropped:", err);
await sleep(2000);
}
}
}
function decodePayload(msg) {
let raw = msg.payload ?? "";
if (msg.encoding === "base64") {
raw = Buffer.from(raw, "base64").toString("utf8");
}
if ((msg.contentType ?? "").toLowerCase().includes("json")) return JSON.parse(raw);
return raw;
}
async function processData(payload, meta) {
// Example real-life task: run a script on webhook events.
console.log("event:", meta?.messageId ?? meta?.deliveryId);
}
async function ack(msg) {
if (msg.meta.ackUrl) {
fetch(msg.meta.ackUrl, { method: "POST", headers }).catch(e => console.error("ack err", e));
}
}
async function nack(msg, err) {
const reason = err instanceof Error ? err.message : String(err);
const url = msg.meta.nackUrl ?? msg.meta.rejectUrl;
if (url) {
fetch(url, {
method: "POST",
headers: { ...headers, "Content-Type": "application/json" },
body: JSON.stringify({ reason }),
}).catch(e => console.error("nack err", e));
}
}
main();FAQ
Answers tailored to Express, plus shared webhook production guidance.
How do I get the raw request body in Express?
General: Signature verification typically requires the raw body bytes (before JSON parsing). Ensure your middleware stack does not transform the body before verification.
How Hooque helps: With Hooque, provider delivery goes to a managed ingest endpoint. Your worker consumes from a queue using REST or SSE, so the “raw body vs parsed body” pitfall is mostly confined to ingest configuration.
What status code should I return for webhooks in Express (Node.js)?
General: Usually return a fast 2xx after validating authenticity and basic schema. Timeouts and 5xx commonly trigger retries.
How Hooque helps: Hooque acknowledges ingest immediately and persists the payload. Your worker acks/nacks/rejects explicitly after processing.
Do I need signature verification in Express (Node.js)?
General: Yes, unless the sender is fully trusted and on a private network. A public endpoint without verification is easy to forge and easy to replay.
How Hooque helps: Hooque can verify at ingest for supported providers or using generic strategies. Either way, your worker receives a normalized meta object and can stay focused on processing.
Why do I see duplicate webhook events in Express (Node.js)?
General: Retries are normal: timeouts, transient network failures, and 5xx responses all produce duplicates. Design idempotency around event ids and side-effect boundaries.
How Hooque helps: Hooque makes delivery outcomes explicit (ack/nack/reject) and provides replay/inspection so you can fix issues without guessing what was received.
How do I test webhooks locally in Express (Node.js)?
General: You can use a tunnel, but local dev still breaks on sleep, VPNs, clock skew, and signature-byte mismatches.
How Hooque helps: With Hooque you can avoid inbound locally: receive events into a durable queue and pull/stream to your laptop, then replay from the UI after changes.
Should I use REST polling or SSE streaming for webhook processing?
General: Use REST polling for simple batch workers and environments without long-lived connections. Use SSE for low-latency “process as it arrives” flows.
How Hooque helps: Hooque supports both: `GET /next` for polling and `GET /stream` for streaming. Both include meta with ready-to-call ack/nack/reject URLs.
Start processing webhooks reliably
Use Express for your app, and keep webhook processing as a simple run-forever consumer loop with explicit ack/nack/reject control.
No credit card required