Pipedrive
What Paperbeam reads from Pipedrive, the read-only access it asks for and why, filters, and the beats it feeds.
CRM
Read-only API key
Won and lost deals, new deals and stage movement from Pipedrive.
What we read
- Deals: stage changes, wins and losses, amounts and owners
Only the reporting window of each edition is read. Paperbeam stores derived facts and short excerpts, not copies of your Pipedrive data, and keeps raw evidence only for your retention period.
Access we ask for, and why
| Scope | Why |
|---|---|
deals:read | Read deals, values and stages |
users:read | Credit deal owners |
All access is read-only. You can revoke it from Pipedrive at any time, or disconnect the source in Paperbeam.
Connect Pipedrive
- Go to Sources and choose Pipedrive.
- Create a api token. In Pipedrive: your avatar → Personal preferences → API, then copy your personal API token. Open Pipedrive settings.
- Fill in Personal API token, then click Test connection. Paperbeam makes one read-only call and shows the account it reached, or exactly what went wrong.
- Click Connect. The credential is encrypted before it is stored and never shown again. Use Sync now on the source’s page to see what it collects from the last 24 hours, and set filters there.
You need the admin or owner role in Paperbeam, and enough permission in Pipedrive to grant read access to the data listed above.
Filters
Set on the source’s page at Sources›Pipedrive. Filtered-out data is never collected.
| Filter | Effect |
|---|---|
| Pipelines | Only deals in these pipelines (ids or names). Leave empty for every pipeline. |
To keep specific people, channels or topics out of the paper across all sources, use exclusion rules and the never-mention list in House style.
Beats
Pipedrive is a source for:
Stories land in whichever of your sections fits them best.