Skip to main content
Outlit monitors what it can see. Every source you connect — billing, product usage, CRM, conversations, support — sharpens customer profiles and widens what monitoring can catch. You connect sources once from Integrations in the app, and Outlit keeps them in sync. The Outlit Browser SDK adds the website visits that precede those customer records.

​
Before you start

  • Workspace access. You have signed in at app.outlit.ai to a workspace provisioned with Outlit.
  • Who can connect what. Admins can connect any source. Members can connect their own accounts where the source is per-person (Gmail, Granola personal keys) — see roles and access.
  • Admin rights at the source. Some connections need privileges on the other side: Salesforce requires a Salesforce admin, and API-key sources need a key you can create in that tool.

​
Connect a source

1

Open Integrations

In the app sidebar, open Integrations — or finish the connect step of onboarding, which shows the same catalog grouped by what each source adds: revenue, customer records, conversations, and product usage.
2

Choose a source and connect

Click Connect on a card. Depending on the source you’ll either authorize Outlit in a popup (OAuth — Stripe, Salesforce, HubSpot, Attio, Slack, Google, Gong) or paste a key you create in that tool (PostHog, Pylon, Fireflies, Granola, Autumn, Supabase Auth, Clerk). Mixpanel uses a service-account username and secret, project ID, and region. See the integrations guides for exactly what each one asks for.
3

Finish required setup

Some sources need one more step before their data counts: CRM connections ask you to map the pipeline — renewal stages, won/lost outcomes, and the renewal-date field; Gong and Pylon need a webhook; Slack asks which channels to include; and Mixpanel needs its account-property mapping confirmed. The app flags these on the source and in onboarding’s Setup step.
4

Wait for the first sync

First-sync time varies by source and how much history it holds. The Attention page tells you where you stand — see below.

​
How you know it’s working

The Attention page reflects your data state until the first item arrives: Once imports land, customers appear in Customers, and the first attention items start arriving as monitoring sees enough signal to say something.

​
Which sources matter most

Monitoring is only as good as its inputs. For churn and renewal coverage, these do the most work: If you can only connect two things first, connect Stripe and a product-usage source — they cover the inputs churn monitoring checks. Whether monitoring is actually active depends on coverage and your workspace’s responsibilities being enabled: open Responsibilities → Churn and the status card shows readiness plus anything still missing. Add a CRM to get renewals, conversations for evidence quality, and the Outlit Browser SDK for the journey from first visit to conversion.

​
Troubleshooting

Monitoring needs eligible accounts (paying or past-due customers for churn) plus enough signal to justify an item. Check Responsibilities → Churn for the monitoring status card — it lists reduced-coverage reasons like a missing billing source, missing product source, or missing notification destination.
Open Integrations and review the flagged card — usually re-authorization or a missing webhook. See the integrations overview for per-source specifics.
Gmail connects per teammate — each person syncs their own mailbox, so shared coverage grows as teammates connect. Most other sources connect once for the whole workspace.

​
Next steps

Review your first attention item

What lands when monitoring finds something

Integration guides

Per-source connect steps and requirements