CRM
In short
How does Reply's Pipedrive integration work?
People are the only object that syncs, in both directions. Everything else (activities, deals, deal stages) is written by triggers rather than synced, which is a different mechanism with different behaviour. Reply also creates a filter inside your Pipedrive account that must not be deleted.
> Two different Pipedrive connections exist in Reply. This page covers the integration: a scheduled, > field-mapped sync between Reply and Pipedrive. Reply's in-product AI assistant can also connect to Pipedrive > separately, so it can look things up and act there while it works with you. They are set up in different > places, have different capabilities, and share no settings. If you want contacts and activity kept in step, > you are in the right place. If you want to ask the assistant about your Pipedrive data, see > agents.reply.io.
At a glance
| Availability | Available. Included on plans that offer CRM integrations – check yours in Billing |
| Direction | Two-way for people · Reply → Pipedrive for everything triggers write |
| Sync timing | Automatic on a regular cycle, with variation between runs, plus a manual sync. Trigger actions fire on the event, not on the cycle |
| What you need | A Pipedrive API token from a user with access to the people and deals you care about |
| Surfaces | Setup: in the app only. Once connected: the people that sync are readable and writable through the API and MCP. The trigger actions are configured in the app, not through the API |
| Does not | Sync organizations, deals or activities as objects · read anything dated before 2014 · offer a few Pipedrive fields for mapping |
Availability
Available on plans that include CRM integrations. Pipedrive connects with an API token rather than by authorizing an app, so the permissions the sync has are whatever that token's user has.
How to connect Pipedrive
Before you start
- Get an API token from the Pipedrive user whose access the sync should use
- Decide which people are in scope – the integration works through a filter, so this matters up front
- Decide whether you want trigger actions as well as sync, since they are configured separately
Connect
- Log in to Reply.
- Open the Integrations page, find Pipedrive, and click Connect.
- Enter your Pipedrive API key in the dialog and click Authenticate. The key is in Pipedrive under Settings → API.
- On the Steps tab, open the sync steps you want: people from Pipedrive into Reply, people from Reply into Pipedrive, or both.
- Set your field mapping in the integration's Mapping section.
The filter Reply creates
On connecting, Reply creates a filter inside your Pipedrive account, named so that it is clearly not yours; it says plainly that it should not be edited or deleted. The integration uses that filter to decide which people to read.
Do not delete or rename it. If someone tidying up your Pipedrive filters removes it, the sync stops finding people and the cause is not obvious from the Reply side.
What to expect
What syncs
| Data | Direction | When | Notes |
|---|---|---|---|
| People | ↔ | Every cycle | The only object that syncs |
| Activities | Reply → Pipedrive | On the event | Written by a trigger, not by sync |
| Deals | Reply → Pipedrive | On the event | Created or moved by a trigger |
What triggers can do
This is where Pipedrive differs most from the other CRM integrations. Rather than syncing activity on a cycle, Reply reacts to events (an email sent, opened or replied to, a link clicked, a call logged, a task completed) and performs an action in Pipedrive:
- log an activity against a person or a deal
- create a deal
- move a deal to the next stage, or to a specific stage
Activities Reply writes carry recognizable names (Email sent, Email Opened, Link Clicked, Reply, Positive Reply, Call logged) so they are straightforward to spot on a Pipedrive timeline.
Because these are triggers rather than sync, they behave like triggers: they fire once, on the event, and a trigger applies to every sequence unless a condition narrows it. See Why did a trigger not fire?.
What doesn't sync
- Organizations, deals and activities as objects. Deals and activities can be written by triggers, but they are never read back or kept in step.
- Anything dated before 2014. Records older than that are not read.
- A few Pipedrive fields are never offered for mapping, including the visibility and picture fields.
- Activity in the other direction. Work logged in Pipedrive does not appear in Reply.
Common problems
- People stopped syncing after a Pipedrive tidy-up – check the Reply filter still exists in Pipedrive.
- An activity was not logged – activities come from triggers, so check the trigger, not the sync. Full guide
- A person never arrives – a required Pipedrive field left empty, or a value too long. Full guide
- Nothing syncs at all – check the API token is still valid; it stops working if the user is deactivated. Full guide
Pause or disconnect
Turn the integration off to stop syncing while keeping steps and mappings. Disconnecting removes the token; records already synced stay in both systems. The filter Reply created in Pipedrive is not removed automatically: delete it yourself once the integration is gone for good.
FAQ
Can Reply sync deals with Pipedrive?
Not as objects. Reply can create a deal or move one to another stage through a trigger, but deals are never read back or kept in step.
What is the "Reply.io filter" in my Pipedrive?
Reply creates it to decide which people to read. It must not be edited or deleted, or the sync stops finding people.
Why do activities appear with odd names?
Reply names the activities it writes after what happened (Email sent, Link Clicked, Positive Reply) so they are recognizable on the timeline.
Does Reply sync organizations?
No. Only people sync.
Need help connecting Pipedrive?
If the connection fails or data isn't syncing the way you expect, the Reply support team can check your integration settings with you. Open the Reply Help Center and send the team a message.
To get an answer faster, include:
- which integration and which sync step is affected
- what you expected to sync, and what happened instead
- the error text from the integration's Logs, or a screenshot of it
Don't send passwords, API keys, or access tokens.
Related
- CRM and integrations – everything Reply connects to
- Sync Reply with a CRM – how sync works for every CRM
- Why did a trigger not fire? – Pipedrive activities come from triggers
- Why did my CRM sync stop?
Build with Reply
- REST API: Contacts – read and write the contacts that sync
- Webhooks: Webhook events – react to Reply events in your own systems
- MCP: docs.reply.io/mcp – let an assistant read and update synced people