Pipedrive
Connect Pipedrive once and your allme customers keep their own contact details current on your Pipedrive persons. No admin procedure, no field wizard, no code — authorize the app and the fields map themselves.
Before you start
- A Pipedrive account you can authorize apps for.
That is the whole prerequisite list. The allus portal creates and holds the account credential this step needs; Pipedrive's own API creates every custom field this integration needs, so nothing is prepared by hand first.
Setting it up
- Open the allus portal — Configuration → Integrations.
- Step 1 — connect allus. Click Connect next to Pipedrive. This creates the service your customers connect to (alerts go to your allus account's own email), its data client and its webhook — nothing to paste — and hands you to this integration's own setup page.
- Step 2 — connect Pipedrive. You are sent to Pipedrive to authorize the app, and back to your status page when you approve. That is the last step: syncing starts on its own.
Where each field lands
A Pipedrive person has one Name and no address property, so two of the standard fields land on native properties and the rest become clearly-labelled custom fields.
| What your customer shares | Where it appears in Pipedrive |
|---|---|
| The person's Email, as the primary entry | |
| Phone | The person's Phone, as the primary entry |
| First name, last name | Custom fields First name (allme) and Last name (allme); the person's Name is composed from the two |
| Address | A custom address field |
| Anything else your service asks for | A custom field named after your own request field, suffixed (allme) |
Every field this integration creates carries the (allme) suffix, so it can never be confused with — or start writing into — a field you made yourself. One further custom field, allme ID, holds the customer's share code and is how the integration finds the same person again.
How an existing person is matched
When someone connects for the first time, the integration looks for them in this order: the allme ID field, then an exact email match, then an exact phone match. If a step finds more than one person, it moves on rather than guessing — and if nothing matches uniquely, a new person is created.
What happens after that
- Edits arrive within seconds. When a connected customer changes a shared field, the Pipedrive person updates.
- Withdrawing a field clears it and leaves a note on the person saying which field was withdrawn. Withdrawing a name recomposes the person's Name from whatever remains; if nothing does, the Name becomes the customer's allme ID, since Pipedrive requires every person to carry one.
- Ending a connection leaves the person intact and adds a note. Nothing is deleted or blanked.
- Sync is one-way. Editing the person in Pipedrive never changes your customer's allme profile; the next update from them simply overwrites it again.
Documents and signed flows
When a connected customer shares, updates, removes, or signs a document, or completes a contract flow with your company, a note appears on their Pipedrive person naming the document (or the flow) and what happened to it. No document bytes ever reach Pipedrive — only the fact that something changed.
Limits worth knowing
- Notes can duplicate after an interruption. Pipedrive notes carry no external key, so if the integration is interrupted between writing a note and recording that it did, that note can appear twice. Contact fields are unaffected — only notes. Documents and contract flows share this limitation, since they land as notes too.
- Your Pipedrive API allowance is respected. The integration paces itself and backs off when Pipedrive asks it to; a busy day of edits is spread out rather than spent at once.
- Reconnect after 60 days idle. Pipedrive expires an unused authorization after 60 days. If that happens your status page shows it, and reconnecting is one click.
If something looks wrong
Your status page carries a sync-health card naming the affected customer and what to do — usually reconnect. It also shows the field mapping, how many changes are waiting, and the switch between having changes pushed to the app or fetched on a schedule.
Next
CRM integrations overview · How the connection model works · Portal guides