Integrations
CRM, calendar, mailbox, Slack, meeting bots and knowledge connectors, all OAuth-based.
Every integration connects from Settings → Integrations with the provider's own consent screen. RepCue stores only the tokens it needs, encrypted with AES-256-GCM, and each integration shows its health, last sync and a disconnect button.
Overview
| Integration | Direction | What it does |
|---|---|---|
| Salesforce | in + out | Opportunity, account and contacts into the call pack; rep-approved field diffs written back |
| HubSpot | in + out | Same, for deals and companies |
| Pipedrive | in + out | Same, for deals (API-token based) |
| in + out | Calendar auto-arm and pre-call brief; send follow-ups through Gmail as the rep | |
| Microsoft 365 | in + out | Same via Outlook calendar and mail (Graph) |
| Slack | out | Post-call summaries to deal channels, coaching digests |
| Recall | in | Dispatch a meeting bot to a Zoom/Meet/Teams link when the desktop app can't be installed |
| Notion / Google Drive / Confluence | in | Knowledge connectors; see Knowledge base |
CRM
What comes in
At arm time RepCue builds a call pack: the matched deal (by calendar attendee domain, CRM lookup, or the rep's choice), its stage and amount, the contacts on the call, the last call's summary and open action items, and the battlecards most relevant to the stage. That pack is what makes the first suggestion on a call specific to this account.
What goes out
After the call, the post-call pipeline proposes field changes (stage, close date, next step, MEDDIC fields, new contacts) as explicit diffs: Stage: Evaluation → Negotiation. Nothing is written until a person approves, from the desktop review sheet or the console. Each approval is audit-logged with who, when and the before/after values.
Connecting
- Salesforce: OAuth2 connected app. Requires API access on the user's profile. Sandbox orgs work; set the instance when prompted.
- HubSpot: OAuth2 app with
crm.objects.dealsandcrm.objects.contactsread/write scopes. - Pipedrive: paste a company API token (Pipedrive's OAuth app review is in progress). The token is vaulted like any OAuth credential.
Only admins can connect a CRM; every rep's calls use the org-level connection, writes are attributed to the approving user.
Calendar + mailbox (Google, Microsoft)
Connect once per user. The desktop app reads the next 24 hours of events, arms the HUD two minutes before any meeting with a join link, and shows the pre-call brief. Mail scope lets the follow-up go out from the rep's address, in their sent folder, with the thread intact. Calendar and mail scopes can be granted separately.
Without a mailbox connection, follow-ups send from RepCue's domain with reply-to set to the rep.
Slack
A bot user posts the post-call summary, action items and link to the call into the channel you map per deal or per team. Coaching digests (weekly adoption, top objections) can go to a managers channel.
Recall meeting bot
For locked-down machines. From the console or the calendar brief, dispatch a bot to a meeting URL; it joins as a visible participant named RepCue Notetaker, streams audio to the same pipeline, and the rep sees cards in the console's live view. Higher latency than the desktop app and always visible by design; it aligns with the consent posture rather than hiding from it.
Health, sync, disconnect
Each card in Settings → Integrations shows connected as, last successful sync, and token expiry. Sync now forces a refresh; Disconnect revokes the token with the provider where the API allows and deletes it from the vault. Outbound writes that fail are retried with backoff and surface in the audit log, so a CRM outage never blocks the review sheet.