FDA Recall Monitor — Real-Time Slack & Telegram Alerts avatar

FDA Recall Monitor — Real-Time Slack & Telegram Alerts

Pricing

from $500.00 / 1,000 result delivereds

Go to Apify Store
FDA Recall Monitor — Real-Time Slack & Telegram Alerts

FDA Recall Monitor — Real-Time Slack & Telegram Alerts

Real-time alerts on FDA drug, food, and medical device recalls from the official openFDA API. Watch any firms or products and push notifications to Slack, Discord, Telegram, or webhook. A modern alternative to FDAzilla, RegEd, and FDA email subscriptions — pay only $0.50 per match

Pricing

from $500.00 / 1,000 result delivereds

Rating

0.0

(0)

Developer

Netsrac

Netsrac

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Share

FDA Recall Monitor — Real-Time openFDA API Alerts to Slack, Discord & Telegram

Get push notifications the moment a new FDA recall is published — across drugs, food, and medical devices. Built directly on the official openFDA API (no scraping, no anti-bot drama, no auth needed). Set a firm watchlist or product-keyword watchlist, choose your severity classification (Class I, II, III), and recall events get pushed to your Slack, Discord, Telegram, or any HTTPS webhook within minutes of openFDA publishing them.

A modern, programmable alternative to manual FDA email subscriptions, FDA RSS, FDAzilla, RegEd, and other $300–$1,500/mo regulatory-monitoring SaaS — for compliance teams, supplement brands, food manufacturers, medical device firms, pharma RegOps, and equity analysts who need to know before their lawyers do.

TL;DR: FDA publishes recalls weekly through the openFDA enforcement API. This actor is a recall watchlist + watcher — it polls that feed, filters by your firm/product/severity criteria, and pushes clean structured alerts. Pay only $0.50 per recall match delivered. Quiet weeks cost $0.

What does FDA Recall Monitor do?

This actor is a programmable wrapper around the official openFDA Enforcement Reports API (api.fda.gov/drug/enforcement.json, api.fda.gov/food/enforcement.json, api.fda.gov/device/enforcement.json). It polls the openFDA API for new FDA enforcement actions across:

  • Drugs (~17,000+ historical records)
  • Food (~28,000+ historical records)
  • Medical devices (~38,000+ historical records)

It filters by firm name keywords, product description keywords, classification severity (Class I, II, III), and optional US state, then pushes a structured alert to your Slack, Discord, Telegram, or HTTPS webhook. Every alert is also written to the run's dataset for backup and downstream integrations.

Real-world signals like "Class I recall — Philips Respironics — CPAP machines — pending field safety notice" hit your channel within a polling interval of FDA publishing them.

What this actor solves

  • Push notifications the moment a new recall posts — not a daily/weekly email digest
  • Custom watchlists — by firm name, product keyword, or severity classification
  • Direct openFDA API — clean JSON, no scraping, no breakage
  • Programmatic access — pipe alerts to your compliance dashboard, ticketing system, or LLM
  • No Zapier or n8n needed — Apify's built-in Schedules feature does the cron

Why use FDA Recall Monitor instead of FDA email or expensive RegOps SaaS?

FDA email subscriptionsRegOps SaaS (RegEd, Kallpa, FDAzilla)FDA Recall Monitor
CostFree, but unfiltered noise$300–$1,500/month~$0.50 per match delivered
Push to your channel❌ Email onlyLimited, paid integrations✅ Slack, Discord, Telegram, webhook
Firm watchlist filter
Product keyword filter
Classification (Class I/II/III) filter
JSON dataset for archiving
No dashboard required
Pay only when something matchesn/a❌ (flat fee)

For most compliance teams watching <50 firms or <20 keywords, this actor costs under $25/month.

Use cases & workflows

1. Pharma / supplement compliance

Watch your own firm name + your contract manufacturers + your raw-material suppliers. Get a Slack ping the moment any of them appears in an FDA enforcement action — often before your QA team would notice.

2. Competitor & sector intelligence

Watch competitors. A Class I recall on a competing product is a sales-team signal worth millions: launch a "switch from X" campaign within hours of the news breaking.

3. M&A and due diligence

Monitor target acquisitions during deal evaluation. A surprise Warning Letter or recall mid-process can swing valuation by 8 figures.

4. Investor / hedge fund tracking

Watch a basket of pharma / food / device tickers' parent firms. A material recall is often a stock-moving event before press releases hit the wire.

5. Insurance / liability monitoring

Insurers and legal teams watch entire supply chains. Aggregating openFDA + alert routing dramatically cuts time-to-claim-prep.

6. Journalists & researchers

Beat the FDA RSS feed by hours. Custom keyword watches like "infant formula", "EpiPen", "compounding pharmacy" surface stories before competitors.

How to use FDA Recall Monitor

⚠️ Important: this actor must be scheduled to receive ongoing alerts. A single run only checks once. Use Apify's built-in Schedules feature — no Zapier, n8n, or external cron needed.

  1. Click "Try for free" to add the actor to your Apify account.
  2. Configure the input: select product types (drug/food/device), add firmKeywords and/or productKeywords, set classification severity, pick a notificationChannel.
  3. Paste your webhook URL or Telegram credentials. All secret fields are stored encrypted by Apify.
  4. First run: enable testMode to fire one alert for the most recent matching recall and confirm your webhook works.
  5. Set up the Schedule: Actor → Schedules tab → New schedule → cron 0 */12 * * * (every 12 hours, since openFDA updates weekly there's no value in faster polling).
  6. Optional: add an openFDA API key for higher rate limits in openFdaApiKey. Free tier (no key) gives 1,000 req/day, which is plenty for typical use.

Schedule cadence cheat sheet

CronFrequencyBest for
0 */6 * * *every 6 hoursActive monitoring (default for compliance teams)
0 */12 * * *every 12 hoursStandard — matches openFDA's update cadence
0 9 * * 1-5weekdays 9am UTCDaily morning digest

Input

FieldDescription
productTypesOne or more of drug, food, device
firmKeywordsOptional list of firm-name substrings (case-insensitive). Empty = match all firms.
productKeywordsOptional list of product/reason substrings. Empty = match all products.
classificationsSeverity: Class I, Class II, Class III. Default Class I + II.
statesOptional 2-letter US state codes (e.g. ["CA","NY"]). Empty = all locations.
lookbackDaysHow many days back to scan each run. Default 30 (recommended due to openFDA's reporting lag).
notificationChannelnone | slack | discord | telegram | webhook
slackWebhookUrl / discordWebhookUrlChannel webhooks
telegramBotToken + telegramChatIdTelegram bot credentials
customWebhookUrlAny HTTPS endpoint receiving JSON alerts
openFdaApiKeyOptional — recommended for production schedules
testModeFirst-run sanity check — fires one alert without dedup

Output

Every alert is also pushed to the run's dataset. Example item:

{
"recallNumber": "Z-1646-2026",
"eventId": "98763",
"reportDate": "2026-04-29",
"recallInitiationDate": "2026-04-09",
"productType": "device",
"classification": "Class I",
"recallingFirm": "Philips Respironics, Inc.",
"city": "Murrysville",
"state": "PA",
"country": "United States",
"productDescription": "DreamStation 2 Auto CPAP Advanced...",
"reasonForRecall": "Potential health risk from heater plate degradation...",
"distributionPattern": "Nationwide in the USA",
"status": "Ongoing",
"voluntaryMandated": "Voluntary: Firm initiated",
"fdaUrl": "https://www.fda.gov/safety/recalls-market-withdrawals-safety-alerts?search_api_fulltext=Z-1646-2026"
}

You can download the dataset in JSON, CSV, Excel, or HTML from the Apify Console.

Data table

FieldTypeDescription
reportDatedateWhen FDA published the recall
productTypestringdrug / food / device
classificationstringClass I / II / III
recallingFirmstringName of company recalling
productDescriptionstringWhat's being recalled
reasonForRecallstringWhy
distributionPatternstringWhere the product was distributed
statestringUS state of recalling firm
recallNumberstringOfficial FDA recall number
fdaUrllinkDirect link to FDA recall page

Pricing — pay-per-event

This actor uses Apify pay-per-event pricing: ~$0.50 per recall alert delivered. On days with no matching recalls, you pay nothing. Compare to:

ServiceApprox costNotes
FDA email subscriptionFreeUnfiltered, email-only, no API
Email-to-Slack via Zapier$20/mo + Zapier feesDIY, brittle
RegOps SaaS (RegEd, FDAzilla)$300–$1,500/monthEnterprise contracts, far more features
FDA Recall Monitor$5–$50/month for typical usePush alerts + JSON API

Tips & advanced options

  • Use firm + product filters together. If you watch 20 firms with no keyword filter, expect 20–100 alerts/month. Add product keywords to narrow.
  • Default to Class I + II. Class III recalls are technical/cosmetic — usually noise.
  • Get an openFDA API key. Free, raises your daily quota from 1,000 → 120,000 requests. Useful if you watch many product types or have very wide keyword filters.
  • Pipe to a database. Set notificationChannel: "none" and use Apify's Webhook Integration to POST every new dataset item to your own backend or BI tool.
  • Combine with FDA Warning Letter / Form 483 monitoring. Recalls are downstream signals; Warning Letters and 483s are leading indicators. Pair this actor with separate Warning Letter and 483 monitors for full coverage.

FAQ

Is this legal? Yes. openFDA is the FDA's official public API under the Open Government Initiative. All data is public-domain.

How fresh is the data? openFDA updates roughly weekly with a 3–10 day lag from the original FDA enforcement report. Keep lookbackDays at 30 to ensure no recalls slip through.

Why might I see 0 alerts on a single run? openFDA batches updates — many days have no new postings. With dedup, repeat runs only alert once per recall.

Why isn't my firm appearing? Firms appear in openFDA exactly as they're listed in the FDA report. If you watch "Pfizer", you may also need "Pfizer Inc.", "Pfizer Pharmaceuticals", and any subsidiaries. Use shorter substrings ("pfizer") for broader matching.

Does this cover Warning Letters or Form 483? No — only enforcement recalls. Warning Letters and 483 inspections are separate FDA data sources.

Does this cover non-US recalls (EU EMA, UK MHRA, Canada Health)? No — US FDA only. Each authority would need its own actor.

Support

Open an issue on the actor's Issues tab. Feature requests and feedback welcome.


Disclaimer: This actor is an information-retrieval tool for publicly available FDA data. Nothing in its output constitutes legal, medical, or compliance advice.

Keywords: FDA recall alerts, FDA recall monitor, FDA recall watchlist, FDA recall watcher, openFDA API, openFDA enforcement API, openFDA wrapper, FDA enforcement reports API, drug recall alerts, food recall monitor, medical device recall tracker, FDA Class I recall, FDA enforcement reports, FDA recall Slack alerts, FDA recall Discord bot, FDA recall Telegram bot, pharma compliance monitoring, supplement recall tracker, recall notification API, FDAzilla alternative, RegEd alternative, real-time FDA recalls.