MARKET RESEARCH
Support-inbox review clustering into prioritized Linear issues
When new Zendesk tickets arrive, batches and clusters their feature requests with a HuggingFace model, and once a cluster crosses a demand threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Zendesk ticket arrivesZendesk
- LogicKeep feature-request tickets
- ActionCluster ticket to a request themeHugging Face
- LogicCheck if cluster crossed demand threshold
- ActionCreate or update Linear issue with quotesLinear
- OutputLink ticket back to Linear issueZendesk
What it does
Converts the steady drip of support requests into roadmap-ready work. It groups incoming tickets by the underlying feature ask, and when enough customers have asked for the same thing, it files a single Linear issue (or bumps the count on an existing one) carrying the demand evidence and real quotes.
When to use it
Use it when valuable product signal is buried in support and never reaches the backlog. It gives PMs a deduplicated, quantified queue of customer-driven requests instead of one-off ticket forwards.
How it works
- 1A new Zendesk ticket event triggers the flow.
- 2A logic step keeps tickets tagged as requests or marked feature-related.
- 3A HuggingFace model embeds the ticket and matches it to an existing request cluster or starts a new one.
- 4Logic checks whether the cluster has crossed the demand threshold.
- 5When it has, a Linear issue is created or updated with the request count and two representative quotes.
- 6The originating Zendesk ticket is linked back to the Linear issue for the support agent.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 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
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.
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.
Weekly Hiring-Intel Briefing for GTM
An agent reviews the week's accumulated hiring signals across all target accounts, writes a narrative briefing that infers each account's likely initiatives.
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.