Connecting Pipedrive to Heymarket, keeping contacts in step, and logging every conversation on the Pipedrive timeline.
1. What the integration does
The Pipedrive integration keeps people in step between the two systems and puts your text and email conversations onto the Pipedrive timeline, so a salesperson looking at a person in Pipedrive can see the whole conversation without leaving the page.
It is made of four pieces. Three are switches you turn on separately; the fourth, the Heymarket panel, is simply there once you are connected. Timeline Activities also needs at least one contact sync switched on — see section 8.
| Piece | What it does | Direction |
|---|---|---|
| Pipedrive to Heymarket Sync | Brings Pipedrive people into Heymarket as contacts, and keeps their name, phone, email and any fields you have mapped up to date. Creates the Heymarket contact if it does not exist yet. | Inbound |
| Heymarket to Pipedrive Sync | Pushes your Heymarket contacts into Pipedrive as people, and keeps the name and mapped fields up to date. Creates the Pipedrive person if a matching one cannot be found. | Outbound |
| Timeline Activities | Logs each text or email as a completed activity on the matching Pipedrive person's timeline, dated to when the message was actually sent or received. Requires at least one contact sync to also be on. | Outbound |
| Heymarket panel inside Pipedrive | Opens Heymarket inside a Pipedrive person page and jumps straight to that person's conversation. Nothing to switch on — it is part of the Pipedrive app. | Both |
|
Nothing moves until you say so Connecting your account does not sync anything. All three switches start in the off position, on purpose, so you can set up your field mapping before the first contact is created. This matters — see section 7. |
The Pipedrive settings page on a connected account. Pipedrive to Heymarket Sync is on and has just run; the other two are still off.
2. Before you start
What you need
| Requirement | Detail |
|---|---|
| Heymarket admin access | Every part of this integration — connecting, the switches, field mapping, disconnecting — is restricted to team administrators. A regular member cannot see or change any of it. |
| The Pipedrive integration switched on for your account | Pipedrive is not available on every Heymarket account by default. Your Heymarket contact enables it for your team. If the Pipedrive tile is missing from your Integrations page, or clicking it bounces you back with an upgrade prompt, this is why — ask Heymarket support to enable it. |
| Pipedrive admin access | You will be asked to authorise Heymarket against your Pipedrive company. You need an account allowed to grant that access. |
| Pop-ups allowed | Connecting from inside Heymarket opens the Pipedrive sign-in in a pop-up window. If your browser blocks it, Heymarket shows "Please allow popups for Heymarket and try again." |
Decide these before you connect
- Which direction do you want contacts to flow? You can run one way, the other, or both. Both is normal, but it is the setting most worth thinking about — see the warning below.
- Which Heymarket custom fields should hold your Pipedrive data? Create them in Heymarket first. The mapping table can only point at custom fields that already exist.
- Which phone and email label does your team use in Pipedrive? Work, home, mobile or other. This decides which number Heymarket picks up. Default is work.
- Do you want conversations on the Pipedrive timeline? If so, note that Timeline Activities only works alongside at least one direction of contact sync — see section 8.
|
Turning on Pipedrive to Heymarket Sync will create contacts The first sync brings across every person in your Pipedrive account who has a phone number or an email address. On a large Pipedrive account that is a lot of new Heymarket contacts. This is not reversible with a switch — turning the sync back off leaves the contacts in place. Be sure that is what you want. |
|
Recommended order Connect → set your phone and email labels → add your field mappings → then turn on the sync switches. Fields you map after the first sync will not be filled in on contacts that have not changed in Pipedrive since. Section 7 explains how to fix that if you get the order wrong. |
3. Installing — three ways
All three routes end in the same place: a connected Pipedrive account on your Heymarket integration page with every sync switched off. Pick the one that matches where you are starting from.
| Route | Use it when | Where you end up |
|---|---|---|
|
Option 1 Start in Heymarket |
You already use Heymarket and want to add Pipedrive. | On the Heymarket Pipedrive settings page, ready to configure. |
|
Option 2 Start in the Pipedrive Marketplace |
You already use Heymarket but found the app in Pipedrive first. | Back in Pipedrive, with the connection made. You then open Heymarket to configure. |
|
Option 3 Marketplace, new to Heymarket |
You have Pipedrive and no Heymarket account yet. | Signed up, onboarded, connection made, back in Pipedrive. |
Option 1 — Start in Heymarket
- In Heymarket, go to Administration → Integrations.
- Find the Pipedrive tile — "Integrate with Pipedrive to sync contacts and activities." — and click it.
- On the Pipedrive page, click Setup.
- A pop-up opens on Pipedrive's sign-in and permission screen. Sign in if you are asked to, choose the Pipedrive company you want to connect, and approve the access Heymarket requests.
- The pop-up closes on its own. The Heymarket button shows "Finishing connection…" while it confirms, then the page switches to the full settings view.
The Pipedrive tile on the Integrations page. Once connected it reads Manage; before that, Setup.
The Setup card, before anything is connected.
Pipedrive's authorisation window. Check the company shown here before clicking Allow and Install.
The button reads Finishing connection… while Heymarket confirms the link.
|
Check which Pipedrive company you picked If your Pipedrive login can reach more than one company, the authorisation screen decides which one gets connected. Once connected, confirm the Pipedrive account row on the settings page shows the company you expected before you turn any sync on. Connecting the wrong company and then syncing writes your contacts into the wrong CRM. |
Option 2 — Start in the Pipedrive Marketplace, existing Heymarket customer
The Heymarket listing in the Pipedrive Marketplace. Install now starts the flow.
- Open the Heymarket listing in the Pipedrive Marketplace — https://www.pipedrive.com/en/marketplace/app/heymarket/678caf085729bb33 — and click Install now.
- Approve the access Pipedrive asks about.
- Pipedrive hands you to Heymarket, which shows "Finishing your Pipedrive setup…" while it completes the connection.
- If you are not signed in to Heymarket, you are asked to sign in first. The install resumes by itself once you are in — you do not need to start over.
- Heymarket sends you back to your Pipedrive account. The connection is made but nothing is switched on.
- Open Heymarket and go to Administration → Integrations → Pipedrive to configure it.
|
The install link expires The authorisation Pipedrive hands over is single-use and short-lived. If you take too long over signing in, or the connection fails, you will see "We couldn't finish connecting Pipedrive. Please reinstall the app from the Pipedrive Marketplace." Reinstalling from the Marketplace listing is the correct fix — refreshing the page will not work. |
Option 3 — Marketplace, new to Heymarket
- Open the Heymarket listing in the Pipedrive Marketplace, click Install now and approve the access.
- You land on Heymarket's sign-up. Create your account.
- Complete the short onboarding form — company name, size, industry, how you plan to use Heymarket, and your phone number.
- When you submit that form, Heymarket picks the Pipedrive install back up automatically and finishes the connection.
- You are returned to Pipedrive. Sign in to Heymarket and go to Administration → Integrations → Pipedrive to configure.
What happens the moment you connect
- Your Pipedrive account is linked to your Heymarket team, and the account name appears on the settings page.
- All three sync switches are off. No contact is created, changed or sent anywhere.
- No field mappings exist yet.
- The External Message activity type is not created yet — that happens the first time you switch Timeline Activities on.
4. The settings page, control by control
Everything lives on one page: Administration → Integrations → Pipedrive. It has two blocks — Settings and Contact Field Mapping — and a Disconnect Pipedrive button at the bottom.
| Control | What it does |
|---|---|
|
Pipedrive account read-only |
The Pipedrive company currently linked. Check this before switching anything on. It only appears once Heymarket has been able to read the account name. |
|
Connected on read-only |
When the connection was made. A reconnect updates it. |
|
Pipedrive to Heymarket Sync switch |
Brings Pipedrive people into Heymarket. Switching it on starts the schedule and runs one sync straight away, so you see results in minutes rather than waiting for the next slot. Once it has run at least once, the row shows Last synced …. |
|
Heymarket to Pipedrive Sync switch |
Pushes Heymarket contacts into Pipedrive. |
|
Timeline Activities switch |
Logs messages onto the Pipedrive timeline. The first time you switch it on, Heymarket creates the External Message activity type in your Pipedrive account. If Pipedrive cannot be reached at that moment the switch stays off and you are asked to try again. |
|
Phone Property dropdown |
Which Pipedrive phone label Heymarket should treat as the number for a person. Work, Home, Mobile or Other. See section 6. |
|
Email Property dropdown |
The same idea for email. Work, Home or Other. |
|
Resync now button, top right of Settings |
Re-reads your entire Pipedrive contact list from scratch instead of only what has changed. Use it after adding field mappings. It only runs Pipedrive to Heymarket — see the warning below. |
|
Contact Field Mapping table |
Pairs a Pipedrive person field with a Heymarket custom field. Section 7. |
|
Disconnect Pipedrive button, bottom of page |
Unlinks the account and switches everything off. Section 14. |
|
"Resync now" is one-directional It re-reads everything from Pipedrive. It does not re-send your Heymarket contacts to Pipedrive. There is currently no button that forces a full Heymarket-to-Pipedrive re-push; that direction only picks up contacts that have actually changed since it last ran. |
|
Resync needs inbound switched on If Pipedrive to Heymarket Sync is off, the Resync button refuses with "inbound sync is disabled; enable it before resyncing". That is deliberate — a resync with the switch off would fetch everything and then throw it away. |
How the page looks straight after connecting: the account is linked and all three switches are off.
The Phone Property dropdown. Email Property offers the same list without Mobile.
5. Fields that sync automatically
Three things always sync without any configuration: name, phone and email. You cannot map them yourself and you do not need to. Everything else is up to you (section 7).
| Field | Pipedrive to Heymarket | Heymarket to Pipedrive | What to know |
|---|---|---|---|
| Name | Pipedrive Name → Heymarket display name. | Sent on create, and on update only when the Heymarket contact actually has a name. | A Heymarket contact with no name at all is created in Pipedrive as "Heymarket Contact" — Pipedrive refuses to store a person without a name. Rename it in Pipedrive and Heymarket will not overwrite it. |
| Phone | The number carrying your chosen label (section 6), reduced to digits. | Only when creating a new person. Never on an update. | The most important asymmetry in the integration — see the red box below. |
| The address carrying your chosen label, lower-cased. | Only when creating a new person. Never on an update. | Same as phone. |
|
Editing a phone or email in Heymarket does not change it in Pipedrive Pipedrive holds many numbers and addresses per person; Heymarket holds one. Any write we make would replace the whole list and silently delete the numbers we cannot see. Rather than risk destroying data, Heymarket leaves contact details alone on every update. Pipedrive stays the system of record for phone numbers and email addresses. They are only ever sent when Heymarket creates a brand-new person in Pipedrive, where there is nothing to overwrite. |
|
Organisation is not synced A Pipedrive person's organisation is not brought into Heymarket and cannot be mapped. Organization does appear in the mapping picker, but adding it fails with "Could not create the field mapping. Please try again." — pick a different field. |
What else the sync does to contacts
- Contacts created by Pipedrive to Heymarket Sync are marked as originating from Pipedrive and are attributed to the administrator who set the integration up.
- Contacts created by Heymarket to Pipedrive Sync keep their original Heymarket origin. They simply gain a link to their Pipedrive person; where the contact came from is not rewritten.
- Either way the contact is added to Heymarket search straight away, so it appears in the Contacts list, filters and audience building.
- A Pipedrive person with neither a phone number nor an email address is skipped — Heymarket would have no way to reach or match them.
|
Field-change automations and the very first sync Heymarket automations that trigger on a custom-field change do not fire during the first full import. Without that, importing thousands of contacts at once would fire thousands of automations. Every sync after the first one fires them normally. |
6. Phone and email labels
Pipedrive lets one person hold several numbers, each tagged work, home, mobile or other. Heymarket stores one. The Phone Property and Email Property dropdowns are how you tell Heymarket which one to take.
How Heymarket picks
- The first entry whose label matches your choice.
- If none matches, the entry Pipedrive has flagged as primary.
- If there is no primary, the first entry with a value in it.
So setting it to Mobile does not mean "only sync mobiles" — it means "prefer the mobile; fall back to the primary if there isn't one". Nobody is skipped for lacking the label you chose.
| Setting | Value |
|---|---|
| Default when unset | Work. Pipedrive tags an unlabelled number as work, so this suits most accounts. |
| Phone options | Work · Home · Mobile · Other |
| Email options | Work · Home · Other |
Where the setting applies
| Situation | Does the label setting apply? |
|---|---|
| Reading a person during Pipedrive to Heymarket Sync | Yes — it chooses which number becomes the Heymarket contact's number. |
| Matching an existing Heymarket contact | Yes — the chosen number is what Heymarket looks up. |
| The Heymarket panel inside Pipedrive | Yes — it decides which number the panel opens the conversation for. |
| Creating a new person in Pipedrive | Yes — the number and address are written under your chosen label. |
| Updating an existing person in Pipedrive | Not applicable — contact details are never sent on an update. |
|
Changing the setting later is safe and takes effect on the next sync It does not rewrite anything on its own. Contacts pick up the newly preferred number the next time their Pipedrive record changes — or straight away for everyone if you run Resync now. |
7. Mapping your own fields
The Contact Field Mapping table pairs a field on the Pipedrive person with a Heymarket custom field. Once paired, that value moves in both directions automatically — as long as the sync switch for that direction is on.
Adding a mapping
- Create the Heymarket custom field first, if it does not exist. The picker only lists fields that already exist on your team.
- Scroll to Contact Field Mapping.
- In the left dropdown, Select a Pipedrive field. The list is read live from your Pipedrive account, so your own custom fields appear here by their real names. You can type to filter.
- In the right dropdown, Select a Heymarket custom field.
- Click Add. The pair appears in the table straight away.
Contact Field Mapping with three saved pairs. Each row has its own Remove; the empty row at the bottom is where you add the next one.
The Pipedrive field picker. Type to filter — here hm narrows the list. The list comes from your own Pipedrive account, so your custom fields appear under their real names.
The rules
- One Pipedrive field per mapping. A field that is already mapped disappears from the picker, so you cannot pick it twice. The same is true of Heymarket fields.
- Name, email and phone are not in the list. They always sync (section 5).
- People only. Pipedrive deals, organisations, leads and activities are not synced and cannot be mapped. Organization is offered by the picker but will not save — see section 5.
- Removing a mapping stops future syncing. Values already written to either side stay where they are; nothing is cleaned up.
|
Pipedrive also lists a separate “Currency of …” field For every monetary field, Pipedrive exposes a companion field holding its currency, and that companion appears in the picker as a field of its own. You can map it if you want the currency code stored in Heymarket, but it is treated as an ordinary value — mapping it does not make Heymarket write the amount in that currency. |
|
Monetary fields lose their currency Heymarket stores the number, not the currency. When it writes the value back, Pipedrive applies your account's default currency. If a particular person's amount was set in a different currency, it will be reset to the account default the next time Heymarket updates that person. If you deal in multiple currencies, do not map monetary fields. |
|
Multi-select values are stored as one list Heymarket stores a multi-select field as its chosen options joined by a comma and a space, for example Red, Blue. If one of your option names itself contains a comma and a space, Heymarket cannot reliably split it apart again, and the wrong options may be set when the value is written back to Pipedrive. Rare, but worth knowing if your option names are long phrases. |
Emptying a value
| In Pipedrive the mapped field is… | In Heymarket |
|---|---|
| Given a value | Set to that value. |
| Cleared (emptied or set to none) | Cleared as well. |
| Not present in the record at all | Left exactly as it is. Heymarket does not treat absence as deletion. |
Fields you have not mapped are never touched by the integration, in either direction.
|
Field-change automations and a full resync A resync re-reads every person in your Pipedrive account, so any mapped value that has changed will be written to the matching Heymarket contact. If you run automations that trigger on a custom-field change, run the resync at a quiet time and be ready for a burst of activity. |
|
Add your mappings before the first sync, or resync afterwards A mapping only takes effect on contacts that sync after you add it, and the Pipedrive-to-Heymarket sync only looks at people who have changed. Add a mapping after the first import and the new field stays empty on every contact until something changes about them in Pipedrive. Fix it with Resync now, which re-reads every person and fills the field in. |
8. Timeline activities
With Timeline Activities on, every text and email between your team and a matched contact appears on that person's Pipedrive timeline as a completed activity, dated to when the message actually happened.
|
Timeline Activities needs at least one contact sync switched on as well An activity can only be attached to a Pipedrive person that Heymarket has already linked to the contact, and that link is created solely by Pipedrive to Heymarket Sync or Heymarket to Pipedrive Sync. Turn on Timeline Activities on its own, with both contact syncs off, and no activity will ever appear — the messages are held for seven days waiting for a link that never arrives, then dropped. Switch on at least one direction of contact sync, and only contacts that direction has linked will receive activities. |
What it looks like in Pipedrive
| Activity type | External Message — a custom type Heymarket creates in your account, with a speech-bubble icon and a yellow colour. |
| Subject | Heymarket message on every activity. |
| Status | Marked done, so it appears as something that happened rather than a task to do. |
| Date and time | The moment the message was sent or received, in UTC — not the moment it was logged. Older conversations land in the right place on the timeline. |
| Attached to | The Pipedrive person, as the primary participant. |
| Body | The message text, a Sent or Received badge, and the timestamp. Images appear inline; other attachments appear as a "View attachment" link. |
| Emails | Also carry a Subject / From / To / Cc header above the body, and the email's own formatting is preserved. |
An outbound message logged on the Pipedrive timeline: the Heymarket message subject, a green tick because it is marked done, the Sent badge, and the message's own timestamp. Pipedrive shows its header time in your account's time zone — here 4:06 PM for a message sent at 10:36 UTC.
What is not logged
| Not logged | Why |
|---|---|
| Messages that failed to send | Recording a message that never arrived would misrepresent the conversation. |
| Group texts | One group message would otherwise fan out across every recipient's timeline. |
| Internal notes and comments | Only messages to and from the contact are logged. |
|
Messages that arrive before the person is linked are held, not lost If a message comes in for someone Heymarket has not yet matched to a Pipedrive person, it is held for up to 7 days. As soon as the link is made — by either sync direction — the held messages are logged onto the timeline in the right order, with their original dates. After 7 days they are dropped. |
|
The gap worth knowing about: a brand-new number that texts you first When somebody Heymarket has never seen texts your number for the first time, Heymarket does not create a contact for them. With no contact, there is nothing to link to a Pipedrive person, and the holding mechanism above never gets a chance to release. Those first messages do not reach the Pipedrive timeline. Once the person exists as a contact — you add them, or they arrive through either sync — everything from that point forward is logged normally. Heymarket is tracking this as a known gap. |
One email, several recipients
An email sent to several people creates one activity per recipient, each on that person's own timeline, provided they are matched. The sender is excluded, so replying to all does not log an activity against your own team's contact record.
|
Duplicates are prevented Heymarket remembers, for three days, which messages it has already logged for each person, so a retry after a hiccup does not produce a second copy of the same activity. |
9. The Heymarket panel inside Pipedrive
Installing the Heymarket app adds a Heymarket panel to the Pipedrive person page. Open a person and the panel loads their Heymarket conversation, so your team can read and reply without switching tabs.
How it works
- Open any person in Pipedrive.
- Open the Heymarket panel on that page.
- Heymarket looks up that person's phone number and email address — using the labels you chose under Phone Property and Email Property — and opens the matching conversation.
What you need for it to work
| Requirement | If it is missing |
|---|---|
| A connected Pipedrive account in Heymarket | The panel cannot look anything up. |
| You are signed in to Heymarket in the same browser | The panel will ask you to sign in. |
| The Pipedrive person has a phone number or email | Nothing to open a conversation for; the panel shows an empty state. |
|
If you belong to more than one Heymarket team with Pipedrive connected Heymarket will not guess which team's data to show — surfacing the wrong team's conversation would be worse than showing nothing. The panel reports that it cannot decide. Teams that hit this should keep one Pipedrive connection per person where possible. |
|
Nothing to switch on The panel is not controlled by the three sync switches. It works as soon as the account is connected, and it does not create or change any data — it only reads the person to find the right conversation. |
The Heymarket panel on a Pipedrive person page. It has opened this person's conversation and you can reply straight from it. Note the phone above the panel is labelled (Work) — that is the label Heymarket matched on, set by Phone Property.
10. How Heymarket decides two records are the same person
Both directions try hard to match an existing record before creating a new one. Understanding the order helps explain most "why did I get a duplicate" questions.
Pipedrive to Heymarket
For each Pipedrive person, in this order, stopping at the first match:
- Phone. The chosen number, compared as digits only, so (650) 555-0142, 6505550142 and +16505550142 all match each other.
- Email. The chosen address, compared without regard to capitals.
- No match — a new Heymarket contact is created.
When a match is found on one channel and the Pipedrive person has the other as well, Heymarket fills in the missing one, so the contact is reachable both ways afterwards.
Heymarket to Pipedrive
- If Heymarket already knows which Pipedrive person this contact is, it updates that person.
- Otherwise it searches Pipedrive by phone, then by email, and verifies that the person it found genuinely carries that number or address before using it.
- No match — a new Pipedrive person is created and linked.
|
Two Pipedrive people sharing one phone number Family members or colleagues on a shared line can both match the same Heymarket contact. Heymarket cannot tell whose name and email its single record holds, so it deliberately stops writing name, phone and email to those people — writing them would overwrite a real person with somebody else's details. Mapped custom fields still sync, because those describe the record rather than claiming who it is. |
11. How often everything syncs
Each part of the integration runs on its own cadence. None of it needs you to keep a browser open.
| What | How often | Detail |
|---|---|---|
| Pipedrive to Heymarket | Every 30 minutes | Only people changed since the last run. Runs once immediately when you first switch it on. |
| Heymarket to Pipedrive | Every 30 minutes | Only contacts changed since the last run. Runs once immediately when you first switch it on. |
| Timeline activities | Continuous | Not on a schedule — messages are picked up as they happen. Usually on the timeline within a minute. |
| Resync now | On demand | Re-reads the whole Pipedrive contact list. Minutes on a small account, longer on a large one. |
| Held messages | On link | Released the moment the contact is matched to a Pipedrive person; discarded after 7 days. |
| Retry after a hiccup | Every 5 minutes | A message that could not be logged is retried a handful of times before being parked. |
Pushing to Pipedrive is slower than reading from it because each contact is created or updated individually, within the limits Pipedrive allows. It runs in the background in stages and picks up where it left off, so a very large first push may span several scheduled runs. You do not need to keep the page open.
|
If Pipedrive's daily limit is reached Pipedrive allows a fixed volume of API activity per day. If a large sync exhausts it, Heymarket pauses that connection — up to about an hour — and then carries on from exactly where it stopped. Nothing is lost or skipped. You may see a sync appear to stall on a very large first import — this is usually why. |
12. Limitations and things to know
An honest list. Most of these are how the integration works today rather than settings you can change; the one acknowledged gap is called out as such.
Data direction
| Limitation | What it means for you |
|---|---|
| Phone and email only go to Pipedrive when a person is created | Correcting a number in Heymarket will not correct it in Pipedrive. Make contact-detail corrections in Pipedrive. |
| Organisation is not synced | Company names live only in Pipedrive. |
| People only | Deals, organisations, leads, notes and Pipedrive activities are not synced. |
| "Resync now" is Pipedrive-to-Heymarket only | There is no equivalent full re-push in the other direction. |
| Monetary fields lose their currency | Per-person currencies get reset to the account default. Avoid mapping them in a multi-currency account. |
Deleting
| Limitation | What it means for you |
|---|---|
| Deleting a person in Pipedrive does not delete the Heymarket contact | The contact and its message history stay in Heymarket, still linked. Delete it in Heymarket separately if you want it gone. |
| Deleting a contact in Heymarket does not delete the Pipedrive person | Deliberate — deleting records in a CRM on Heymarket's initiative would be dangerous. |
| Removing a field mapping does not remove the data | Values already synced remain on both sides. It only stops further syncing. |
Matching
| Limitation | What it means for you |
|---|---|
| A person with no phone and no email is skipped | They will not appear in Heymarket. |
| Two people sharing a number | Their name, phone and email stop being written from Heymarket. Mapped custom fields still sync. |
Timeline activities
| Limitation | What it means for you |
|---|---|
| Timeline Activities does nothing on its own | It needs at least one contact sync switched on, because that is what links a contact to a Pipedrive person. See section 8. |
| A brand-new number that texts you first is not logged | See section 8. Known gap. |
| Group texts and failed sends are not logged | By design. |
| Held messages expire after 7 days | Link the contact within a week and nothing is lost — provided the contact exists in Heymarket at all (see the gap above). |
| Activity timestamps are in UTC | Pipedrive displays them in your account's own time zone setting. |
| Every activity has the same subject | "Heymarket message". The detail is in the body. |
Setup
| Limitation | What it means for you |
|---|---|
| One Pipedrive account per Heymarket team | Connecting a second replaces the first. |
| Administrators only | Regular members cannot see the settings page. |
| Mappings added later need a resync | Section 7. |
| Heymarket to Pipedrive Sync covers every contact | There is no way to restrict it to a list, tag or segment. Every contact in the team is eventually pushed. |
| Automations do not fire on the first import | Section 5. |
13. Troubleshooting
| Symptom | Cause and fix |
|---|---|
| The Pipedrive tile is missing from Integrations | Pipedrive is not enabled for your Heymarket account, or you are not an administrator. Ask Heymarket support to enable it. |
| Clicking Pipedrive bounces me back with an upgrade prompt | Pipedrive is not switched on for your Heymarket account. Contact Heymarket support. |
| "Please allow popups for Heymarket and try again." | Your browser blocked the sign-in window. Allow pop-ups for Heymarket and click Setup again. |
| "We could not confirm the connection. Please try again in a moment." | The pop-up closed but Heymarket had not finished registering the connection. Reload the page — the connection has often gone through. If not, click Setup again. |
| "We couldn't finish connecting Pipedrive. Please reinstall the app from the Pipedrive Marketplace." | The Marketplace authorisation expired or was already used. Reinstall from the Marketplace — refreshing will not help. |
| Red banner: "Pipedrive integration error" | Heymarket's access was revoked, expired, or the Pipedrive user who authorised it lost access. Click Reconnect in the banner. Everything is paused until you do, and the switches are locked while the connection is in this state. |
| Nothing has synced at all | Check the switches are actually on, and check the Last synced line under each. Remember the schedule is every 30 minutes. |
| Contacts came across but my mapped fields are empty | The mapping was added after those contacts last changed in Pipedrive. Click Resync now. |
| A phone number I fixed in Heymarket is still wrong in Pipedrive | Expected. Contact details only go to Pipedrive when a person is created. Fix it in Pipedrive. |
| A contact is named "Heymarket Contact" in Pipedrive | The Heymarket contact has no name, and Pipedrive requires one. Give the contact a name in Heymarket, or rename the person in Pipedrive — Heymarket will not overwrite a name you set there. |
| Messages are not appearing on the timeline | Work through, in order: is Timeline Activities on; is at least one contact sync also on (activities cannot work without one); is the contact actually linked to a Pipedrive person (check the person exists and shares the number or address); was the message a group text or a failed send; and is this the first-ever message from an unknown number (section 8). |
| "Could not set up the Pipedrive activity type." | Heymarket could not reach Pipedrive to create the External Message type. The switch stays off. Wait a moment and try again. |
| "Could not load Pipedrive fields." | Heymarket could not read your field list from Pipedrive. Usually momentary — reload. If the connection banner is red, reconnect first. |
| A big first sync seems to have stalled | Most likely Pipedrive's daily API limit. Heymarket pauses, then resumes from where it stopped — usually within the hour. Check again later before raising it. |
| Duplicate people appeared in Pipedrive | Usually the two records had no shared number or address in a comparable form. Merge them in Pipedrive; Heymarket keeps using the older link. |
14. Disconnecting, reconnecting, switching accounts
Disconnecting
Click Disconnect Pipedrive at the bottom of the settings page and confirm.
| What happens | What does not |
|---|---|
| All three switches are turned off, Heymarket's access to Pipedrive is revoked, and the Pipedrive page returns to its not-connected state. | No contact is deleted on either side. No Pipedrive person is deleted. Your field mappings and the links between contacts and people are kept. |
Reconnecting to the same Pipedrive account
- Your field mappings and contact links are still there and are re-attached automatically.
- The sync switches stay off. A sync you deliberately turned off is not silently turned back on. Switch them on again when you are ready.
Connecting a different Pipedrive account
|
Switching accounts clears your configuration Everything Heymarket stored referred to records in the old account — person identities and field identifiers mean nothing in a new one. So when Heymarket detects a different Pipedrive company, it discards all field mappings and all links between Heymarket contacts and Pipedrive people, and starts from scratch. You will need to set your mappings up again. Contacts and message history in Heymarket are untouched. |
|
The reason to check the account name before syncing If you connect the wrong Pipedrive company and switch a sync on, Heymarket will start writing your contacts into it. Confirm the Pipedrive account row first, every time you connect or reconnect. |
15. Frequently asked questions
Can I sync only some contacts?
No. Both directions cover every contact and every person in the account. There is no filter, segment or list restriction today.
Can I run Pipedrive alongside another CRM integration?
Yes, Heymarket does not stop you. Bear in mind that two CRMs both writing to the same contacts can produce surprising results, so think it through before turning both directions on.
Will this create duplicate contacts in Heymarket?
It is designed not to — see section 10. The usual cause of a duplicate is two records with no comparable number or address between them.
What happens to messages sent before I connected?
They are not backfilled onto the Pipedrive timeline. Activity logging starts when you switch it on. The only exception is a message that arrived after you switched Timeline Activities on but before the contact was linked to a Pipedrive person — those are held for 7 days.
Do I need to keep the browser open during a big sync?
No. Everything runs on Heymarket's servers.
Does this cost Pipedrive API usage?
Yes. Pipedrive meters API activity daily, and a large first sync uses a meaningful share of it. Heymarket backs off and resumes rather than exhausting your quota outright.
Can I choose which Heymarket inbox contacts belong to?
No. Synced contacts belong to the team, the same as any other contact.
Can I pause syncing temporarily?
Yes — switch the relevant sync off. Turning it back on resumes from where it left off; nothing queues up in between.
Does turning off a sync remove what it already synced?
No. Nothing is removed by turning a switch off.
Who appears as the creator of contacts brought in from Pipedrive?
The administrator who set the integration up.
Can I map a Pipedrive field to a standard Heymarket field like first name?
No. Mappings target Heymarket custom fields. Name, phone and email are handled automatically.