Open JakobStadlhuber opened 1 month ago
/bounty 50
/claim #16797
in the PR body to claim the bountyThank you for contributing to calcom/cal.com!
/attempt #16797
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@itsalam | 1 cal bounty | TypeScript, JavaScript, Python |
﹟17563, ﹟17580 |
Cancel attempt |
@JakobStadlhuber, I'm not completely familiar with working CRM integrations, are you able to identify which PipeDrive API's corespond to the current Revert counterpart? The naming between the two don't match, and I'd prefer not to infer the wrong ones.
Revert documentation for reference: https://docs.revert.dev/api-reference/api-reference/crm/company/get-company
Revert has to be removed its deprecated and has to be replaced with an official Pipedrive integration: https://developers.pipedrive.com
💡 @rajesh-jonnalagadda submitted a pull request that claims the bounty. You can visit your bounty board to reward.
@JakobStadlhuber
I was trying to ask what Revert APIs correspond to which Pipedrive APIs. i.e PipeDrive's Acitivity API is what should replace Revert's Event API, but its not clear until inspecting every other API's body one by one.
Either way I think I figured it out, no worries.
@itsalam I've already raised the PR. If you think it could be improved, we can collaborate and share the work accordingly. What do you think?
Although my implementation might differ quite a bit, I'd be happy to collaborate reach a middle point. I'll post my implementation in a bit for reference.
Is your proposal related to a problem?
Yes, the Pipedrive integration in Cal.com is currently not functioning because it relies on Revert.dev, which has been deprecated and no longer maintained since September 2023. When I try to add Pipedrive via the web UI, I receive an error message stating "pipedrive client id missing."
Describe the solution you'd like
I would like the Pipedrive integration to be updated to remove the dependency on Revert.dev. Instead, the integration should directly use Pipedrive's API, implementing OAuth2 authentication. This would involve updating the web UI to allow users to input their Pipedrive Client ID and Client Secret to establish the connection.
Describe alternatives you've considered
I've considered manually integrating Pipedrive using custom API scripts, but this approach is not practical for most users due to its complexity. I also looked into third-party integration tools, but they may not offer the same seamless experience and could incur additional costs.
Additional context
Maintaining a functional Pipedrive integration is crucial for users who rely on it to sync their scheduling with their CRM systems. The deprecation of Revert.dev has disrupted this workflow, impacting productivity. Updating the integration will restore this essential functionality for many users.
Requirement/Document