Pabbly ↔ Pipedrive / Strange Behavoir with "Find Person"

[Finding Frodo]

Your Task History ID

IjU3NjUwNTY4MDYzNzA0MzA1MjY4NTUzMDUxM2E1MTY3NTQzNTBmMzki_pc

Hello folks,

since 1-2 weeks I have problems with the "Find Person" request of the Pipedrive integration. I use it to find a person by email, which you can see in the provided task history.

The error, that occurs for a while now, is: "Required field Term missing." The term is the email of the person in this case. In the request URL the term is empty. But the source, where I take the email from, is clearly containing valid data, as you can see for example 2 tasks above the failing one.

So I can only guess, that the "Find Person" method has some kind of bug.

Please fix asap, since wide parts of workflows rely on this (I'm sure not only in my account).

 

[Preeti Paryani]

Hello @Finding Frodo,

Could you please try deleting the specific step, re-read it, and then add a test? Let us know the results afterward.

 

[Finding Frodo]

Hello Preeti,

I tried that, but without success. Also I think it's not a good practice (in sense of support) to let the user recreate parts of the workflow, as this is much work, needs time to test and has effects on some of the following tasks. The same with "create a new connection and test with that one", which is even worse and will be your next suggestion, I'm sure.

I'm pretty sure that the problem here is the data source, meaning, where this email address comes from, that is used as the term.

As you can see, if you have a closer look at the workflow and history of failed executions, the email comes from step 2 in the workflow. It is the result of a request to WooCommerce API.

The task history tells clearly, that an email address is received from Woo. Same with the firstname and lastname.

However, this email address seems to be empty when it is used in the later step 8.

I found that out, because there is also a problem in step 11 (Pipedrive → Custom API Request), which in general works fine, but uses the firstname and lastname from the WooCommerce request, but both are always empty.

Please take a deeper look into what happens to the data between it is returned from WooCommerce (task 2) and then later used in Pipedrive requests (task 8 & 11).

 

[Preeti Paryani]

Hello @Finding Frodo,

Thank you for sharing the detailed observations, and we truly appreciate the time you've taken to investigate the issue from your end.

We’re really sorry if the troubleshooting suggestions felt repetitive or inconvenient; we completely understand your concern. While steps like creating a new connection or rebuilding parts of the workflow may seem tedious, they do sometimes help identify or resolve underlying issues, which is why we initially recommend them.

That said, we’ve reviewed the workflow and history more thoroughly, and we agree with your assessment. It appears the root cause lies in the data transition between step 2 (WooCommerce) and its later usage in steps 8 and 11.

We've escalated this to our technical team for further review, and as soon as we receive any updates, we’ll share them with you right away.

We sincerely apologize if any part of the support process felt lacking. Our aim is always to assist effectively, and your feedback helps us improve.

 

[Finding Frodo]

So, how is it going? This Bug is really getting annoying.

 

[Soumya Tripathi]

Hello @Finding Frodo
Thank you for the follow-up. Our team is still looking into the issue. Could you please provide us with the workflow URL in which you were facing issue, as the Task History ID you provided is no longer available?

 

[Finding Frodo]

Workflow IDs where this happens the most are:

IjU3NjUwNTY1MDYzNTA0Mzc1MjZkNTUzMzUxM2Ei_pc
IjU3NjUwNTY1MDYzNTA0Mzc1MjZkNTUzYzUxMzIi_pc