Weekly competitor 510(k) and PMA clearance brief for medical device teams

Build me an agent workflow that produces a weekly competitor 510(k) clearance brief for our medical device team.

Trigger: a cron schedule that fires every Monday at 8:00 AM America/New_York.

Inputs the workflow should accept as configuration: a list of competitor firm names we want to monitor, and a list of FDA product codes relevant to our category. The brief should match on either field.

When the workflow runs, the agent should:

1. Use the openFDA integration's Search Device 510(k) Clearances operation to look up clearances where decision_date falls in the past seven days AND (applicant matches one of our competitor firms OR product_code matches one of our tracked codes). Use a generous limit so we catch every match.

2. Use the openFDA integration's Search Device Premarket Approvals (PMA) operation the same way: decision_date within the past seven days, filtered to our competitor applicants or product codes. Class III PMA approvals are rarer but high-signal.

3. If both searches return zero matches, send a single Slack message to our #competitor-intel channel via the Slack Bot integration's Send a Message operation that says something like 'No new competitor 510(k) or PMA filings in the past 7 days.' Then exit. Do not create a Notion page.

4. If there are matches, for each filing, reason about: what the device is (from device_name and openfda.device_name), the intended use (from statement_or_summary or the device classification description), the predicate device cited (for 510(k)s, the predicate fields), the clearance pathway and date, and a short take on what the filing implies for our roadmap (new entrant in a code we play in, line extension, indication expansion, etc.). Be concrete and avoid filler.

5. Group the findings by competitor firm. For each competitor, write a short analyst-style section with one paragraph per filing. Open the brief with a 2-3 sentence executive summary that highlights the most strategically interesting move of the week.

6. Use the Notion integration's Create a Page operation to file the brief as a new page in our Regulatory Intelligence database. The page title should be 'Competitor 510(k) Brief, week of <Monday date>'. Include a properties payload with at least the week-of date and a 'count' of filings. The page body should contain the executive summary plus the per-competitor sections, written in Notion blocks (heading_2 per competitor, paragraph per filing, with a bulleted_list of key facts for each filing: applicant, K/PMA number, product code, decision date, predicate if present).

7. Use the Slack Bot integration's Send a Message operation to post a recap to #competitor-intel. The Slack message should be a one-line headline per filing (competitor: device name, K-number or PMA-number) plus a single link at the bottom to the Notion page that was just created. Keep it scannable; this is a heads-up, not the full brief.

Operational notes for the agent: openFDA is a public, unauthenticated API with a 404 response when zero records match (treat as 'no results', not as a fatal error). Format decision_date filters as a date range. For Notion, the workflow author should expose the Regulatory Intelligence database ID as a configurable input. For Slack, expose the channel as a configurable input (default to #competitor-intel).

The watch lists (competitor firms, product codes) should be easy for a non-engineer to edit later without touching code.

Additional information

What does this prompt do?

Pulls every new 510(k) clearance and premarket approval the FDA published in the past seven days for the competitors and product codes you care about.
Reasons through each filing: what the device does, its intended use, the predicate it cites, and what the move signals for your roadmap.
Groups findings by competitor and writes a short analyst-style brief, saved as a new page in your Regulatory Intelligence database in Notion.
Posts a headline list to your Slack channel with a link to the full brief. If nothing new landed, you get a one-line 'no new filings' note instead.

What do I need to use this?

A list of competitor company names and FDA product codes you want to track.
A Notion workspace with a Regulatory Intelligence database (or any page where new briefs should land).
A Slack workspace and the channel where the team reads competitive intel (for example, #competitor-intel).
No FDA login is needed. The clearance and approval data comes from the FDA's public openFDA service.

How can I customize it?

Change the schedule. Mondays at 8am ET is a common cadence, but you can run it daily, biweekly, or only on the first of the month.
Edit the watch list. Add or remove competitor names and product codes as your competitive landscape shifts.
Tune the brief format. Choose how much detail per filing, whether to include MAUDE adverse event context, or how the agent phrases roadmap implications.
Pick where it lands. Swap the Notion database, change the Slack channel, or route to a private channel for leadership only.

Frequently asked questions

Where does the clearance data come from?

Directly from the FDA's public openFDA service, which publishes 510(k) clearances and premarket approvals. There is no login, paywall, or scraping involved.

What if no new filings landed that week?

You get a one-line 'no new filings' note in Slack so the team still knows the workflow ran, and no Notion page is created.

Can it track filings by product code, not just company name?

Yes. You can give it a list of competitor firms, a list of FDA product codes, or both. The agent filters on either.

Does this cover premarket approvals (PMAs), not just 510(k)s?

Yes. Class III devices that go through the PMA pathway are checked alongside 510(k) clearances each week.

How does the brief read?

Each filing gets a short paragraph covering what the device does, its intended use, the predicate cited (for 510(k)s), and a one-line take on what it might mean for your roadmap. Filings are grouped by competitor.