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.
This page lists, field by field, what Revial reads from Salesforce and what it
writes back. For connecting and permissions, see
Connecting Revial to Salesforce. Field names
in code are Salesforce API names.
Everything runs as the Salesforce user who authorised the connection, so the user's profile, permission sets, sharing rules and field-level security decide what Revial can see and change.
1. How the sync runs
- A sync runs roughly every hour, starting as soon as you connect. The first
one reads everything; later ones read only records with a newer
LastModifiedDate. - On a full sync, Opportunities are limited to open deals plus deals modified in the last 12 months.
- Each object is capped at 50,000 records per sync.
- If field-level security hides a field Revial asks for, Revial drops that field and continues. If the user cannot read Event, Task or EmailMessage at all, that object is skipped and the connection is flagged for re-authorisation.
- Revial stores each record as returned, alongside the fields mapped below.
- Disconnecting deletes Revial's synced copy of your Salesforce data.
2. Accounts
| In Revial | Salesforce field |
|---|---|
| Name | Name |
| Website, phone, industry | Website, Phone, Industry |
| Employees, annual revenue | NumberOfEmployees, AnnualRevenue |
| Description | Description |
| Billing address | BillingStreet, BillingCity, BillingState, BillingPostalCode, BillingCountry |
| Created / modified | CreatedDate, LastModifiedDate |
3. Contacts
| In Revial | Salesforce field |
|---|---|
| First, last and full name | FirstName, LastName |
Email | |
| Work and mobile phone | Phone, MobilePhone |
| Title, department | Title, Department |
| Mailing address | MailingStreet, MailingCity, MailingState, MailingPostalCode, MailingCountry |
| Account | AccountId |
| Last activity | LastActivityDate |
4. Leads
Unconverted leads only (IsConverted = false).
| In Revial | Salesforce field |
|---|---|
| Name, email, phones | FirstName, LastName, Email, Phone, MobilePhone |
| Company, title | Company, Title |
| Description, source | Description, LeadSource |
| Status | Status, grouped into open / qualified / disqualified |
5. Opportunities
| In Revial | Salesforce field |
|---|---|
| Deal name | Name |
| Value | Amount |
| Stage | StageName, matched against your opportunity stages |
| Status (open / won / lost) | IsClosed, IsWon |
| Win probability | Probability |
| Expected close date | CloseDate |
| Actual close date | CloseDate, once closed |
| Stage entered | LastStageChangeDate |
| Last activity | LastActivityDate |
| Account | AccountId |
| Contacts and primary contact | OpportunityContactRole — ContactId, IsPrimary |
Revial also reads your active OpportunityStage records (MasterLabel,
SortOrder, IsClosed, IsWon). Stage history is not read from Salesforce —
Revial records stage changes it sees between syncs.
6. Activities, emails and notes
| Object | What Revial reads |
|---|---|
| Event | Subject, Description, StartDateTime, duration, Location, WhoId (contact), WhatId (opportunity) |
| Task (not email tasks) | Subject, Description, ActivityDate, call type and duration, Status, WhoId, WhatId, OwnerId |
| EmailMessage | Subject, TextBody — the full email text, MessageDate, Incoming, Status, RelatedToId, and the contacts on the email via EmailMessageRelation |
| Note (classic) | Title, Body, ParentId |
Revial reads the full text of emails stored in Salesforce as EmailMessage records. If email content must stay out of Revial, remove the authorising user's read access to EmailMessage — Revial then skips it.
7. What Revial does not read
- Owners on Accounts, Contacts, Opportunities, Leads and Events (Task owner is read).
- Currency (
CurrencyIsoCode) and custom fields. - Products, files, attachments, Lightning notes (ContentNote), Cases and Campaigns.
- Record types and field history.
8. Known limitations when reading
- Every amount is shown in euros, whatever the opportunity's currency.
- Deletions are not detected. A record deleted in Salesforce stays in Revial's copy, and so does a lead after it is converted.
- Records beyond the 50,000 cap are skipped and are not picked up by later syncs.
- All opportunities share one pipeline in Revial; record types and sales processes are ignored.
- Disqualified leads can show as qualified, because the status grouping matches "qualif" first.
- Events always show as scheduled, including past ones, and an Event linked only to an Account is not linked to the company in Revial.
9. What Revial writes to Salesforce
Revial never deletes anything in Salesforce and never creates Accounts, Contacts, Leads or Opportunities.
9.1 Meeting summary Task — automatic
After a meeting's summary is ready, Revial creates a completed Task:
| Task field | Value |
|---|---|
Subject | "Meeting Summary – meeting title" |
Description | The summary as plain text: your note template, a link to the meeting in Revial and an AI-generated notice. Capped at 64 KB |
Status, Priority | Completed, Normal |
WhoId | The matched contact |
WhatId | The matched opportunity, otherwise the account |
- Attached to: the matched opportunity; if none, the account; if none, one Task per matched contact. Admins can change this order in CRM settings.
- Written once per meeting, in your CRM output language if one is set.
- No
ActivityDateorOwnerIdis set, so the Task is owned by the authorising user.
Automatic pushing can be switched off for a connection by Revial support. Any team member can also push a summary manually, editing it first.
9.2 Mapped fields — optional
Admins can map Revial summary fields and custom extraction fields to fields on Contacts, Accounts and Opportunities.
- Revial updates the matched record only.
- A field that already has a value is left alone, unless that mapping is set to overwrite. Revial reads the current values first.
- Values are converted to the field type; text is capped at 64 KB.
- Any field the authorising user can edit can be mapped, standard ones included.
- If a batch update fails, each field is retried once individually.
9.3 Visit Reports — set up per organisation
If Revial has configured a Visit Report custom object for your organisation, a meeting creates a Visit Report record instead of a Task: notes, subject, visit date, contact, account, opportunity, extracted picklist and checkbox values, and a needs-review flag.
Revial then updates the matched Event: a link to the new Visit Report and, where configured, a stakeholder picklist and an owner field set to the seller — which can reassign the Event's owner. These are the only writes Revial makes to records it did not create.
9.4 Not written to Salesforce
- New opportunities — deal creation is not available for Salesforce.
- Transcript notes and Events.
Connecting Revial to Salesforce
OAuth sign-in, production and sandbox orgs, connected-app approval, and what to do when the connection is blocked.
Salesforce technical integration guide
For Salesforce administrators, security reviewers and IT — how Revial authenticates, what it reads and writes, the permissions it needs, API consumption, failure behaviour and auditing.