--- id: "18.7" title: "Integration roadmap" dept: integrations-and-ecosystem status: draft owner: Param branded: false last_verified: 2026-10-26 sources: - "brew origin/main: SCOPE.md:14, 32-39; connectors/index.js:28-40; docs/connectors-approvals.md:3-4, 14; DUMMY.md row 7; jam2/engines.js:1-9" - "memory brew-real-connectors, brew-name-and-scope, brew-connected-facts, treg-catalog-for-brew, brew-apify-watch, brew-higgsfield-wiring, brew-shopify-app-review, brew-meta-app-review, brew-google-oauth-scopes, brew-live-stores" - "handbook content/engineering/connectors.md, product/v2-prd.md, product/v4-prd.md, read for consistency" --- # Integration roadmap ## Answer We connect next only what a Play needs and only what the brand already uses, in this order: finish the three platform approvals so any brand connects in one click, then read the gaps Plays already ask about, then, one version at a time, the write access each version adds, each behind a person's yes. ## Today ### What is connected | Connector | State | Source | |---|---|---| | Shopify, Meta Ads, Google Analytics, Google Ads, Klaviyo, Judge.me | Real and read only on the live sites since 16 Oct | [src: brew/SCOPE.md:14] [src: memory brew-real-connectors] | | Slack | Real; posts what the team sends and brings replies back; never evidence | [src: brew/SCOPE.md:14] | | Marketplaces | Off since 16 Oct; Coming soon cards on the connectors page | [src: brew/connectors/index.js:30-32] [src: brew/DUMMY.md] | How often each re-reads and what a new connector needs is in [Connectors](/engineering/connectors) [src: brew/connectors/index.js:33-40] [src: memory brew-connected-facts]. ### What decides the order - Approvals gate every vendor; Composio, Pipedream and Nango would hit the same approvals, so we build on the platforms directly [src: brew/docs/connectors-approvals.md:3-4] [src: memory brew-real-connectors]. - Brew acts on the brand's own stack, Shopify, Meta, Google Ads and GA4, Klaviyo, reviews apps and Slack; no payments, logistics, tax or India only plumbing [src: memory brew-name-and-scope]. - Writing to accounts is cut from v1; connectors use read only scopes [src: brew/SCOPE.md:37]. ### What is waiting | Item | State | Source | |---|---|---| | Shopify public app | Submitted 21 Oct, no answer recorded | [src: memory brew-shopify-app-review] | | Meta App Review | Blocked on Business Verification and two screencasts | [src: memory brew-meta-app-review] | | Google | Verified 21 Oct | [src: memory brew-google-oauth-scopes] | ### Gaps Plays already hit | Gap | How it is filled now | Source | |---|---|---| | Indian marketplaces: Nykaa, Flipkart, Myntra | Apify actors, weekly for India | [src: memory brew-apify-watch] | | Quick commerce: Blinkit, Zepto, Instamart | Apify actors, weekly for India | [src: memory brew-apify-watch] | | Amazon | treg, weekly in every Amazon market | [src: memory brew-apify-watch] | | The brand's own Instagram posts and Search Console | Listed by treg as free when connected; no Brew connector reads them | [src: memory treg-catalog-for-brew] | | Studio partners fal, HeyGen, ElevenLabs | Named in the router, not connected, skipped | [src: brew/jam2/engines.js:8-9] | ## Tomorrow | Item | Why | Version | Tag | |---|---|---|---| | One-click Shopify from the App Store listing | Removes the own app setup for every new brand | v1 | Changes, after approval | | Meta for any brand, out of the development tier | Removes the app role step | v1 | Changes, after App Review | | Marketplaces back on, read only, from the brand's own seller account | Plays on price, stock and reviews already use shelf data | v3 | New, per the engineering plan | | Instagram and Facebook Page publishing | v2 posts and schedules after a yes; Meta is the first channel proposed | v2 | New, needs a new Meta review | | Klaviyo write key for drafts | v2 drafts an email in the brand's own tool | v2 | New | | Shopify write scopes for page or product changes | Store Plays that change the store | v2 or later | New | | Ad changes on Meta first | v4 runs ads inside rules | v4 | New, needs `ads_management` | | Search Console and own Instagram reads | Free signals Plays already describe | v2 | New | | WhatsApp or email sending as a fallback | Only for brands with no Klaviyo or WhatsApp tool | v2 | New, per the scope note | Every row after the two approvals is a proposal for Param. The engineering plan places write scopes at v3 while the version plan puts posting in v2 and ads in v4; this page follows the version plan [src: handbook engineering/connectors] [src: handbook product/v2-prd] [src: handbook product/v4-prd]. ## How we do it 1. A new connector is added only when a named Play needs its numbers and at least one design partner uses that tool. 2. Ask the platform for the smallest scope, one permission per review; never bundle scopes [src: handbook product/v2-prd]. 3. Add it to `EVERY_H`, `OPEN_H`, `NAMES` and `PRECEDENCE`, heal saved packs, and test on Cozy or Zenant before a design partner [src: memory brew-connected-facts] [src: memory brew-live-stores]. 4. Read only until the version that adds the write, and then only behind a person's yes per action [src: handbook AGENTS.md]. 5. Do not propose a connector vendor again without new facts [src: memory brew-real-connectors]. ## Numbers | Metric | Definition | Where measured | |---|---|---| | Brands with one or more live connections | Brands whose team connected at least one account | `connections` on production, Proposed | | Connections per brand | Live connections divided by brands | same, Proposed | | Days blocked on approvals | Days each platform review has been open | This page, Proposed | ## Open 1. **Which comes first after the approvals: marketplaces or Instagram reads?** Proposal: own Instagram reads, because they are free and every brand has an account. 2. **Do write scopes start at v2 or v3?** Proposal: v2 for posting only, as the version plan says, and fix the engineering table to match. 3. **Do we build email or WhatsApp sending at all?** Proposal: no in v1 and v2; send through the brand's own Klaviyo or WhatsApp tool.