Manage your fields
Organization → Data Sources → Fields is the list of Pipedrive fields your rules are allowed to read. A rule can only point at a field that appears here.
Most of it fills itself in. This page is for the times it does not — a field Lokom did not bring in, a field it gave the wrong job, or one you want gone.
Goal
Know what is on the list, why, and how to change it.
Prerequisites: a connected Pipedrive. → Connect Pipedrive
The three jobs a field can have
A rule needs three different things from your deal data, and a field can be eligible for any of them. That eligibility is what the badges on this page show.
| Badge | The rule step it feeds | In plain terms |
|---|---|---|
| Period event | Trigger | The date that decides which period a deal belongs to |
| Recipient | Recipient | Who gets paid |
| Source | Source | The amount a rate is applied to |
A field can carry more than one badge, or none. A field with no badge is still on the list and still readable — it just is not offered as a trigger, a payee or an amount.
What lands automatically
Lokom decides eligibility from the field's type in Pipedrive, not its name:
| Pipedrive type | Badge it earns |
|---|---|
| Date | Period event |
| User | Recipient |
| Money, or a decimal number | Source |
| Text, checkbox, dropdown, whole number, anything else | none |
Two lists get built from that:
- Standard fields — the built-in Pipedrive fields (deal value, close date, owner…). The section is tagged Always available. You cannot add or remove these.
- Custom fields — your own. Any custom field whose type earns a badge is pulled in for you, at connection and again on every sync. So a custom "Contract signed" date or a custom "ARR" amount is already there.
Custom fields that earn nothing are left out on purpose. A text note cannot be a trigger, a payee or an amount, so importing it would only make the list longer. Add those yourself if you want them.
A Pipedrive whole number field never becomes a Source on its own. Almost every hidden Pipedrive id — pipeline, stage, owner, person — is stored as a whole number, and paying a percentage of an id number is nonsense. If you have a genuine count you want to pay on, like seats sold, turn Source on for it yourself. See Change what a field is used for.
Add a field
For anything not brought in automatically.
- In the Custom fields section, click + Add field.
- The Add a Pipedrive field dialog opens. Search by the field name as it appears in Pipedrive.
- Pick it —
↑↓to navigate,↵to add — and confirm with Add field.
You get a toast: "'<name>' added." / "It's now available in the rule builder."
Two things the dialog will tell you:
- "Already-added fields don't appear here." — if you cannot find something, it is probably already on the list. Close the dialog and use Search fields… instead.
- "All caught up" — everything Pipedrive has is already added.
If a field does not exist in Pipedrive at all, create it there first. Lokom picks it up on the next sync.
Change what a field is used for
Lokom guesses from the type, and a guess can be wrong — a date field that is not the one you pay on, a money field that is a cost rather than revenue.
- Click the badge on the field's row.
- Choose Mark as period event / Don't use as period event (and the recipient and source equivalents).
It saves immediately — there is no Save button — and you get "Updated."
Your choice sticks. Before you touch it, the popover reads "Auto-set from field type. You can override." Afterwards it reads "You set this manually. It won't change on refresh." Later syncs leave it alone, even if someone changes the field's type in Pipedrive.
The badge itself tells you which state it is in: a manually-set one is marked manual, and a job you switched off shows as Period event off / Recipient off / Source off.
Their badges show a lock and the tooltip reads "Standard field — eligibility is fixed." Clicking does nothing. This is deliberate — the built-in fields are what the engine's own defaults rely on.
There is no "reset to automatic" button. To go back, just set it to the value Lokom would have picked; it stays marked manual, which changes nothing about how it behaves.
Remove a field
Only custom fields can be removed.
- Click Remove on the row.
- Confirm in the Remove '<name>'? dialog.
Read the dialog before confirming. If the field is in use it says so — "'<name>' is used in N rules. Removing it will affect those rules. Remove anyway?" — and warns "Rules using this field will stop running until they're edited." It lists which rules. That is not a soft warning: those rules stop producing commission until you point them somewhere else.
If nothing uses it, you get the mild version: "It will no longer be available in the rule builder."
A removal sticks. Lokom will not quietly re-import a field you removed, on any future sync. If you want it back, add it again with + Add field.
When it is still syncing
Right after connecting, the page may show "Syncing your Pipedrive fields" / "This usually takes under a minute.", and rows show Syncing… instead of Available. Removal is disabled while that runs — the tooltip says "Available after sync completes".
If it hangs, you will see "Sync is taking longer than expected" with a Refresh button. → Pipedrive isn't syncing
When a field says Unavailable
Unavailable means Lokom asked Pipedrive for that field twice in a row and it was not there — usually because someone deleted or renamed it in Pipedrive.
Rules pointing at it will not find a value. Either restore the field in Pipedrive, or edit the rules to use a different one. → A rep sees no commission
New fields you create later
Create a field in Pipedrive after connecting and Lokom picks it up on its next sync, within the hour, if its type earns a badge. If it does not earn one, add it manually whenever you need it — there is nothing to wait for.