What the integration does
Contacts, on reply or accept. When a prospect accepts your connection request or replies to a message, Prospectio creates that contact in Pipedrive if it does not exist, or updates the record if it does.
That is it. It is a deliberately small integration and we would rather describe it accurately than imply a full pipeline sync you would discover was missing in week two.
What it does not do
Worth stating plainly, because most integration pages in this category do not:
- It is one-way. Prospectio writes to Pipedrive. It does not read from it.
- You cannot push a Pipedrive list into a Prospectio campaign from the CRM side. Build the list in Prospectio, or send it in over the API.
- It does not log every sequence step as an activity against the record.
- It does not create meetings in Pipedrive when one is booked.
If you need any of those, the API and webhooks will do it. See the Zapier, Make and n8n pages for the pattern: a POST with an X-API-KEY header, triggered on whatever event you care about.
Setup
- In Prospectio, go to Settings → Integrations and connect Pipedrive
- Authorise in Pipedrive
- Send yourself a test reply and check the contact appears
One thing that catches people out. The authorisation screen names Integrio.io rather than Prospectio. Integrio is the middleware handling CRM connections on the platform Prospectio runs on. It is expected, and if you are the person approving app installs at your company it is worth knowing before you see it.
Why it matters
Outreach that is not in the CRM did not happen, as far as the pipeline review is concerned. Reps stop logging manually within about a fortnight, every time.
Getting the contact in automatically at the moment they engage is the part that actually gets skipped, and it is the part this handles. The rest of the picture, the activity trail and the meeting record, currently needs a webhook.