Webhooks

Overview

Webhooks let you receive an HTTP POST notification at your own endpoint every time a conversion completes. Use them to trigger workflows in Zapier, Make, n8n, or any custom backend.

Webhooks are a PRO plan feature. Each user can register up to 3 webhook endpoints.

Setup

Open the Web2MD extension and go to Settings.
Scroll to the Webhooks section.
Enter your endpoint URL and click Add Webhook.
Copy the signing secret — you will need it to verify incoming requests.

Payload

When a conversion completes, Web2MD sends a POST request to your endpoint with the following JSON body:

{
  "event": "conversion.completed",
  "data": {
    "conversionId": "conv_abc123",
    "url": "https://example.com/article",
    "title": "Example Article",
    "markdownLength": 4820,
    "timestamp": "2026-03-21T12:00:00.000Z"
  }
}

Field	Type	Description
`event`	`string`	Always `"conversion.completed"`
`data.conversionId`	`string`	Unique ID for this conversion
`data.url`	`string`	The source URL that was converted
`data.title`	`string`	The page title
`data.markdownLength`	`number`	Character length of the generated Markdown
`data.timestamp`	`string`	ISO 8601 timestamp of the conversion

Security

Every webhook request includes an X-Web2MD-Signature header containing an HMAC-SHA256 signature of the raw request body, signed with your webhook’s signing secret.

Always verify the signature before processing a webhook. This prevents attackers from sending forged requests to your endpoint.

Verification example (Node.js)

const crypto = require("crypto");

function verifyWebhookSignature(payload, signature, secret) {
  const expected = crypto
    .createHmac("sha256", secret)
    .update(payload)
    .digest("hex");
  return crypto.timingSafeEqual(
    Buffer.from(signature),
    Buffer.from(expected)
  );
}

// In your request handler:
app.post("/webhooks/web2md", (req, res) => {
  const signature = req.headers["x-web2md-signature"];
  const rawBody = JSON.stringify(req.body);

  if (!verifyWebhookSignature(rawBody, signature, process.env.WEB2MD_WEBHOOK_SECRET)) {
    return res.status(401).send("Invalid signature");
  }

  const { event, data } = req.body;
  console.log(`Conversion completed: ${data.title} (${data.url})`);

  res.status(200).send("OK");
});

Use crypto.timingSafeEqual instead of === to prevent timing attacks when comparing signatures.

Retry behavior

Attempt	Timing	Timeout
First	Immediate	5 seconds
Retry	1 second after first failure	5 seconds

If both attempts fail (non-2xx response or timeout), the delivery is dropped. Web2MD does not retry beyond the single retry attempt.

Use cases

Zapier / Make / n8n

Use a Webhook trigger in your automation platform to start a workflow whenever a page is converted — post to Slack, add a row to a spreadsheet, or save to Notion.

Slack notifications

Send a message to a Slack channel every time a team member converts a page, keeping everyone in the loop.

Auto-save to external storage

Fetch the full Markdown via the REST API (using conversionId) and save it to S3, Google Drive, or your own database.

Analytics pipeline

Track conversion volume and content types by forwarding webhook events to your analytics backend.

Testing webhooks

During development, use a tool like webhook.site or ngrok to expose a local endpoint and inspect incoming payloads before deploying your handler to production.

Getting Started

Core Features

Advanced

Plans

Overview

Setup

Payload

Security

Verification example (Node.js)

Retry behavior

Use cases

Zapier / Make / n8n

Slack notifications

Auto-save to external storage

Analytics pipeline

Testing webhooks

​Overview

​Setup

​Payload

​Security

​Verification example (Node.js)

​Retry behavior

​Use cases

Zapier / Make / n8n

Slack notifications

Auto-save to external storage

Analytics pipeline

​Testing webhooks

Overview

Setup

Payload

Security

Verification example (Node.js)

Retry behavior

Use cases

Testing webhooks