Docs Tutorials / New recall alerts in n8n and Zapier
New recall alerts in n8n and Zapier
Two ways: poll the new-recalls feed once an hour, or catch webhook messages. Either way, each recall has a stable id you can use to skip duplicates.
You need a free key (get one; it takes about a minute) in the environment variable RECALLDB_KEY. Keep the key on a server or your own machine, never in a web page.
The request both tools send
# What a no-code tool (n8n, Zapier, Make) sends every hour: new recalls since a time, newest first.
# On a free key the feed is a copy up to 1 hour old, so polling more often than hourly gains nothing.
curl "https://recalldb.app/v1/new?since=2026-11-15T00:00:00Z&category=vehicle&limit=20" \
-H "Authorization: Bearer $RECALLDB_KEY"Each poll counts as one request: hourly polling is about 720 a month, inside the free 1,000. On a free key the feed is a copy up to 1 hour old.
n8n
- Schedule Trigger: every hour.
- HTTP Request: GET
https://recalldb.app/v1/new, querysince={{ $now.minus({ hours: 2 }).toISO() }}(a little overlap is safe) and anycategoryoragencyfilter. Authentication: Generic, Header Auth, nameAuthorization, valueBearer rdb_your_key. - Split Out: field
data. - Remove Duplicates: "Remove items processed in previous executions", compare field
id. - Slack or Send Email:
{{ $json.title }},{{ $json.issued_by }}and{{ $json.source.official_url }}. Add "Data from RecallDB" with a link.
Zapier
- Trigger: Webhooks by Zapier, event Retrieve Poll. URL
https://recalldb.app/v1/new?limit=50, headerAuthorization=Bearer rdb_your_key, Keydata, Deduplication Keyid. - Action: Slack, Gmail or any app. Map
title,issued_byandsource official_url, and add "Data from RecallDB".
Instead of polling: webhooks
Use Catch Hook (Zapier) or a Webhook node (n8n), register its URL with POST /v1/webhooks, and point a watchlist at it (see webhook alerts). Check the signature where the tool allows it (an n8n Code node can run the receiver's verify function).
Reference: GET /v1/new, integrations.