Webhooks
Webhooks overview
Lenit sends a POST request to a URL you register whenever an event happens. Receive it on your own server to notify people over your own channels — KakaoTalk, email, push — or wire it up to Slack, JANDI or Zapier.
What can you do with it?
| Scenario | How it works |
|---|---|
| Status change → notify the people involved | When the "Add dark mode" idea moves to Done, send a KakaoTalk message from your own account to everyone who voted or commented on it |
| Announcement published → notify related users | Link an announcement to an idea when you publish it, and everyone connected to that idea is notified automatically |
| Slack channel alerts | Post to #product-feedback whenever a new idea comes in |
| Zapier / n8n | Create a Notion page, trigger an email campaign, and more — all from a no-code automation tool |
One feature, many targets — automatic formatting
Depending on the webhook URL you register, the backend converts the payload to the right format automatically.
| URL pattern | Converted to |
|---|---|
hooks.slack.com/... | A Slack Block Kit message |
wh.jandi.com/... | JANDI connectInfo |
| Every other URL | The standard Lenit JSON envelope (event + eventLabel + data + audience) |
One organization can register several endpoints at once, each with its own events and audience.
A real-world setup
Payload structure (for your own server)
POST body — the standard Lenit envelope
Request headers:
Content-Type: application/jsonX-Lenit-Event: idea.status_changed
Registering a webhook
- In the admin dashboard, open
Team · Integrations → Webhooksin the sidebar - Click + Add webhook
- Enter the URL, tick the events you want, tick the audience groups, and save
- To check it really works, register a throwaway receiver such as webhook.site, then trigger a real event on the board — change an idea's status, say — and inspect the payload.
NoteThere is no separate "send test" button
The audience (voters, commenters, author) is only filled in meaningfully when the event fires exactly as it does in production, so we recommend verifying with a real event rather than a dummy send.