Webhook payloads

Sample payloads and headers sent by Distro Workflows webhooks.

Sample webhook payloads for different sources in Distro Workflows.

Distro sends JSON to your configured webhook URL.

Payload shape depends on the source type and trigger.

Payloads are examples. Distro may add fields over time.

Basics

All webhooks use the same envelope:

{
  "event": "meeting_booked",
  "timestamp": "2024-01-15T10:30:00Z",
  "data": {}
}

• event: the trigger that fired the webhook (see Triggers).

• timestamp: ISO 8601 time when Distro sent the webhook.

• data: the event payload. Shape depends on source type.

Conventions:

• Keys use snake_case.

• data.source_type is one of: router, click_router, booking_link, group_meeting_link.

• data.booking can be null for submission-only triggers.

Payload examples

Router

Triggered by Form Routers.

{
  "event": "meeting_booked",
  "timestamp": "2024-01-15T10:30:00Z",
  "data": {
    "source_type": "router",
    "source_id": 123,
    "source_title": "Demo Request Router",
    "submission": {
      "id": 789,
      "uuid": "sub-xyz789-abc123",
      "form_data": {
        "email": "[e-mail]",
        "company": "Acme Corp",
        "employees": "50-100",
        "message": "Interested in enterprise plan"
      },
      "time_zone": "America/New_York",
      "source_url": "https://example.com/contact",
      "created_at": "2024-01-15T10:25:00Z"
    },
    "booking": {
      "id": 456,
      "uuid": "book-abc123-def456",
      "title": "Discovery Call with Acme Corp",
      "start_time": "2024-01-20T14:00:00Z",
      "end_time": "2024-01-20T14:30:00Z",
      "status": "scheduled",
      "meeting_url": "https://meet.google.com/abc-defg-hij",
      "time_zone": "America/New_York",
      "notes": "Looking forward to discussing your needs."
    },
    "assignee": {
      "id": 1,
      "email": "[e-mail]",
      "first_name": "Alex",
      "last_name": "Smith"
    },
    "attendees": [
      {
        "name": "Jane Doe",
        "email": "[e-mail]"
      }
    ]
  }
}

Submission-only events

For form_submitted, prospect_disqualified, and prospect_no_booking, booking is null.

{
  "event": "form_submitted",
  "timestamp": "2024-01-15T10:30:00Z",
  "data": {
    "source_type": "router",
    "source_id": 123,
    "source_title": "Contact Form Router",
    "submission": {
      "id": 789,
      "uuid": "sub-xyz789-abc123",
      "form_data": {
        "email": "[e-mail]",
        "company": "Acme Corp",
        "employees": "50-100"
      },
      "time_zone": "America/New_York",
      "source_url": "https://example.com/contact",
      "created_at": "2024-01-15T10:30:00Z"
    },
    "booking": null,
    "assignee": {
      "id": 1,
      "email": "[e-mail]",
      "first_name": "Alex",
      "last_name": "Smith"
    },
    "attendees": []
  }
}

Click Router

Booking Link

Group Meeting Link

Operational notes

HTTP headers and signatures

Every webhook request includes:

• Content-Type: application/json

• User-Agent: Distro-Webhooks/1.0

• X-Distro-Delivery-ID: unique delivery ID for tracking

• X-Distro-Timestamp: Unix timestamp of request (seconds)

• X-Distro-Signature: t={timestamp},v1={signature} (only if a signing secret is configured)

• X-Distro-Test: true (only for test webhooks)

Use X-Distro-Delivery-ID as an idempotency key if you store deliveries.

Verifying signatures

• Signature header: X-Distro-Signature: t={timestamp},v1={signature}

• Signed content: {timestamp}.{raw_request_body}

• Algorithm: HMAC-SHA256 using your signing secret

• Compare the computed hex digest with v1

Use the raw request body bytes for verification.

Don’t parse and re-serialize JSON before hashing.

Event-specific notes

Cancelled meetings

When event is meeting_cancelled, booking.status is cancelled.

{
  "event": "meeting_cancelled",
  "timestamp": "2024-01-18T11:00:00Z",
  "data": {
    "booking": {
      "status": "cancelled"
    }
  }
}

No-show meetings

When event is meeting_no_show, booking.status is no_show.

{
  "event": "meeting_no_show",
  "timestamp": "2024-01-18T11:00:00Z",
  "data": {
    "booking": {
      "status": "no_show"
    }
  }
}

Payload limits

• Maximum payload size: 1 MB

• Maximum form_data size: 100 KB

If limits are exceeded, Distro truncates data and includes a truncation marker:

{
  "form_data": {
    "_truncated": true,
    "_original_size": 150000,
    "_message": "Form data exceeded 100KB and was truncated"
  }
}