Webhooks & alerts

When alerts fire

Alerts are attached to scheduled crawls. After each scheduled run, we compare it with the previous crawl of the project and alert only when something regressed:

• the Health score dropped meaningfully,
• new error-severity issues appeared, or
• a custom rule got worse.

A clean run sends nothing. There’s deliberately no “crawl finished” notification — if you hear from us, something needs attention.

Email alerts

Enable notifications on the project and regression emails go out from alerts@crawlie.app, summarising what changed with a link to the report.

Webhook alerts

Each project can also have an alert webhook (Project → Settings). We POST a simple JSON payload:

{ "text": "Health dropped 82 → 74 on example.com: 3 new errors …" }

That text shape is exactly what Slack and Discord incoming webhooks accept, so pasting a Slack webhook URL gives you alerts in a channel with zero glue code. Anything that accepts a JSON POST works.

Alerts for humans, API for machines

Webhooks tell you that something regressed. For pipelines that need the details, follow up over the REST API or MCP — fetch the diff and act on exactly what changed.