How do I send Evaboot leads to Pipedrive?
Connect Pipedrive from the Integrations page, then save the integration settings. Evaboot finds existing people and organizations before creating any, and never changes owners.
Before you start
Section titled “Before you start”- A Pipedrive account. You sign in to Pipedrive and approve Evaboot’s access on Pipedrive’s own page. No API key is needed.
- Optional: a person label in Pipedrive if you want every pushed person tagged with it.
Connect Pipedrive
Section titled “Connect Pipedrive”- Open Integrations and click New integration. If you have no integration yet, the tool cards show on the page directly.

- Click the Pipedrive card, then Connect Pipedrive.

- Approve the access on the Pipedrive page. You come back to the Pipedrive settings page, which shows the account you connected.
Choose the settings
Section titled “Choose the settings”- Name the integration.
- Optional: Label pushed people. Pick one of your Pipedrive person labels, or leave None.
- Pick what to send under Send data from: Sales Navigator exports, URL enrichment, Email finder or Email verifier.
- Set the filters.
- Email filter: All emails, Safe emails only, or Found emails only.
- Qualification filter: All prospects, or Qualified only.
- Pick the trigger.
- Automatic: send when a job completes: each finished, unlocked export is sent. Under Send leads from, choose all exports, all recurring exports, specific recurring exports, or specific folders.
- Manual: only send when you trigger it: nothing is sent until you push an export yourself.
- Optional: Overwrite existing values with Evaboot data. Off, Evaboot only fills empty fields.
- Click Save. The integration appears on the Integrations page.
What Evaboot sends to Pipedrive
Section titled “What Evaboot sends to Pipedrive”- People with name, email, job title and LinkedIn URL, linked to their organization.
- Organizations with name and domain. Account exports create organizations only.
- Evaboot adds a
LinkedIn URLfield on people and aDomainfield on organizations the first time it needs them. If Pipedrive refuses the standard job title field, the title goes to a customJob titlefield.
How records are matched:
- People: by email first, then by the LinkedIn URL. A person pushed before is found again directly.
- Organizations: by domain first, then by exact name.
- A match is updated, never duplicated. Without overwrite, only empty fields are filled.
- Even with overwrite on, an existing email is never replaced, labels are added (never removed), and owners are never changed.
- A lead with no email and no LinkedIn URL is skipped, since Evaboot could not find it again.
Send an export by hand
Section titled “Send an export by hand”On the export list, click + in the Push column of a finished export (Push this export) and pick your Pipedrive integration. The export must be unlocked first. Click the Pipedrive logo in the same cell to see the push log: created, updated, skipped and failed counts.
To send every run of a recurring export, pick the integration under Send new leads to when you set the schedule up.
If it didn’t work
Section titled “If it didn’t work”- “Pipedrive connection was cancelled or failed”: the approval on Pipedrive did not finish. Click Connect Pipedrive again.
- Reconnect shows in the Status column: Pipedrive no longer accepts the connection. Click Reconnect and approve the access again.
- “Pipedrive is not responding”: wait a few minutes and try again.
- Some records failed: open the push log. A failed record shows Pipedrive’s reason, for example a contact owned by a colleague you cannot edit. The other records are still sent.
- The push failed with a rate-limit message: Pipedrive limits API usage per day. Click Retry in the push log later. Records already sent are found again, not duplicated.