Last week I finally completed the migration from the V1 to the V2 Pipedrive API. Since Make doesn’t offer a native V2 Pipedrive module, I had to build everything using HTTP modules.
Does anyone know whether V3 will be deprecated in the coming days, weeks, or even years?
I really hope the legacy V3 module will remain available, otherwise I’ll need to rebuild my entire scenario again. And the one above is just 1 out of 10…
Maybe it would be a good idea for the Make developers to create a migration tool that can automatically update all existing V3 HTTP modules to V4 with a single click.
Hello @TT92 , I understand your situation — you’ve already spent a lot of time upgrading your Pipedrive modules, and now it may feel overwhelming to consider upgrading your HTTP modules as well.
However, there’s no need to worry about having to migrate to the new HTTP app in the near future. Both versions will continue to run side by side.
At some point, we will end support for the older HTTP version (we don’t yet know exactly when). This means it will be deprecated, but it will remain fully functional in your existing scenarios. If you decide to upgrade later, you’ll be able to do so at your own pace.
You may continue to use the legacy app but just letting you the new app makes workflows easier, reduce technical complexity, such as pagination issues. |
Currently Make uses Pipedrive v1 but soon in near future you can expect v2 modules as well
I believe yes, the output variable will change because when you add a v4 app, it will have a new module no, and the variable should be mapped from its output. However, if you continue to use legacy app then there is no need to change anything
