MARKET RESEARCH
Cluster App Store reviews into feature-request themes
Scrapes recent App Store and Google Play reviews, clusters them into recurring feature-request themes with a zero-shot classifier.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionScrape App Store + Play reviewsApify
- LogicKeep only feature-request reviews
- ActionZero-shot classify into themesHugging Face
- LogicAggregate and rank themes by weighted demand
- OutputUpsert ranked theme table to CodaCoda
What it does
Every week this pulls fresh reviews for your app from both the Apple App Store and Google Play, isolates the ones asking for something new ("I wish it could…", "please add…"), groups them into named themes, and publishes a ranked table to Coda so product can see what users keep asking for.
When to use it
When your roadmap planning is driven by gut feel instead of evidence, and review volume is too high to read by hand. Best for teams that already track roadmap candidates in Coda and want a recurring, deduplicated signal of demand.
How it works
- 1A weekly schedule fires the run.
- 2Apify review scrapers fetch the latest reviews for your app IDs on both stores.
- 3A filter step keeps only reviews that express a request or unmet need, dropping pure praise and bug reports.
- 4A Hugging Face zero-shot model assigns each surviving review to a candidate feature theme and confidence score.
- 5A logic step aggregates themes, counts mentions, and computes a demand rank weighted by review recency and rating.
- 6The ranked theme table is upserted into a Coda doc, replacing last week's rows so the product team always sees current demand.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect CodaDocs, packs, automations.
- 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.