MARKET RESEARCH
Competitor Patent Filing Alert with Notion Tracker Log
Daily watch for new patent filings from a named list of competitor assignees; logs each new filing as a row in a Notion database and pings Slack only when a watched competitor…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionQuery filings per watched competitorPerplexity
- LogicFilter out already-logged filings
- ActionAppend new filings to Notion trackerNotion
- LogicAny new filings today?
- OutputAlert Slack on competitor activitySlack
What it does
It watches a specific list of competitor companies and, each day, finds any new patent filings assigned to them. Every new filing becomes a structured row in a Notion tracker (assignee, title, filing date, abstract, link) and a Slack alert fires only when one of your watched competitors actually files something. No noise on quiet days.
When to use it
Use it when you track a defined competitor set and need an auditable running log of their patent activity, not just a digest. The Notion database becomes a searchable history product can reference in planning.
How it works
- 1A daily schedule triggers the run.
- 2For each watched assignee, a Perplexity query retrieves recent patent filings tied to that company.
- 3A logic filter drops anything already logged (matched against existing Notion rows) and anything older than the lookback window.
- 4Each genuinely new filing is appended as a row to the Notion tracker database.
- 5A logic branch checks whether any new rows were created today.
- 6If yes, a Slack message lists the new filings and links to the Notion rows; if none, the run ends silently.
Set it up
What you configure once, before turning it on.
- 1Connect PerplexitySearch-grounded answers with citations.
- 2Connect NotionPages, databases, comments.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Market Research workflows
Hiring Surge Detector with Slack Alert
Detects when a target account's open-role count jumps above its recent baseline and posts a ranked Slack alert to the GTM channel so reps can act on a company that is clearly…
Tech-Stack Shift Inference from Job Descriptions
Reads new job descriptions for target accounts, uses an LLM to extract named technologies and infer stack changes.
Enrich Inbound Accounts with BigQuery Firmographics and Score Fit
When a new account row lands in Airtable, joins it against BigQuery public business datasets to attach firmographic attributes.
Blend BigQuery TAM with Live Competitor Signals into a Notion Brief
On demand, sizes a chosen segment from BigQuery public data, gathers current competitor signals via Brave Search, and synthesizes a one-page market brief into Notion.
Allocate Sales Territory TAM from BigQuery Geo Data to HubSpot
When triggered by a webhook, queries BigQuery public ZIP-level business data to compute TAM per sales territory.
Discover Adjacent Segments from BigQuery and Rank Expansion Bets
On a schedule, scans BigQuery public industry data for fast-growing NAICS sectors adjacent to your core segments, scores them as expansion bets.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.