What Revial syncs with Pipedrive
For your Pipedrive administrator and whoever reviews the integration's data access — every Pipedrive field Revial reads, everything it writes back, and the known gaps.
This page lists, field by field, what Revial reads from Pipedrive and what it
writes back. For connecting, scopes and revoking access, see
Connecting Revial to Pipedrive. Field names in
code are Pipedrive API field names.
Everything runs as the Pipedrive user who authorised the connection, so Revial sees exactly what that user sees.
1. How the sync runs
- A sync runs roughly every hour. The first one reads everything; later ones
read only records updated since the previous sync (
updated_since). - Each record type is capped at 50,000 records per sync.
- Revial requests Pipedrive's standard record and stores it as returned, alongside the fields mapped below. Only the fields in the tables are used.
- Records Pipedrive marks as deleted are removed from Revial's copy on incremental syncs.
- Disconnecting deletes Revial's synced copy of your Pipedrive data.
2. Organizations
| In Revial | Pipedrive field |
|---|---|
| Name | name |
| Address | The organization's address parts |
| Created / updated | add_time, update_time |
Website, phone, industry, employee count and revenue are not read from Pipedrive organizations.
3. Persons
| In Revial | Pipedrive field |
|---|---|
| First, last and full name | first_name, last_name, name |
| Email addresses | emails — every address with its label; the primary one is used for matching |
| Phone numbers | phones — every number with its label |
| Job title | job_title |
| Organization | org_id |
| Last email received / sent | last_incoming_mail_time, last_outgoing_mail_time |
| Last activity | last_activity_date |
The two email timestamps help Revial judge whether a deal has gone quiet. Revial never reads email subjects, bodies or recipients.
4. Deals
| In Revial | Pipedrive field |
|---|---|
| Deal name | title |
| Value and currency | value, currency |
| Status (open / won / lost) | status |
| Win probability | probability |
| Expected close date | expected_close_date |
| Actual close date | won_time, lost_time or close_time, once the deal is closed |
| Pipeline and stage | pipeline_id, stage_id |
| Stage entered | stage_change_time |
| Last activity | last_activity_date |
| Organization and primary person | org_id, person_id |
| All participants | /api/v1/deals/{id}/participants — person_id and primary flag |
5. Pipelines and stages
Revial reads your first pipeline's stages: id, name and order_nr.
6. Activities and notes
| Type | What Revial reads |
|---|---|
| Activities (all types) | type, subject, note, done, due_date and due_time, duration, location, linked person, organization and deal |
| Notes | content (converted to plain text), linked person, organization and deal |
7. What Revial does not read
- Email content — Revial requests no mail scope.
- Owners of deals, persons, organizations, activities and notes.
- Custom field values — none are used, although they may be present in the stored copy of a record if Pipedrive includes them by default.
- Products, files and your user list. The only user call is the check of the authorising user when connecting.
8. Known limitations when reading
- Deal stages show as numbers. Revial stores the Pipedrive stage ID rather than the stage name, so open deals are not classified by stage.
- Only the first pipeline's stages are read.
- Records beyond the 50,000 cap are skipped and are not picked up by later syncs.
- A deal without a currency is treated as euros.
- On a full sync, deleted records are not filtered out, and a deal with the
status
deletedis stored as open. - Participant lookups are one request per deal, and a rate-limit response fails that sync's deals step, which is then retried.
9. What Revial writes to Pipedrive
Revial never deletes anything in Pipedrive, never creates persons, organizations, deals or activities, and never changes pipelines or field definitions.
9.1 Meeting summary note — automatic
After a meeting's summary is ready, Revial creates a Pipedrive note
(POST /api/v1/notes) with content and one of deal_id, person_id or
org_id:
- Content: "Meeting Summary – meeting title", an AI-generated notice, the summary in your organisation's note template, and a link to the meeting in Revial. On an organization note, participants not found as persons are listed. Written in your CRM output language if one is set. Capped at 64 KB.
- Attached to: the matched deal; if none, the organization; if none, one note per matched person. Admins can change this order in CRM settings.
- Not pushed when no Pipedrive record matches. Written once per meeting.
- Authored by the authorising user — Revial sets no separate owner.
Automatic pushing can be switched off for a connection by Revial support.
9.2 Mapped fields — optional
Admins can map Revial summary fields (including the full transcript) and custom extraction fields to fields on persons, organizations and deals.
- Revial updates the matched record only (
PATCH /api/v2/{entity}/{id}). - A field that already has a value is left alone, unless that mapping is set to overwrite. Revial reads the record first to check.
- Values are converted to the field type; text is capped at 64 KB.
- Any field can be mapped, standard ones included — choose mappings with care.
- If a batch update fails, each field is retried once individually and failures are recorded.
- Known issue: Pipedrive's v2 API may expect custom fields in a nested structure that Revial does not yet send. If a mapped custom field is not updated, contact Revial support.
9.3 Manual push from Revial
Any team member can push a meeting note from Revial to a person, organization or deal they choose, edit it first, and optionally push mapped fields too. This works even if automatic pushing is switched off.
9.4 Not written to Pipedrive
- Transcript notes — the full transcript reaches Pipedrive only through a mapped field.
- New deals — deal creation is not available for Pipedrive.
- Activities and tasks.
Connecting Revial to Pipedrive
For your Pipedrive administrator and whoever signs off on the integration's data access — who authorises, scopes, what Revial reads and writes, and what it deliberately does not do.
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.