Connecting Revial to Pipedrive

Revial connects to Pipedrive as a Pipedrive Marketplace OAuth app. There is no API token to paste and no service account to provision. One person authorises the app once; Revial then holds a refresh token bound to that person's Pipedrive user and company.

Because Revial acts as that person, the connection sees exactly what they see. That single fact decides the scope of the integration, and section 2 covers it in full.

For every field Revial reads and writes, see What Revial syncs with Pipedrive. For the token model, API consumption and failure behaviour, see the Pipedrive technical integration guide.

1. What you need to determine before connectingCopy Anchor Link

1.1 Who authorises the connectionCopy Anchor Link

What it decides: everything Revial can see and everything it can write. Revial calls the Pipedrive API with that user's token, so it sees exactly the deals, persons and organizations that user sees, and writes as that user.

• If Revial should cover the whole pipeline, authorise with an admin account or any account with company-wide visibility.
• If Revial should be limited to a subset, authorise with a user whose Pipedrive visibility groups and permission set already restrict them to that subset. This is the only scoping mechanism available.

We recommend a dedicated, named integration user — for continuity: if a salesperson leaves and their account is deactivated, the connection stops.

1.2 Whether meeting data should land in fieldsCopy Anchor Link

Revial writes each meeting summary as a Pipedrive note. If you also want values — a summary, the transcript, or custom extraction fields — in specific fields on the deal, person or organization, an admin can map them in Revial (section 6). The fields must already exist.

2. Important: OAuth scopes cannot separate B2B from B2CCopy Anchor Link

A Pipedrive OAuth scope controls which endpoints an app may call and whether it may read or write. It does not filter rows. Granting persons:read grants read on every person the authorising user can see.

Row-level restriction comes from the user's own permissions: their permission set and visibility groups. Since Revial acts as that user, those restrictions carry through — inherited, not configured for Revial.

The sync copies everything the authorising user can see. Writes only go to records matched to a meeting's attendees — a behavioural property of the product, not a Pipedrive-enforced restriction.

3. ConnectingCopy Anchor Link

Performed by the Pipedrive user chosen in 1.1, who must also be an Admin or Owner in Revial on a plan that includes the CRM integration (Medium or Sales).

1. In Revial, go to Organization → CRM Integrations.
2. On the Pipedrive card, click Connect with Pipedrive.
3. Sign in to Pipedrive as the account chosen in 1.1. If a different account is already signed in, sign out first — the authorisation binds to whoever is signed in.
4. Review the requested access and approve the installation.
5. You return to Revial with "CRM connected successfully". The card shows Connected and the Pipedrive email of the authorising user. Check that email.

Revial checks the token with GET /api/v1/users/me before storing anything, and starts the first sync straight away.

One Pipedrive connection per organisation. A second Pipedrive connection is refused while one is connected. Other CRMs can be connected alongside it.

If you install Revial from the Pipedrive Marketplace instead, Revial shows "App installed! Click Connect to complete the setup." — finish with step 2.

4. The scopes on Revial's Pipedrive appCopy Anchor Link

These are set on the Marketplace app and are the same for every customer; Revial sends no scope parameter.

The write scopes are broader than what Revial does with them. Pipedrive has no field-level scope, and Revial's field mapping can target any field, standard ones included. The boundary is what your admins map — enforced by Revial's software, not by the scope. If you need platform-level enforcement, the lever is the authorising user's permission set.

5. What Revial reads and writesCopy Anchor Link

Reads:

After the first full sync, syncs are incremental (updated_since) and run roughly every hour. Records Pipedrive flags as deleted are removed from Revial's copy on incremental syncs; a full sync does not filter them out.

Writes:

Revial does not create activities, deals, persons or organizations, and does not add deal participants.

Partial failures are reported, not hidden. If the first pipeline's stages cannot be read, or deal participants fail, the sync is marked partial. A rate-limit response while reading participants fails that sync's deals step, which is retried.

Notes are attributed to the authorising user, because that is whose token makes the call. Revial sets no separate owner.

6. Field mappingCopy Anchor Link

Organisation admins and owners map Revial summary fields and custom extraction fields to Pipedrive fields under Organization → CRM Settings → Property Mapping. Revial lists your person, deal and organization fields, custom ones included.

• The field must already exist; Revial does not change your Pipedrive schema.
• A field that already has a value is left alone unless the mapping is set to overwrite.
• If a batch update fails, Revial retries each field individually and reports which ones failed.
• The full transcript can reach Pipedrive only through a mapped field.

7. What Revial deliberately does not doCopy Anchor Link

Revial has no delete capability on any Pipedrive entity. It does not create or modify fields, does not change pipelines or stages, does not alter user permissions and does not touch company settings.

Revial requests no mail scope and never reads email content. It does read the last_incoming_mail_time and last_outgoing_mail_time timestamps on persons to judge whether a deal has gone quiet.

These boundaries rest on what the software does, not on a Pipedrive permission. The one boundary Pipedrive itself enforces is the authorising user's visibility.

8. Credentials, expiry and revoking accessCopy Anchor Link

Access tokens are refreshed automatically before they expire. If Pipedrive issues a new refresh token, Revial stores it. There is no rotation task for you.

A refresh token stops working when the authorising user is deactivated, the app is uninstalled, or Pipedrive invalidates it. Revial then marks the connection as needing re-authorisation and an organisation admin receives the notification "CRM: Authentication expired".

To revoke Revial's access: uninstall the Revial app from Pipedrive, or deactivate the authorising user.

Disconnecting in Revial (Organization → CRM Integrations → Disconnect) stops syncing and, in the background, deletes Revial's synced copy of your Pipedrive data, the stored tokens and the field mappings.

Notes and field values Revial already wrote into Pipedrive stay there.

9. Verifying the connectionCopy Anchor Link

1. The connection is accepted and the email shown is the intended account.
2. The first sync populates organizations, persons and deals — confirms the read scopes and the authorising user's visibility.
3. A deal is linked to the right organization and person.
4. Push a test meeting note to a known deal — confirms note creation.
5. If you use field mapping, check the mapped field was written.
6. For case A in section 2, confirm a consumer record is absent from the synced data.

10. TroubleshootingCopy Anchor Link

11. Questions to raise with us before connectingCopy Anchor Link

• Your consumer and business records are separated only by a field value (case C).
• You need per-seller attribution on notes written into Pipedrive.
• You need Revial restricted to specific pipelines.
• Your review requires the unused scopes in section 4 removed.