Send waitlist signups, feedback and changelog entries to Make
Run a Make scenario from Nordva Launch events: a custom webhook module receives the JSON envelope and the rest of the scenario maps it into Google Sheets, Airtable, HubSpot, Notion or email.
How do I connect Nordva Launch to Make?
In Make, add Webhooks → Custom webhook, create a hook and copy its address (hook.<region>.make.com). Paste it as a Nordva Launch webhook and press Test so Make can determine the data structure from the ping. Then map data.email, data.summary and the rest into the modules that follow.
01Get the Make URL
- Create a scenario. First module: Webhooks → Custom webhook → Add. Copy the address; it starts with https://hook. followed by your region, for example hook.eu1.make.com.
- Make waits for a sample to learn the structure. Leave the scenario open on “Redetermine data structure” and go to Launch.
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://hook.<region>.make.com/…",
"events": ["waitlist.signup.created", "feedback.created"],
"description": "Make"
}'
# → 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 Make, 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 Make 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.
- Paste the address as the endpoint URL and press Test. Make reports “Successfully determined”. The structure is the ping envelope; real events add keys under data, which Make will pick up as they arrive, or you can send one real signup now.
- Add a Router if one endpoint carries several event types, with a filter on type per route.
- Schedule the scenario as Immediately so the webhook runs it on arrival.
- 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. Make does not verify the signature; keep the hook address private.
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 Make 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 Make is down, the signup still succeeds.
Questions
Do I need a paid Make plan?
Custom webhooks are part of Make's core modules and were available on the free plan when checked; the limit is the number of operations a month. Check Make's pricing page for the current figures.
The data structure is missing fields.
Make learns the structure from the first sample, which is the ping. Send one real event (add a signup, publish an entry) and press Redetermine data structure on the webhook.