Outgoing webhook

Send Unwaited submissions to Zapier

Send Standard signup and Preorder order events to a Zap. Map the records into a spreadsheet or another destination.

Example mapping, using Unwaited's test event

UNWAITED

entry.created

entry.email: [email protected]

entry.position: 1

Zapier Catch Hook → spreadsheet action

Email columnPosition
[email protected]1

Expected test result: one row with the sample values. Check your actual Zap run to confirm.

Before you start

  • Unwaited Starter or Pro for webhooks, plus a paid Zapier plan with Webhooks by Zapier. Check the linked Zapier guide for current eligibility.
  • Supported events are entry.created, entry.status_changed, order.created, and order.status_changed. Queue tickets and class bookings do not emit these webhooks.
  • Keep your Catch Hook URL private. The basic Catch Hook setup does not verify Unwaited's signature; signature verification requires additional receiver logic.

Platform guidance: Zapier: webhook triggers, plans, and tests.

Set up and test the handoff

  1. Create a Catch Hook trigger

    Create a Zap, choose Webhooks by Zapier, and select Catch Hook. Leave the child key blank to keep the full event envelope. Continue to Test and copy its unique webhook URL.

  2. Save and publish the webhook URL

    Open your Unwaited page's Webhooks tab, paste the URL, and choose Save to draft. Publish the page configuration to activate the new URL. Then use Send test and return to Zapier's Test trigger.

  3. Map the sample into a test destination

    Send test produces a Standard entry.created sample, even on a Preorder page. For a Standard signup, map entry.email and entry.position into a test spreadsheet. Filter by event so a status change does not create another signup row. Deduplicate retries with deliveryId.

  4. Check the result, then turn on the Zap

    Test your destination action with the sample and confirm its test row contains [email protected] and position 1. A successful webhook delivery only confirms Zapier received it; check the action result too. Preorder mappings need the order payload, not the entry sample.

Sample Standard event

Illustrative JSON from Send test. IDs and timestamps vary. Real Preorder events use an order object instead of entry.

{
  "event": "entry.created",
  "deliveryId": "example_delivery_id",
  "waitlist": {
    "id": "example_waitlist_id",
    "slug": "YOUR_FORM_ID",
    "name": "Example signup page"
  },
  "entry": {
    "id": "test_entry",
    "position": 1,
    "email": "[email protected]",
    "status": "WAITING",
    "data": {
      "test": true
    },
    "createdAt": "2026-09-29T12:00:00.000Z"
  }
}

Questions

Does a delivered webhook mean my automation finished?

No. It means the receiver accepted the request. Check the Zap's run history and destination to confirm the action completed.

How do I map a Preorder event?

Use order.created or order.status_changed and map order.email, order.pickup, order.status, and order.items. The Send test button produces only an entry.created sample, so it cannot prove your Preorder mapping works. Validate order mappings with a separate test workflow before using customer records.

Choose the page you want to connect.

Webhooks are available on Starter and Pro.

Open your dashboardAll integration guides