MARKET RESEARCH
New Patent Filing Webhook to Linear Triage Issue
Receives a webhook when a watched competitor publishes a patent, classifies whether it threatens a current initiative.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives new patent filingHTTP webhook
- ActionSummarize and classify threat levelOpenAI
- LogicStop low-relevance filings
- ActionCreate triaged Linear issueLinear
- OutputReturn issue link to callerHTTP webhook
What it does
This workflow turns an individual competitor patent publication into an actionable triage item. An inbound webhook delivers the filing; the workflow classifies its threat level against your active initiatives and, when relevant, creates a Linear issue assigned to the right team with the abstract, classification, and a suggested response.
When to use it
Use it when a patent-monitoring feed or alerting service can push events to a webhook and you want real-time, per-filing follow-up rather than a periodic batch. Best for teams that already run engineering and strategy work in Linear and want competitor IP to enter the same triage queue.
How it works
- 1A webhook receives a new patent filing event for a watched competitor.
- 2OpenAI summarizes the filing and classifies its threat level and affected product area.
- 3A logic branch stops low-relevance filings before they create noise.
- 4For relevant filings, a Linear issue is created with the summary, classification, and the owning team.
- 5The issue link is returned so the alerting service can record it.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.