Connecting Revial to Salesforce
OAuth sign-in, production and sandbox orgs, connected-app approval, and what to do when the connection is blocked.
The CRM integration is set up once for the whole organisation. Salesforce connects with interactive Salesforce sign-in (OAuth) — Salesforce returns your instance URL during sign-in, so there is no URL to type for a production org.
The connection acts as a single Salesforce user and sees only what that user's
profile, permission sets, sharing rules and field-level security allow. We
recommend a dedicated integration user (for example
revialintegration@yourcompany.com).
For exactly which fields Revial reads and writes, see What Revial syncs with Salesforce. For the authentication model, API consumption and security details, see the Salesforce technical integration guide.
Overview
- Meeting briefs — enriched with opportunity stage, contacts, recent activity and account details from Salesforce.
- Meeting summaries — filed back automatically as a completed Task on the matched opportunity or account.
- Contact and company matching — meeting participants are linked to Salesforce records.
- Deal context — open opportunities, stages and amounts appear alongside meetings.
Revial reads Accounts, Contacts, unconverted Leads, Opportunities (open, plus those modified in the last 12 months on the first sync), opportunity stages, Events, Tasks, EmailMessages and classic Notes.
Requirements
- Revial role: Admin or Owner in your organisation.
- Revial plan: one that includes the CRM integration (Medium or Sales).
- Salesforce user: API access enabled ("API Enabled") and read access to the objects listed above. A standard sales profile is normally enough.
- Salesforce edition with API access — Enterprise, Unlimited, Performance or Developer. API access is not included in Essentials and is an add-on in Professional.
- If your org restricts connected apps: a Salesforce administrator who can approve the Revial app (see below).
Step 1 — Open CRM Integrations
- In Revial, go to Organization → CRM Integrations.
- Find the Salesforce card (Not connected).
Step 2 — Connect
Production org: click Connect with Salesforce.
Sandbox org: tick Sandbox org and enter the sandbox's own login host in
Salesforce login host, without https:// — for example
acme--uat.sandbox.my.salesforce.com. Then click Connect with Salesforce.
Use the sandbox's own host, not the generic test.salesforce.com. The generic
host sends a user who already has a Salesforce session to whichever org they
are signed in to, which can connect your production org by mistake.
Salesforce always shows its login screen, even if you are already signed in, so you choose the account the integration will use. Sign in, review the requested permissions and click Allow.
Before saving anything, Revial exchanges the authorisation code for tokens, checks the instance URL and reads the signed-in user's profile. If any step fails, nothing is saved and you return to CRM Integrations with an error message.
Step 3 — Verify the connection
You return to Revial with the message "CRM connected successfully". The card shows Connected, the Salesforce user's email, Sync Now and Disconnect. Check that the email is the account you intended.
First sync
The first sync starts automatically in the background when you connect. After that Revial syncs roughly every hour while Automatic Sync is on in CRM Settings (it is on by default). Sync Now starts a sync straight away.
For the Salesforce admin — approving the connected app
If your org restricts which connected apps users may authorise, an administrator has to approve Revial before users can connect.
When is this needed? A user sees "This app is blocked", "OAuth error: this app is not approved for access", or the sign-in fails right after Allow.
- Sign in to Salesforce as a System Administrator.
- Go to Setup → Apps → Connected Apps → Connected Apps OAuth Usage.
- Find Revial — it appears after the first connection attempt.
- Click Install / Manage → Edit Policies.
- Set Permitted Users (for example "Admin approved users are pre-authorized") and assign the relevant profile or permission set.
- Save.
Also check that the connecting user's profile has API Enabled — without it, sign-in succeeds but every API call fails.
Managing the connection
Syncing — Sync Now on the Salesforce card starts a sync; the Automatic Sync toggle in Organization → CRM Settings turns hourly syncing on or off. Turning it off also stops meeting summaries being pushed automatically.
Disconnecting — Disconnect on the Salesforce card, then confirm. Revial stops syncing and, in the background, deletes its synced copy of your Salesforce data, the stored tokens and the connection's settings (field mappings included). Tasks and records Revial already wrote stay in Salesforce.
Disconnecting in Revial does not revoke Revial's access in Salesforce. To end the grant, revoke the app under Setup → Connected Apps OAuth Usage, or deactivate the connecting user.
Changing the connected user — disconnect, wait for the disconnection to finish, then connect again signing in as the new user. While a Salesforce connection is still connected, a new connection is refused.
Troubleshooting
Connection errors
| Message | What to do |
|---|---|
| "This app is blocked" / sign-in fails right after Allow | A Salesforce administrator must approve the Revial app — see above |
| "Connection cancelled" | Permission was denied on the Salesforce screen. Connect again and click Allow |
| "Failed to authenticate with Salesforce" | The code exchange failed — usually the sign-in was interrupted. Try again |
| "Failed to validate Salesforce access" | Sign-in worked but the profile check failed. Check the user has API Enabled and your edition includes API access |
| "Missing instance URL from Salesforce" / "Not a recognized Salesforce domain" | Salesforce returned an instance outside *.salesforce.com or *.force.com. Contact Revial support with your org's My Domain URL |
| "Invalid or expired state" | More than five minutes passed during sign-in. Start again from CRM Integrations |
| "Invalid Salesforce login host…" | The sandbox host is not a Salesforce domain. Enter the sandbox's own host, for example acme--uat.sandbox.my.salesforce.com |
| "Team already has an active Salesforce connection. Disconnect it first." | Disconnect the existing Salesforce connection first |
| "You must be a team admin or owner to connect a CRM" | Ask a Revial organisation admin or owner to connect |
| "CRM integration is not available on your current plan…" | Your plan does not include the CRM integration |
| "Too many requests. Please try again later." | Too many attempts in a short time. Wait a minute and retry |
| "Failed to save connection" | Revial could not store the connection. Try again; contact support if it repeats |
Sync problems
| Symptom | What to do |
|---|---|
| Data is missing after a sync | The connecting user cannot see those records — check sharing rules, role and object permissions |
| Emails, Events or Tasks missing, and the connection asks to be re-authorised | The user lacks read access to that object. Grant it; the rest of the sync still completes |
| A notification says "CRM: Authentication expired" | The refresh token was revoked — the app was revoked, the user deactivated or their password reset. Disconnect and connect again |
| A record deleted in Salesforce still shows in Revial | Expected — Revial does not detect Salesforce deletions |
Quick guide — connecting
- Revial → Organization → CRM Integrations → Salesforce.
- Sandbox only: tick Sandbox org and enter the sandbox's own login host.
- Click Connect with Salesforce, sign in as the integration user, click Allow.
- If the app is blocked, ask your Salesforce administrator to approve it.
- Check the email shown on the card. The first sync starts automatically.
Pipedrive technical integration guide
For Pipedrive administrators, security reviewers and IT — how Revial authenticates, the scopes and access it relies on, API consumption, failure behaviour and auditing.
What Revial syncs with Salesforce
For your Salesforce administrator and whoever reviews the integration's data access — every Salesforce field Revial reads, everything it writes back, and the known gaps.