Notifications & webhooks
A regression in AI visibility is only useful if it reaches you quickly. Lokrix can deliver alerts to email, Slack, or an outbound webhook so they land in the tools your team already watches — and webhooks let you fold Lokrix events into your own automations.
What can trigger a notification
Notifications are driven by alert rules on a property. Typical triggers include:
- A meaningful drop in the Lokrix AI Score — one that clears the confidence interval, not statistical noise.
- A change in presence or share-of-voice for a specific engine or prompt.
- A competitor overtaking you on a tracked prompt.
- A completed scan or a failed scan that needs attention.
Because scores are sampled with a confidence interval, alert rules compare against that interval so you are not paged for a single unlucky run — see sampling & confidence intervals.
Channels
- Email — sent to workspace members you choose; the simplest channel, on by default for critical alerts.
- Slack — post alerts to a channel via an incoming webhook URL you paste into the integration.
- Webhook — an HTTPS endpoint you own that receives a signed JSON payload for every event, for routing into your own systems.
Outbound webhooks
Register an endpoint under the property's Integrations panel. Lokrix delivers a compact, minified JSON body over HTTPS describing the event — its type, the property, the engine or prompt affected, and the relevant metric values with their confidence interval. Deliveries are retried with backoff if your endpoint is temporarily unavailable.
Verifying signatures
Each request carries a signature header computed with a per-endpoint signing secret shown when you create the webhook. Recompute the HMAC over the raw request body and compare it to the header using a constant-time check; reject the request on any mismatch. This confirms the payload came from Lokrix and was not altered in transit. Rotate the secret from the same panel if it is ever exposed.
If you would rather pull events than receive them, the same data is available through the REST API, authenticated with an API key and scope.