Connect the systems your team already uses
FrontRace listens across CRM, email, phone, video, and collaboration tools. Connections are secure, read-only by default, and take minutes per source.
What FrontRace listens to
CRM
Accounts, opportunities, contacts, stages, owners, and activity — the backbone of the decision model.
Email & calendar
Meeting cadence, threads, attendees, and response patterns — to see what's actually happening between CRM notes.
Phone & dialer
Call activity, duration, and outcomes from RingCentral, PhoneBurner, CallRail, and others.
Video & conversation
Meeting recordings, transcripts, and call intelligence from Zoom, Google Meet, and Gong.
Collaboration
Slack and Microsoft Teams for in-channel signals and internal deal discussion context.
Knowledge
Notion and similar tools for playbooks, battlecards, and enablement context.
How to connect a source
-
Open Integrations
You'll see every supported source grouped by category, with a Connect button next to each.
-
Authorize via OAuth or API key
Most connections are OAuth. A few (Close, Crelate, Avianis, Gong, CallRail) use an API key generated from within that product's settings.
-
Scope permissions to read-only
Use the least-privilege option wherever available. FrontRace never needs write access to run the decision model.
-
Select what to ingest
Pick which accounts, mailboxes, channels, or workspaces to include. You can exclude anything sensitive or out of scope.
-
Confirm the backfill
FrontRace pulls up to 24 months of history by default to calibrate the model. Backfills usually complete within a few hours.
Start with the core three
At minimum, FrontRace needs these three to produce real guidance:
- Your CRM — the source of truth for pipeline and outcomes.
- Email and calendar — Google Workspace or Microsoft 365.
- One conversation source — phone, video, or dialer.
Anything beyond these three sharpens the model and unlocks more signals.
No pixel, no plugin. Reps don't install a browser extension or a desktop app. All data flows through authenticated APIs.
What we read and don't read
| We read | We don't |
|---|---|
| Business email threads with external contacts | Personal email or threads you've marked private |
| Meeting metadata, recordings, and transcripts on business accounts | Meetings you haven't granted access to |
| Channel messages where FrontRace is invited | DMs, and channels FrontRace isn't in |
| CRM records you already have access to | Records outside your permission boundary |
Security and compliance
- All credentials encrypted at rest (AES-256) and in transit (TLS 1.2+).
- Read-only OAuth scopes wherever the platform supports them.
- Per-user and per-workspace data isolation.
- SSO and SCIM available on supported plans.
- SOC 2 Type II report available on request.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| CRM opportunities missing | OAuth user lacks permission to the object or record type. Reconnect with a full-access admin. |
| Call or meeting activity delayed | Provider webhook delay — typically resolves within an hour. |
| Transcripts not appearing | Recording or transcription isn't enabled in the upstream tool (Zoom, Gong, etc.). |
| API key rejected | Key was rotated or scoped incorrectly in the source system. Regenerate with full read scope. |
For the complete list of integrations, see Integrations. To understand what FrontRace does with this data, see How It Works.