Pipedrive setup
Connect SendBeam to Pipedrive: what you need, the steps, and the code.
Native
Sales keeps its people in Pipedrive; marketing keeps its list somewhere else; the two drift apart within a month. Connecting Pipedrive to SendBeam makes the CRM the source of who exists, and puts email engagement back on the person record where whoever picks up the phone can see it.
Before you start
- A Pipedrive account
- A SendBeam account with a verified sending domain
- Permission in Pipedrive to add custom fields, if you want engagement written back
Set it up
- Connect Pipedrive. In SendBeam, go to Settings → Connections and choose Connect Pipedrive. You are sent to Pipedrive to approve access and returned here. The connection belongs to the workspace you are in, so if you run more than one brand, connect it to the one it belongs to.
- Import your people. Contacts → Import → Import from Pipedrive. They arrive with their primary email address, name and the date they were added.
- Leave it running. After the first import SendBeam keeps checking Pipedrive on its own. People added in Pipedrive turn up in SendBeam without anyone exporting anything.
What comes across
A person’s primary email address is the subscriber. Pipedrive lets someone hold several addresses, and importing them all would invent contacts you never had, so the rest are left alone.
Alongside the name, these arrive as fields you can segment on:
| Field | From |
|---|---|
organisation |
The person’s organisation |
owner |
The Pipedrive user who owns them |
phone |
Their primary phone number |
open_deals |
How many open deals they have |
pipedrive_id |
Their Pipedrive id, so the two records stay tied together |
That last one is what lets a later change find the same person again rather than creating a second one.
Sending engagement back
Two-way sync is off until you switch it on, and while it is off SendBeam only reads from Pipedrive and writes nothing at all.
Switch it on and SendBeam adds four fields to the Person record and keeps them current:
- SendBeam: last email opened
- SendBeam: last email clicked
- SendBeam: email status
- SendBeam: last campaign
So the person about to make a call can see whether that lead opened last week’s campaign, without leaving Pipedrive.
Things to know
- SendBeam asks to read and update people, and to manage the custom fields on them. It never asks for administrator access to your Pipedrive account.
- Pipedrive’s consent screen is all or nothing — there is no way to approve part of what an app asks for.
- Creating the four fields needs permission to add custom fields. If your Pipedrive user cannot, the import still works; only the write-back is held up.
- Disconnecting in Settings → Connections stops SendBeam using your Pipedrive account. Contacts already imported stay in SendBeam, and nothing is deleted from Pipedrive.
- Only email people who agreed to hear from you. Someone who is in a CRM because they bought something has not necessarily asked for a newsletter.