-
Notifications
You must be signed in to change notification settings - Fork 60
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 fails #1596
Comments
I'm very sorry for the trouble @harsha-sgroup. I can confirm there might be an issue with the integration. I will have a developer check into it shortly. 🙂 |
I can successfully replicate your issue when I have "Search for all data" turned off in my access scope list. Is your Pipedrive app got "Search for all data" enabled in your access scope list? If not, this needs to be enabled and then click Save. Remember, with any Pipedrive app or OAuth integration, when you update your access scopes, you need to re-save your integration. In this case, under Freeform > Settings > CRM, select your Pipedrive integration and click Save. This will trigger new access and refresh tokens based on your updated access scope. Then test your integration again by submitting a form. |
I'm still facing the same issue. 'Search for all data' is set in my scope list, and the other settings are unchanged. |
Can you setup a new integration and test that, incase there is stale data somewhere? |
Did that and tested every possible scenario with Leads, Deals, Organisations and Person mapping. Still it's not saving anything in Pipedrive. Freeform version: 5.7.2 |
I feel this is an isolated issue since all our test environments work as expected. Can you please send me a copy of your database? I'd like to check your field mappings etc. Do a bit more investigating using your database and data. |
PR submitted changing how fields are fetched for leads. Hopefully get this merged soon. I noticed these errors while testing your field mappings though.
You have both of these fields set to use string type fields, with First Name a hidden field with no default value. |
Hi @harsha-sgroup, This will be corrected in Freeform 5.7.3, which will be available later today. 🙂 |
Hi Kelsey,
The integration worked this time.
Thanks
…On Fri, Nov 22, 2024 at 9:43 AM Kelsey Martens ***@***.***> wrote:
Hi @harsha-sgroup <https://github.com/harsha-sgroup>,
This will be corrected in Freeform 5.7.3, which will be available later
today. 🙂
—
Reply to this email directly, view it on GitHub
<#1596 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXYCKGJ3XOK46T6PVQOJ45T2BZOXXAVCNFSM6AAAAABQWTTJI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJSGUYDKOBSGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
[image: Harsha Mudiyanselage]
[image: S Group]
Harsha Herath
WEB DEVELOPER
S. Group
73 - 75 St John Street, PO Box 1271
Launceston, Tasmania 7250
p 03 6311 1403
Website <https://sgroup.com.au> | Facebook
<https://www.facebook.com/sgroupofficial> | Instagram
<https://www.instagram.com/sgroupofficial>
|
What happened?
The Pipedrive integration returns the following error. Currently, only the Map to Lead is enabled, and relevant fields are mapped to Pipedrive.
Errors and Stack Trace (if available)
How can we reproduce this?
NA
Freeform Edition
Pro
Freeform Version
5.6.8
Craft Version
4.12.5
When did this issue start?
After upgrading from older Freeform version, After upgrading from older Craft version
Previous Freeform Version
No response
The text was updated successfully, but these errors were encountered: