What data is included in a webhook payload?

The payload includes: event type, timestamp, document details (ID, title, status, URL), organization info, and the user who triggered the event. For status changes, we include both old and new status.

How do I secure my webhook endpoint?

Each webhook request includes a signature header (X-WURDX-Signature) signed with your webhook secret. Verify this signature on your server to confirm the request came from WURDX. Use HTTPS endpoints only.

What happens if my endpoint is down?

We retry failed webhooks with exponential backoff: 1 minute, 5 minutes, 30 minutes, 2 hours. After 5 failures, the webhook is marked failed and we stop retrying. You can manually retry from webhook logs.

Can I filter which events trigger webhooks?

Yes. When creating an automation rule, you specify the trigger conditions. Only matching events fire the webhook. For example: 'Only when status changes to Published'.

Is there a rate limit on webhooks?

We have generous limits: 1000 webhook calls per hour per organization. For most teams, this is way more than needed. Contact us if you have high-volume needs.

Can I test webhooks without changing real documents?

Yes. Use webhook.site or Pipedream to receive test webhooks. Create a test document and change its status. The webhook fires to your test endpoint so you can inspect the payload.

Developer Feature

Connect WURDXto anything

Webhooks send HTTP POST requests when events happen. Status changed? Published? Receive a notification at your URL. Build any integration.

Try it free See all features

What you receive

Example webhook payload when a document status changes

POST https://your-endpoint.com/webhook

{
  "event": "document.status_changed",
  "timestamp": "2026-01-15T10:32:00Z",
  "document": {
    "id": "doc_abc123",
    "title": "Q1 Marketing Campaign",
    "status": "published",
    "previous_status": "approved",
    "url": "https://wurdx.com/d/abc123"
  },
  "triggered_by": {
    "id": "user_john",
    "email": "john@acme.com"
  }
}

↑ JSON payload with everything you need to act on the event

Why webhooks?

Without webhooks

•Polling: constantly check 'did anything change?' Wasteful.
•Manual exports: copy data between systems by hand
•Minutes or hours before downstream systems know
•Fragile scripts to scrape or sync data

With webhooks

•Push-based: we notify you when something happens
•Real-time: milliseconds after the event
•Standard format: JSON over HTTP — easy to consume
•Reliable: retries, signature verification, delivery logs

Integration examples

Slack

Post to a channel when documents are published

How: Use Slack's incoming webhook URL as your endpoint

WordPress

Auto-publish content to your blog

How: Build a small plugin that receives webhook and creates a post

Zapier / Make

Connect to 5000+ apps without code

How: Use WURDX webhook as Zapier trigger, route to any action

Custom Backend

Your own APIs and workflows

How: Handle the POST request in your codebase

Built for production

Signature Verification

HMAC-SHA256 signed requests. Verify to confirm authenticity.

Automatic Retries

Failed deliveries retry with exponential backoff up to 5 times.

Delivery Logs

See every delivery: timestamp, status code, response body.

Frequently asked questions

Visual Workflow Builder Custom Statuses Product Teams Enterprise

Ready to integrate?

Start building your custom workflows with WURDX webhooks.

Get started free See pricing