Pipedrive

A Pipedrive connection runs in both directions, the same three ways a HubSpot one does: organizations pushed out, your account mirrored back in, and what Prospex knows written onto the records you already have. Like Attio, it lets you say where each fact lands.

Turning it on

1. Go to prospex.ch/app/accounts/ and connect Pipedrive. Its scopes are fixed on the app, and the person who connects is the one activities get assigned to.
2. The first sweep brings your organizations in.
3. Switch on enrichment if you want Prospex writing onto them, and map any fact you would rather see in a column of your own.

One CRM per account. Connecting HubSpot or Attio while Pipedrive is live is refused.

Matching runs on the organization's Website field. Some plans do not include it; if yours does not, the account page offers to create one, and everything below works the same way once it exists.

Out, when you press the button

The arrow pushes one company across as three things: the organization, matched on its registrable domain and created if your account has none; a note, which opens with the headline in bold and carries the link back into Prospex; and an activity, due in three days and assigned to you. A high-significance event marks the activity high priority.

Pushing twice writes nothing twice. A bulk push sends the first few inline and queues the rest, and a five-minute drain is both the tail and the retry path.

In, every six hours

Prospex reads your organizations and matches them against the register. That match drives the In CRM column and lets a list exclude accounts you already own.

Pipedrive stamps every organization with the time it last changed, so a push that needs to know what moved since the last sweep asks only for that. A company deleted in Pipedrive stops labelling your lists within six hours. A domain that could be two Swiss companies is left unresolved and labels nothing, about one record in fifteen.

Out again, continuously, if you ask

With enrichment on, every matched organization gets its Prospex fields filled in, and each event Prospex sees arrives as a note on the record. Three of those facts are fields as well, so a view can filter on the kind of event, its headline and its date.

A field is read seconds before it is written, so a value somebody typed is never the thing that changes.

Your API budget

Pipedrive gives each account a daily allowance of API tokens, shared across every integration you run. Prospex holds itself to a fraction of the smallest plan's day, so a large first pass spreads over several days rather than spending an allowance your other tools also need. Nothing is lost while it waits.

Writing into your own columns

Somebody who has kept a Branche column for years does not want a Prospex sector next to it. So each fact can name one of your own fields as its destination, and a mapped fact stops being written to ours: mapping means "use my column instead of yours".

Each mapping also says how much of the field it owns. Fill writes only where the record is holding the field blank. Sync rewrites it on every pass. A description somebody wrote is theirs, and a "last signal" column is only useful current.

Destinations are the text, number and date fields you created. Pipedrive's own properties are left alone, and a dropdown cannot be a destination: its values are ids your account minted, so filling one would mean inventing entries in your vocabulary.

What it will not do

• Overwrite a value somebody in your account filled in.
• Write to an organization whose website matches more than one Swiss company, or to two organizations that share one website.
• Touch deals, people or your pipeline.
• Receive Outreach openers. That path exists for HubSpot only today.
• Send email, to anyone, ever.

Disconnecting from the account page uninstalls the app and revokes the token. The fields and notes it created stay on your records, and you can delete them in Pipedrive.