Skip to main content
20% off 3 months · code LAUNCH20 · until 31 October

Send waitlist signups, feedback and changelog entries to Discord

Post waitlist signups, feedback and changelog entries into a Discord channel. Discord webhooks need no bot and no OAuth: a channel webhook URL is enough.

How do I connect Nordva Launch to Discord?

In Discord, open the channel's settings, Integrations → Webhooks → New Webhook, copy the URL and paste it as a Nordva Launch webhook. Launch recognises discord.com and sends one readable message per event. Indie and up. The URL is a credential: it is stored encrypted and masked afterwards.

01Get the Discord URL

  1. Open the channel's settings (the cog next to its name), then Integrations → Webhooks → New Webhook.
  2. Name it, choose the channel, press Copy Webhook URL. It starts with https://discord.com/api/webhooks/.
  3. The URL contains the token. Anyone with it can post to the channel; do not commit it.

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://discord.com/api/webhooks/<id>/<token>",
    "events": ["waitlist.signup.created", "feedback.created"],
    "description": "Discord"
  }'
# → data.signing_secret is returned once (unused for Discord, which cannot verify it)

Or from an AI agent with the MCP server connected: “send new waitlist signups and feedback to Discord, 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 Discord receives

Launch recognises the Discord URL and sends one readable line per event, in the shape Discord accepts, instead of the JSON envelope:

New waitlist signup: jane@example.com (position 42) from hn
New feedback (bug): Export fails for lists over 2,000 rows
Changelog published: Dark mode https://launch.nordva.dev/log/acme/ce_01K5…
  • Press Test. “Test message from Nordva Launch. This webhook works.” appears in the channel.
  • Discord caps a message at 2,000 characters; Launch cuts the line at 1,900. A long changelog entry arrives as its title and public link, not its body.
  • For a community server, subscribe the public channel to changelog.entry.published only, and keep signups and feedback in a private one.

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 Discord 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 Discord is down, the signup still succeeds.

Questions

Can the message @mention a role?

Not from Launch: the message is plain text. Discord supports a webhook that mentions a role if the text contains <@&roleId>, but Launch does not template the message. Send the JSON envelope to your own bot if you need mentions.

Does it work with discordapp.com URLs?

Yes. Both discord.com and discordapp.com webhook hosts are recognised and sent the Discord message shape.