The built in PipeDrive API does not allow interfacing with PipeDrive Projects other than via a manually built API call which loses the ability to look up and map items. How can one get the PipeDrive API support in Make extended to include Projects?
@rsgbmayer Are you talking about that if you use API call for pipedrive then you can’t mp result from that module to different module???
Princy Jain
Make consultant,
For consulting support: Follow up Automated
2 Likes
No, what I am asking/saying, there is a whole section of the API for “Projects” that is not present in the Make implementation of the API. As such, the only way to interact with the “Projects” API in PipeDrive is through a manual API call.
Ie none of these are present in the native PipeDrive integration in Make:
@rsgbmayer well if module is not present then yes “make an api call” is only solution.
Or if you need custom module that also can be built.
Let me know if yiu need any soecific help in this. But yes make an api call have to be used and no other way around.
is there no mechanism to have Make update and add these calls to the pre-defined integration?
Welcome to the Make community!
That’s a great idea! I’m sure others would agree that this is a nice feature to have.
You can submit this suggestion to the Idea exchange, under App improvements.
Don’t forget to search for it first, just in case someone already suggested it, so that you don’t end up creating a duplicate.
2 Likes
Officially from make there is only option to vote for updation.
But i am sure many people are using through “make an api call” only. As that’s the only workaround available.
The Pipedrive Projects API endpoints are still in beta. As such, they’re subject to change - and it’s for that reason that we don’t typically implement App modules in Make for beta endpoints.
When it’s out of beta we’ll certainly be taking a look at implementing the relevant modules - but in the meantime, as @Princy suggested, the Pipedrive Make an API Call module will be the best way to access these.
3 Likes