MARKET RESEARCH
Weekly cross-store version sentiment divergence digest
Each week compares feature sentiment between iOS and Android for the current release and emails product a digest highlighting features that regressed on one platform but not…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionScrape current-version reviews from iOS and AndroidApify
- ActionScore feature sentiment per platformOpenAI
- LogicCompute per-feature cross-store divergence
- ActionCompose divergence digestOpenAI
- OutputEmail digest to product listGmail
What it does
Once a week it gathers the current-release reviews from both the iOS App Store and Google Play, scores feature sentiment on each platform, and computes where the two diverge. It then composes an email digest that highlights features doing fine on one OS but suffering on the other, with the gap size and sample reviews, so platform-specific regressions get attention.
When to use it
Use it when your app ships to both stores and a release can break a feature on only one platform. Cross-store divergence is easy to miss because each store's overall rating looks acceptable in isolation; this digest puts them side by side.
How it works
- 1A weekly schedule starts the run.
- 2Apify scrapes current-version reviews from both stores.
- 3OpenAI scores feature sentiment separately per platform.
- 4The flow computes per-feature divergence between iOS and Android.
- 5OpenAI writes a digest emphasizing the widest single-platform regressions.
- 6Gmail sends the digest to the product distribution list.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GmailRead, draft, send, label.
- 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.