Review Intelligence to Notion — Cross-Platform Review Feed API
Pricing
from $100.00 / 1,000 brand scorecards
Review Intelligence to Notion — Cross-Platform Review Feed API
Pricing
from $100.00 / 1,000 brand scorecards
What to score, one per line. The format depends on the chosen source: • app_store — App Store name, numeric App ID, or apps.apple.com URL (e.g. 'Notion', '1232780281', 'https://apps.apple.com/us/app/notion/id1232780281'). • google_play — Play package id, Play Store URL, or app name (e.g. 'com.spotify.music', 'Notion'). • g2 — G2 product slug or product page URL (e.g. 'slack'). • trustpilot — company name or Trustpilot domain/URL (e.g. 'amazon.com', 'https://www.trustpilot.com/review/stripe.com'). Public review data only.
[ "Notion", "Spotify"]Which public review source to read from. app_store (Apple App Store) and google_play (Google Play) are the proven, ~93%+ reliable primary sources. g2 and trustpilot are also available but may be anti-bot blocked.
Maximum number of reviews to read per item before computing the scorecard (more reviews = more reliable themes and trend).
Storefront / region code for app_store and google_play (us, gb, ca, de, fr, jp, br, in, au, mx, etc.). For App Store, if the chosen storefront returns nothing the Actor automatically falls back to other storefronts. Ignored for g2/trustpilot.
Language code for google_play reviews (e.g. en, es, de, fr). Ignored for other sources.
Review ordering for app_store / google_play: newest first or most relevant/helpful first.
Connect your Notion workspace and this Actor writes the scorecards into a brand-new Notion database in the same run — it never sees your Notion credentials. Authorize a Notion MCP connector in Apify Console → Settings → API & Integrations, then select it here. (Without a connector you get the dataset only.)
Optional. The Notion page ID to create the scorecard database under. If blank, Notion creates it as a private page in your workspace.
Optional. Connect your own Supabase project and the results are also inserted into a table in the same run — the Actor never sees your Supabase credentials. Authorize a write-scoped, project-scoped Supabase MCP connector in Apify Console (Settings -> Integrations), then select it here.
Target table in the public schema (created if missing, with id, a jsonb data column, and a scraped_at timestamp). Default: nexgendata_leads.
Your Supabase project reference (e.g. abcdefghijklmnop). Required unless your connector URL is already project-scoped. Find it in your project URL: supabase.com/dashboard/project/THIS_PART.