I’m having the exact same problem. The error appeared about 5 days ago. I have various workflows working fine for over a year, then all of them broke with the Pipedrive node.
With “Resolve Properties: False” no error is raised.
Using: 1.40.0
I already contacted Pipedrive and reported the bug. Their answer was:
Unfortunately, the logs (the screenshot) you sent us do not explain what is wrong with the API request.
The problem seems to occur when parsing JSON data, especially with the split function that is called for an object that should actually be a string.
In fact, our GET endpoints do not expect an object.
However, without knowing the endpoint or the response you are retrieving, my colleagues can’t be sure if the issue is related to an invalid request or an issue with our API endpoints.
The technician has also tested our GET persona endpoints and found no issues, so they are confident that everything is working on our end.
My colleague suggests you get in touch with n8n support and if they assume the issue is on our end, we need information about the endpoint and the response that is being fetched.
Also, test the same endpoint in Postman and let us know if you get an error there as well.
EDIT: Thanks @BramKn for your answer, we posted at the same time. I’ll update and report back. Thanks!