Developer guide
If your system already uses webhooks internally, ParseForce lets email enter that same event flow. Incoming messages become webhook posts with parsed JSON and delivery metadata.
This page is for teams that do not want to poll inboxes or bolt parsing logic onto mail clients. Email becomes another signed event producer in the system.
Webhook integrations get tricky when retries, duplicates, and signature verification are missing. Those details matter more than the parsing demo.
Webhook delivery is a good fit when email is only one producer in a larger event-driven system.
Example webhook payload shape for this workflow.
json
{
"event": "email.parsed",
"mailboxId": "mbx_ship_19",
"parsedData": {
"tracking_number": "BLF-90211",
"carrier": "BlueLine Freight",
"status": "Delivered",
"delivery_time": "2026-02-26T09:42:00",
"recipient": "Marco Alvarez"
},
"rawEmail": {
"from": "updates@bluelinefreight.com",
"subject": "Shipment update"
}
}Minimal Node.js example for consuming ParseForce output.
node.js
import crypto from "crypto";
import express from "express";
const app = express();
app.post(
"/webhooks/parseforce",
express.raw({ type: "application/json" }),
(req, res) => {
const signature = req.header("x-parseforce-signature");
const expected = crypto
.createHmac("sha256", process.env.PARSEFORCE_WEBHOOK_SECRET)
.update(req.body)
.digest("hex");
if (!signature || !crypto.timingSafeEqual(
Buffer.from(signature, "hex"),
Buffer.from(expected, "hex"),
)) {
return res.status(401).end();
}
const payload = JSON.parse(req.body.toString("utf8"));
console.log(payload.event, payload.parsedData.tracking_number);
return res.status(204).end();
},
);
app.listen(3000);Related guides
Explore related ParseForce pages for webhook delivery, schema design, and implementation details for adjacent email automation workflows.