Stay in the loop without refreshing the dashboard. Trawl can email you results after every scheduled run and alert you when things break.
Notification types
There are two independent notification channels, both configured in Settings → Automation:
Email results
Sends the scraped data by email after each scheduled (cron) run. Choose between:
| Format | Best for |
|---|---|
| CSV | Opening in Excel / Google Sheets, quick scanning |
| JSON | Feeding into other tools, structured processing |
The email contains the full result set from the latest execution. Manual runs and API-triggered runs do not send result emails — only cron runs do.
Alert on failure
Sends an email when the scrap transitions to a failure state:
error— the script threw an exception0 items— the script ran butreturnData([])returned nothing (usually a broken selector)validation_failed— the result did not match the configured schema (see Data Quality)
Alerts fire on state transitions, not on every failed run. If a scrap fails three times in a row, you get one alert on the first failure — not three.
Alerts with Auto-fix
When both Alert on failure and Auto-fix with AI are enabled, the failure email is replaced by an outcome-aware email sent after the fix attempt resolves. This keeps your inbox honest — no "it broke" email seconds before "we fixed it".
| Scrap state | Email sent | Template | When |
|---|---|---|---|
autoFix: false + failure |
Failure (unchanged) | scrap-failed-alert |
Immediately when the run fails |
autoFix: true + Auto-fix recovered |
Recovered (green) | scrap-autofix-recovered |
After the re-run comes back green |
autoFix: true + Auto-fix couldn't fix |
Needs review (amber) | scrap-autofix-failed |
After the fix attempt gives up |
The Recovered email includes the diagnosis, a diff summary of the fix, and a link to the history entry. The Needs review email surfaces the reason (dry-run failed, no worker container, circuit breaker tripped, etc.) plus any attempted fix diff, so you can decide whether to accept, revert, or hand-edit.
Delivery timing: with Auto-fix on, the email arrives after the fix attempt resolves — the fix runs on the next event-loop tick, then the re-run is a real scrap run (typically 30-250s). With Auto-fix off, the email fires immediately.
Rate: one email per terminal Auto-fix outcome per history. Consecutive failures each trigger their own email — if a scrap fails 10 times in a row with Auto-fix giving up each time, you get 10 "needs review" emails. A per-scrap daily cap is on the roadmap.
Configuring recipients
By default, notifications go to your account email. You can override the recipient in Settings → Automation:
- Alert email — who receives failure alerts
- Email results recipient — who receives the CSV/JSON data after cron runs
Both fields accept a single email address.
When do notifications trigger?
| Trigger | Email results | Alert |
|---|---|---|
| Scheduled (cron) run | Yes | Yes (on failure) |
| Manual run (UI play button) | No | No |
| API-triggered run | No | No |
This keeps your inbox clean — notifications are reserved for unattended, automated runs.
See also: Schedule · AI Features · Webhooks · Data Quality
Next step → AI features