Send waitlist signups, feedback and changelog entries to Zapier

02Create the endpoint

Three ways, same result. In the dashboard: Webhooks → Add webhook, paste the URL, tick the events, press Test. Over the API with a secret key:

curl -X POST https://api.nordva.dev/v1/webhooks \
  -H "Authorization: Bearer nv_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://hooks.zapier.com/hooks/catch/…",
    "events": ["waitlist.signup.created", "feedback.created"],
    "description": "Zapier"
  }'
# → data.signing_secret is returned once; keep it if you verify signatures

Or from an AI agent with the MCP server connected: “send new waitlist signups and feedback to Zapier, here is the URL”. The agent calls create_webhook, then test_webhook, and reads the delivery log if the test fails.

Events you can subscribe to: waitlist.signup.created, waitlist.signups.invited, changelog.entry.published, changelog.subscriber.created, feedback.created, or "*" for all of them.

03What Zapier receives

A POST with the JSON envelope. Every event has the same outer shape; data depends on the type. A signup:

{
  "id": "evt_01K5…",
  "type": "waitlist.signup.created",
  "created_at": "2026-09-17T20:41:07.512Z",
  "project_id": "prj_01K4…",
  "data": {
    "signup_id": "ws_01K5…",
    "email": "[email protected]",
    "position": 42,
    "referral_code": "JANE42",
    "referred": false,
    "source": "hn",
    "utm_source": null,
    "created_at": "2026-09-17T20:41:07.512Z"
  }
}

Headers: Nordva-Event-Id, Nordva-Event-Type, Nordva-Delivery-Id, Nordva-Signature (HMAC-SHA256, t=…,v1=…). The full field list per event is in the webhooks guide.

• Press Test on the Launch endpoint, then Test trigger in Zapier. It samples the ping event; the fields of a real event are listed on the docs page linked below and follow the same envelope.
• Map the fields you need: data__email, data__position, data__source for a signup; data__classification and data__summary for feedback; data__title and data__public_url for a changelog entry.
• Add a Filter step on type if the endpoint subscribes to several events and the Zap should react to one.
• The request is the signed JSON envelope: id, type, created_at, project_id and data. Nordva-Event-Id is the same across retries, so use it to ignore a duplicate. Zapier does not verify the signature, so treat the catch URL itself as the secret.

Delivery, retries, limits

• Any 2xx within 10 seconds counts as delivered. A 3xx, 4xx, 5xx or a timeout is retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours, then given up.
• An endpoint that fails 20 deliveries in a row is switched off; the dashboard says why, and one click switches it back on.
• Every delivery of the last 30 days is in the log with what was sent and what Zapier answered.
• Indie includes 2 endpoints per project, Builder 5. Webhooks are not on the Free plan.
• A webhook never slows or fails the API call that caused it: if Zapier is down, the signup still succeeds.

Questions