I’ve been notified that Pipedrive modules are being deprecated because of a change in the Pipedrive API. We only have until Jan 31st before the modules stop working.
Pipedrive has had API V2 available for years, but Make hasn’t updated modules. Also, we are being told that existing modules will stop working after Jan 31st, yet they haven’t created a full contingent of module replacements. For example, Get Organization Details is no longer available, despite this feature being available in the Pipedrive V2 API.
It seems that the Make team has waited a couple of years to update to the new V2 API, and now that they have they haven’t fully replaced functionality that was available in V1.
Is this normal? Should we expect 15 days notice for modules to be deprecated?
I have hundreds of modules to update, and not all of them have V2 modules available for a quick replacement. I could do custom API calls to the V2 API, but this will take much longer to implement.
What is the solution to this issue? Is Make building more modules on the new V2 API? Are they going to be available next week at the earliest?
One year ago I asked Make when they’d be updating to the V2 Pipedrive API. They said at the time they’d give sufficient notice when this happens. Is 15 days sufficient?
This is totally insane! I have more than 60 scenarios to update and the first two already didn’t work! It should be possible to replace at least most of the modules while keeping the settings. I look forward to call my client on Monday …
I’m dealing with exactly the same issue here and fully agree with this concern.
I have dozens of critical production scenarios, and a 15-day notice is simply not feasible for anyone running CRM operations at scale with active clients.
The most worrying part is not the deprecation of the Pipedrive V1 API itself (which was expected), but the fact that Make did not release a full equivalent set of V2 modules. This forces us to rebuild complex automations manually using HTTP calls, without feature parity and without enough time to properly test and validate.
In my case, this directly impacts sales, customer success, and financial automations. These are not “quick fixes.” We’re talking about workflows that took months to design, refine, and stabilize in real-world environments.
It feels like there was a serious planning gap between Pipedrive and Make. If the V2 API has been available for years, why was the module migration left until such a critical moment?
And honestly, 15 days is not a notice period — it’s a crisis alert.
What we urgently need:
An extended deadline or temporary fallback
A clear roadmap for the remaining V2 modules
At least minimum functional parity with the V1 modules
Without this, professionals who rely on automation for their clients’ operations are left completely exposed.
Modules that you’ve previously saved before the deprecation notice now have (Deprecated) listed beside them.
When you go to add a new module, you no longer see the “deprecated” modules listed.
However, when you add a new module, it asks to create a new connection (OAuth, instead of the API Token the old modules use now). Most of the modules that I didn’t see earlier this morning are now available, but it isn’t clearly stated if they are using V2 or V1 from the Pipedrive API.
Easy webhook connections are now entirely gone. I guess we need to create a new webhook connection using the webhooks module? Maybe this is a limitation of the new Pipedrive API that doesn’t allow them to easily create connections? Annoying but not the end of the world.
If the new modules that I can now add are indeed V2, I can work with this. I can’t do it in 15 days, but at least the tools are mostly there.
Make really messed up this transition. They can still do more, give more time, and better communicate what is actually going on.
In the meantime, here’s half of one scenario I’ve got to sort out:
@Make Has sent me an email apologizing for not having all modules ready before the email communication went out. They have not apologized for the VERY short notice of just 15 days.
First of all, please accept our sincere apologies for the confusion and inconvenience this has caused as we completely understand how frustrating this must have been.
The updated modules were supposed to come out along with the mail but an issue occurred because our team was rolling out the updated modules gradually, which is why you were temporarily unable to see the equivalent new modules available in parallel.
That said, the rollout is now complete and you should be able to see the previously missing module(s), except for the modules that have no replacement as mentioned in our email communication, this is because Pipedrive has deprecated the corresponding API endpoints, and unfortunately this is outside of Make’s control.
Could you please verify once again on your end and confirm if the missing module(s) are now visible? The v2 modules should be available now.
Regarding the deadline and batch updating which you have mentioned for updating the hundreds of modules, we completely understand the frustration and we are currently having an internal discussion regarding this with our Developers. Once we get a better update, We will get back to you immediately.
I feel for you guys who are now stuck having to redo large scenarios and update loads of connections, been there many times. Can’t help much but I can suggest using Make’s browser extension: Make DevTool.
It has features that can help with updating connections and mappings within a single scenario in bulk, so it’s useful for large scenarios with dozens of similar modules.
I’d recommend trying it out on a copy of a scenario just to familiarize yourselves with how it works before running it in a production scenario.
Am in the same boat, though, thankfully only a few scenarios to adjust. What I’m finding weird is for the Person modules (Create, Update), ‘Job title’ is no longer an available field. Seems pretty fundamental. Any thoughts here?
Alternatively, try Copy Mapping: this one will require you to manually add V2 modules into the scenarios as replacements, but it may help with copying over the settings of the modules from the old ones to the new ones:
I don’t have legacy Pipedrive connections to test with so if you try out either of the above, could you come back and let us know if either worked in any capacity? It might help others with migration.
Thank you - that should work, though, given it’s a core/required field for a Person in pipedrive, it would presumably be better if it was added to the main Create/Update module…
Fields job_title, notes, birthday, postal_address and ims are only included if the company has contact sync feature enabled.
But I tested those two API calls without this feature enabled (and it worked) so I don’t see why the field can’t be included in the dedicated modules (unless I’m missing something).
I’ve also found that when you create a new Pipedrive webhook in Make, it no longer appears in the Webhooks list within Pipedrive.
In V1, when you created a webhook connection via Make, it would automatically display the webhook (and make.com) endpoint within the Webhooks page in Pipedrive.
Now with V2, Make can create the webhook, but there’s no way of seeing it in Pipedrive.
When I reached out to Pipedrive, this is what they had to say:
”It’s just advised to also create manually to ensure it’s running 100% and so that you can also see more information into sent requests and possible errors, usually it may create automatically, but usually advised to create manually.”
All of this tells me that both Make and Pipedrive have half-baked their development of API’s, connections, and communication.
We apologize for the frustration caused by this transition of our Pipedrive integration from API v1 to v2. We understand that the tight timeline has placed pressure on your teams, and for that, we are truly sorry. This was certainly not our intention.
Our team is actively collaborating with Pipedrive’s developers to address the current challenges and ensure we find a resolution that works for all of the sides.
We’ll keep you in the loop and update this thread later today with further updates.
Thank you for the honest feedback you’ve shared so far and for your patience.
Update Person: “job_title” and “postal_address” are not included as default fields?
via Make an API call, suggestions for updating “postal_address” (expects an array)? The addresses being updated are in various states of completeness (may or may not have all of the following: street address+city+county, in a single text field).
Thank you for your communication… “frustration”… really ? You make it easy! It is dramatic !
This migration should have been anticipated for long by Make. I am usually a big fan of Make but the way Make manages it so far is a shame. So please now collaborate with Pipedrive as much as you can but we need :
a delay
to recover the functionalities we had before and without replacing 1 deprecated Pipedrive module by 3 modules!
Like many users we have many Pipedrive modules everywhere on automations that are key for our process. So it is dramatic.
Furthermore, my first replacement try is not really a success as I cannot get the details as before in “Watch deals” module : now we only get related person and organisation IDs but the names and all the details we had in collections before in 1 module… same problem with “get a deal”… I don’t see the user current owner of the deal neither : it will be difficult for me to automatically send him an e-mail. Do you aim at making us multiplying modules?
What is your goal?
What is the problem & what have you tried?
