New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipedrive Integration Not Working #14759
Comments
It seems like the issue with the Pipedrive integration not working when attempting to add it to your cal.com account might be related to a misconfiguration or absence of the Pipedrive client ID in the application's settings. The error message "App is not found" could indicate that the application is not correctly recognizing the Pipedrive client ID during the OAuth authorization process. To address this, you should verify that the Pipedrive client ID is correctly set in your application's configuration. This involves checking the environment or configuration files where the The process involves the application querying a database to retrieve the app keys, including the If after verifying the client ID the problem persists, consider reviewing the user authentication flow and the determination of the
|
@dosu I'm not using the self-hosted version, I'm using the cloud version |
If you're encountering the "App is not found" error with the Pipedrive integration on the cloud version of Cal.com, it's likely due to a configuration issue with the Revert API keys, which are essential for the integration to work properly. Here's how you can address this:
By ensuring your Revert API keys are correctly configured and following the steps above, you should be able to resolve the integration issue.
|
Issue Summary
I tried to add Pipedrive to my cal.com account via the app marketplace and got an error saying the app does not exist.
Steps to Reproduce
https://oauth.pipedrive.com/oauth/authorize?client_id=[REDACTED]**&redirect_uri=https://app.revert.dev/oauth-callback/pipedrive&state={%22tenantId%22:%**[REDACTED]**%22,%22revertPublicToken%22:%22**[REDACTED]**%22}
The text was updated successfully, but these errors were encountered: