Connecting Your CRM
HubSpot, Pipedrive and Salesforce, with Notion coming soon: what syncs, when it syncs, and the manual push for everything else.
On this page
The CRM integrations follow one principle: your CRM gets buyers, not noise. LeadPinger does not mirror every captured lead into your CRM; it creates records at the moment a lead is Qualified, the status meaning "interest confirmed, worth pursuing". Your pipeline stays a pipeline.
What each one creates
| CRM | On qualification |
|---|---|
| HubSpot | A contact and a deal. |
| Pipedrive | A person and a deal. |
| Salesforce | A Lead. |
| Notion | Coming soon. |
Records carry what LeadPinger knows: the person's name and profile facts, and the verified email when enriched. A lead without an email becomes a record too, under its name or its handle, with the link to the post.
The manual push
Any individual lead can be pushed by hand, ahead of qualification: open the lead, and the ⋯ menu shows Push to HubSpot (or your connected CRM). Useful for the lead you are about to call regardless of status.
Setup
- On Integrations, click Connect on your CRM and sign in through its own authorization screen.
- Notion (coming soon): pick the target database from the card after connecting.
- Qualify a real lead when you are ready to see it flow; there is deliberately no test button on CRM cards, because a test would create a real record.
Practical notes
- Statuses in LeadPinger drive the sync, so a tight habit around marking leads Qualified is what makes the CRM integration sing. See The Leads Queue for the status vocabulary.
- Delivery health shows on the card. A failed push marks Last send failed; fix the connection and qualify onward.
- Prefer your own pipeline logic? The raw webhook emits signed lead events and you decide the rest.
Questions this page didn't answer? Email support@leadpinger.ai, we usually reply within one business day.