Pipedrive
Pipedrive is not one integration among several — it is where Lokom gets everything it calculates from.
Setup is covered in Connect Pipedrive. This page is what to know once it is running.
What Lokom reads
- Deals — value, close date, stage, owner, and the custom fields you map.
- Users — who becomes a participant.
- Pipelines and stages — to determine what counts as closed.
- Custom fields — anything your rules need, once mapped.
The exact access Lokom is granted
The connection card lists the scopes Pipedrive granted. Today they are:
| Scope | What it allows |
|---|---|
base | Basic account access |
deals:read | Read deals |
deal-fields:full | Read and write deal-field definitions |
leads:read | Read leads |
products:read | Read products |
search:read | Search |
users:read | Read users |
webhooks:full | Create and manage webhooks |
You can see this list yourself at Organization → Data Sources → Connection, under "Access granted by Pipedrive" — check it there rather than trusting this table, since scopes can change between releases.
What Lokom writes
Not your deal data. Lokom does not create, edit, move or close deals, and it does not change deal values.
Two of the scopes above are nonetheless write-capable, and it is worth knowing why:
webhooks:full— Lokom registers webhooks so it learns about deal changes as they happen instead of polling.deal-fields:full— full access to deal-field definitions.
The one thing it puts in front of your reps is the commission panel on the deal. → What reps see
Visibility follows the connecting account
Lokom sees what the account that authorised it can see. Connect with a rep's account and Lokom sees only that rep's deals — every other rep computes to zero, with no error anywhere, because from Lokom's side those deals do not exist.
Connect with an admin account that sees everything.
Field mapping
Organization → Data Sources → Fields is where Pipedrive fields become things rules can read.
The mapping that matters most is which field is the amount you pay on. Deal value is the default and frequently not what you mean — annual value on a multi-year contract, value net of discount, the MRR component alone. A rule can only read a mapped field, so add it in Pipedrive first if it is missing, then re-sync.
Sync
Lokom syncs on an ongoing basis. New and updated deals arrive, and open periods reflect them as they do.
Late arrivals — a deal that closed inside a period but synced after you computed it — are tracked rather than absorbed silently, so you can see that a period changed since you last looked. Re-compute to include them. → Run a period
Reconnecting
Access tokens expire and Lokom refreshes them automatically. When the refresh cannot succeed — the app was revoked, or the connecting user left — you will be prompted at Organization → Data Sources → Reconnect.
Reconnect promptly. While the connection is down there is no error at the rule level; deals simply stop arriving, and periods quietly go stale.
If the person who authorised Lokom leaves and their Pipedrive account is deactivated, the connection dies with it. Reconnect with an account that will outlast any individual.