OppFlow.ai Docs

Integrations

What connects, and how

One table, honestly maintained. Live means implemented and offered to you. Anything not listed as live is not connectable, whatever a marketing page says.

IntegrationStatus
SalesforceLIVE
HubSpotLIVE
Google Workspace — mail & calendarLIVE
Microsoft 365 — mail & calendarLIVE
Knobs — mail & calendarPER-CUSTOMER
Gong — recorded callsLIVE
Product-usage sourcesLIVE
Company enrichmentOPT-IN · ADMIN API
Stripe billingTEST MODE
Bug & feature pipelinePARTIAL
Pipedrive · Glean · ZoomNOT AVAILABLE

How connecting works

Most connections are OAuth. OppFlow mints a single-use state token valid for ten minutes and bound to you, sends you to the provider's consent screen, and on return stores the access token, the refresh token, the real expiry and the scopes the provider actually granted. Access and refresh tokens are encrypted at rest on a deployment configured with an encryption key; the recorded expiry and scope list are not secrets and are stored as-is.

A connection that lapses is reported differently from one that never existed, because they need different fixes: one needs a re-consent, the other needs a first connect.

Org-level vs per-person

CRM, Gong, usage sources, enrichment and billing are workspace-level and configured once by an admin. Mail and calendar are per-person — the admin chooses the provider, each individual connects their own mailbox.

OppFlow.ai docs · by Traversal · v0.1.32