Notifications
The group can notify you when certain events happen — for example, when a form submission is received or when a new member joins. Notifications can arrive via email (to Owners) and/or via webhook (to a configured URL).
Configuration is located in Group settings and is managed exclusively by the Owner.
Events
| Event | When it occurs |
|---|---|
| New form submission | Someone completes a form on a published landing. |
| New member | A person accepts an invitation and joins the group. |
| Paid sale | Payment confirmation is received for a store order. |
For each event you independently choose whether you want notifications via email, webhook, both, or neither.
Email alerts arrive with event details and a link to the dashboard. Simply enable the Email channel for that event: by default, it is sent to group Owners.
Choosing recipients
Beneath each event with email enabled, the "Sent to…" line appears. There you choose which team members receive notifications, so you don't depend on an Owner forwarding everything manually.
- Owners is the default setting and is not the same as checking current Owners: it resolves dynamically at the moment of each notification, so an Owner joining later is automatically included. You can revert to this setting anytime.
- If you select individuals manually, the list is fixed: adding someone to the group later does not add them to notifications.
Why you cannot select just anyone
Each alert carries data that is protected behind permissions in the dashboard, so it can only be received by someone who could already see that data by signing into the application:
| Event | Requires permission to view |
|---|---|
| New form submission | Metrics |
| New member | Group data |
| Paid sale | Orders |
People who do not meet requirements still appear in the list, grayed out and with the reason — we don't hide them, so there's no confusion about why someone is missing. If you change someone's role and their new role cannot view that data, they stop receiving the alert, even if still selected: we warn you in the same line. The list is rechecked with every send, not just when saved.
An email once sent cannot be recalled: it remains in the recipient's inbox. Therefore this restriction has no exceptions, even when requested by the Owner.
The webhook channel is not filtered by person: it points to your own system endpoint, not an individual with a role.
Webhook
A webhook is your URL to which Landinker sends a POST containing event data, enabling integration with your own systems.
Configuration
- In Group settings → Webhook, paste your endpoint URL (must be public and use HTTPS).
- Check Webhook enabled and save.
- Enable the Webhook channel on the events you wish to receive.
- Use Send test to verify your endpoint responds.
Payload format
- POST method, JSON body:
{ "event": "...", "groupId": "...", "timestamp": "...", "data": { ... } }. - Headers:
X-Landinker-Event,X-Landinker-Timestamp, andX-Landinker-Signature.
Verifying the signature
Each request is signed with a secret (viewable and regenerable on the same screen). The signature is the HMAC-SHA256 of the raw request body using your secret, transmitted in the header as sha256=<hex>.
On your server: calculate the HMAC-SHA256 of the received body using your secret and compare the result with the X-Landinker-Signature header. If they don't match, discard the request. If you regenerate the secret, remember to update it in your endpoint.
Your endpoint should respond quickly with a 2xx status code. For network errors or 5xx/429 responses, Landinker retries a few times; 4xx codes are considered final.