Hello,
I’m using version 1.33.1 self hosted
When I create a Pipedrive filter with the n8n http node it does create me an empty or better corrupt one in Pipedrive. Can’t delete it there or modify.
When I do exactly the same with the same API Token in make it works. Can you tell me whats the difference?
It looks like your topic is missing some important information. Could you provide the following if applicable.
hello @Sebastian1
I’m not familiar with Pipedrive, but are you sure you have to provide the null values to the API?
Plus I see the empty “or” filter there.
Thanks for your reply. The “null” values are needed and the glue doesn’t make any difference if I remove it.
The Main thing I have is that in make.com it creates the filter without any problem
You can open the dev console (f12 → console tab) and see what the actual request is being sent to. Maybe that will helps
[Node: “PD - Create Filter1”]
Object { headers: {…}, method: “POST”, uri: "Log in ", gzip: true, rejectUnauthorized: true, followRedirect: true, resolveWithFullResponse: true, followAllRedirects: true, timeout: 300000, body: {…}, … }
body: Object { name: “[MAKE-EXPERTS7] - New Deals with Attached Products”, conditions: {…}, type: “deals”
conditions: Object { glue: “and”, conditions: (2) […] }
name: “[MAKE-EXPERTS7] - New Deals with Attached Products”
type: “deals”
: Object { … }
encoding: null
followAllRedirects: true
followRedirect: true
gzip: true
headers: Object { “content-type”: “application/json”, accept: “application/json,text/html,application/xhtml+xml,application/xml,text/;q=0.9, image/;q=0.8, /;q=0.7” }
accept: “application/json,text/html,application/xhtml+xml,application/xml,text/;q=0.9, image/;q=0.8, /;q=0.7”
“content-type”: “application/json”
: Object { … }
json: false
method: “POST”
rejectUnauthorized: true
resolveWithFullResponse: true
timeout: 300000
uri: "Log in "
useStream: true
: Object { … }
Very strange:
With this http node it does create the corrupt filter
With that new created one it works
Do you find the difference?
The differences only with the URL (expression vs fixed type) and body. But I bet the issue is with body. When it is set to expression mode, it should be wrapped into JSON.stringify method, like this:
As soon as I copy this HTTP module into the scenario I need it, it does create me the corrupt one also it has the same output JSON. When I use it in a simple scenario where only the trigger node is before it does work as expected.
I did also copy the node from the bigger scenario into a new workflow but also does create a corrupt filter in Pipedrive.
Any Idea what it could be?
When I run it after the trigger node it works but when it runs after the if node it doesn’t
Does anyone has an Idea how this could happen? I do only use the credentials from previous trigger node. Nothing more and the node is just copied so has the same configuration.
I found the problem. I had to replace the Pipedrive module with the http module. Somehow the Pipedrive module did corrupt the filter. I don’t know why…
In that module I use the filter ID to get the Deals maybe that cause the problem.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
