Enrich the page. Approve the write. Same Outcomes as chat.
Gravitree on LinkedIn, Gmail, Outlook, and company sites — catalog actions only, human approval before writes, full audit in Outcomes. Not a parallel CRM bot.
Supported: Chrome, Edge, Brave (same MV3 pack). Not supported: Firefox, Safari, or mobile. Chrome Web Store listing not published yet — use the setup guide (load unpacked).
Activation in five steps
The milestone that matters: install → connect → enrich → approve → Outcomes. Minutes, not a project plan.
- 1
Install
Add the Gravitree extension in Chrome (store listing when published, or load-unpacked beta).
- 2
Connect
Authorize from the popup — same org session as gravitre.app. No second identity system.
- 3
Enrich
Open a LinkedIn profile (or Gmail / Outlook / company page). Overlay runs catalog reads from page context.
- 4
Approve a write
Confirm once. Creates go through catalog write authority — not DOM clicking in HubSpot or Apollo.
- 5
See Outcomes
The run lands in Outcomes / Runs with source browser_extension — same visibility as chat.
Steps 3 and 4, on the page
The overlay opens beside whatever you are already looking at. You never leave the tab to enrich, and you never leave it to approve.
Step 3 — enrich from page context
Catalog reads run against the tab you are on. Nothing is read until you open the overlay.
Step 4 — confirm the write
The overlay names the exact catalog action before anything is committed. One confirmation, in the same panel.
Supporting proof
No separate queue, no separate audit trail
The overlay does not get its own approval queue or audit trail. A staged write waits in the same Approvals queue as chat, and the run lands in the same Activity feed — tagged with its source.
Step 4, in the app — the shared Approvals queue
The same confirmation you just saw in the overlay also appears here, with the exact catalog action, its blast radius, and who asked for it.
Step 5, in the app — see it in Outcomes
Extension runs appear with source browser_extension and the same lifecycle chain as chat — planned, approved, executed, verified.
Supported surfaces
Explicit host allowlist — no silent expansion. Page context only; creates and list membership use governed catalog actions (Apollo / HubSpot where connected). Outside-allowlist attempts are recorded as usage signals for prioritization, not as new permissions.
- LinkedIn profiles
- Gmail
- Outlook on the web
- Company websites (when you invoke Enrich)
- Careers / about pages (path-matched)
- Salesforce Lightning / Force hosts
- Slack web (app.slack.com)
Salesforce and Slack overlays use page context plus connected catalog actions (Apollo / HubSpot today). Native Salesforce lead search/create and Slack user lookup activate when those connectors are connected — still catalog only, never DOM automation.
Same governance as chat
Writes stage awaiting confirmation with a server-issued token. Org membership is enforced. Outcomes use Module A finalize — not a side channel.
What it will not do
No InMail spam, no clicking Salesforce/HubSpot UI for you, no agentic multi-step form control. If a catalog action exists, we call it.
Quick chat on the page
Ask a short, page-contextual question in the overlay — same unified-turn path as Gravitree chat. Writes and multi-step work hand off to the full app on the same conversation thread (where the progress panel lives). Proven thread: overlay Q → write handoff.
Workflows from the overlay
Trigger existing typed workflows with the same plan-bar approve pattern as chat — named step labels stay visible while it runs, then open the Outcomes chain. Proven runs: NVD + CISA KEV, HubSpot pipelines + deals, Apollo orgs + HubSpot pipelines.
Ready for first value?
Connect HubSpot or Apollo, install the extension, enrich one profile, approve one write, open Outcomes.