Pipedrive Connection and update issues

[Finspro]

Hello Community,

as my first day with Pabbly i want to say hi to you all, i am happy to be here!

Coming from Zapier many things appear different for me and now i have some issues already with my first connection - Pipedrive.
The connection is very easy - it even stays in Pipedrive itself!

What it should do is simple:
Trigger: Check for new Deal
Filter: Check if an custom Field is empty (in this case, i setup a custom field "Deal ID" to store the record ID to be able to search for this value as well.
Action: If Filter ok, then update Custom Field "Deal ID" with the record (Deal) ID

Issues i have are the following:

1. Is it correct, that Pabbly always tries to load over 100 records to choose one from to test with? It slows down the whole interface and i can not work smooth at all, everything is stuck.
   
   
2. When i foung the record, i could not identify the custom field by any name, it was labeled with an strange custom string label like this:
   Res2 Data 99 9460f7c7a8b4a063fd91dbf18ff0838f5b4f7072 (very hard to guess, or do i miss here any used syntax maybe?)
   
   
3. When i found the String (only with trial and error) i think i could set up the filter correct, but when i wanted to place the update step, then i was not possible to select the field with this string above in the list.
   In fact, there have been really few instead.
   How can i then update the desired field when a) it is not visible or b) i have such a hard time to discover the right one?
   

I guess there must be any kind of hint or special way to find the right field and i also assume, i just dont see anywhere the correct field or button to get this field for the update process?

As this is just the very first step on my hopeful long journey, every help to get the whole process started smooth is highly appreciated

Thank you all in advance, and all the best for you.
Best regards
Christian

 

[Preeti Paryani]

Hello @Finspro

Kindly allow us some time to look into it we will get back to you soon.

 

[Finspro]

Hi @Preeti Paryani ,

Thank you so much for your feedback, sure, take your time to investigate my points
If you need any additional information, just let me know.

Best regards
Christian

 

[Preeti Paryani]

Hello @Finspro

By default, there is a limit of 500 deals that can be fetched under the "update deal" action. This is the reason for the system latency.

Is it correct, that Pabbly always tries to load over 100 records to choose one from to test with? It slows down the whole interface and i can not work smooth at all, everything is stuck.

The custom fields are sent by Pipedrive in this format, and no modifications are made on our end.

When i foung the record, i could not identify the custom field by any name, it was labeled with an strange custom string label like this:
Res2 Data 99 9460f7c7a8b4a063fd91dbf18ff0838f5b4f7072 (very hard to guess, or do i miss here any used syntax maybe?)

If you'd like to add more fields to be updated under the "update deal" action, you can click the (+) button to add pairs of labels and values. Please refer to the attached screenshot for guidance.

In fact, there have been really few instead.
How can i then update the desired field when a) it is not visible

To update a custom field, you can find the custom field key using the "Get All Deal Fields" action. This requires a one-time manual setup, which is detailed in the screenshot provided below.

i have such a hard time to discover the right one?

You can obtain the custom field key from the New Deal trigger response. Look for it in the response from the "Get All Deal Fields" action. Once you identify the associated label, you can map the custom field key and its value accordingly in the "update deal" action step.

I hope this helps resolve your issue. If you have any further questions or concerns, please let us know

 

[Finspro]

Hi @Preeti Paryani ,
thank you very much for your detailed feedback, will try the points and let you know,

Is there any way (for the setup of the new workflows) to reduce the number of queued records for performance reasons individually?

Will come back with results of the testing.

Best regards
Christian

 

[Finspro]

Hi @Preeti Paryani ,
i am sorry but i am stuck here with the testing

I tested like you said, i checked for the field that contained the value and this aplhanumeric part i copied into a new label field and for the value took the record id from the first step where it checks for the new Deal.

I tested with a new creation but it did not work.
Also wanted to check with the webhook listener for a new entry but it seems not to work?

What am i doing wrong here?
Is there any kind of example process for this that i can follow?
Thank you for your help in advance.

BR
Christian

 

[Preeti Paryani]

Hello @Finspro

Kindly set up a new workflow and add the Company Domain as mentioned in the image below. You can also refer to this tutorial -

Let us know if you face any further issues.

 

[Finspro]

Hi @Preeti Paryani,

good morning

Good news first:
i changed the Company Domain according to your recommendation from full URL to just the Company Name part.
Although i received also data from Pipedrice before as well, i have the impression, that now after the change the listening function is working correctly so i can use a single entry to check for, thank you for this hint.

For the major part i could now manage the correct updates, but i have some small follow up questions on this:

1. I thought when i leave fields blank in the update action, it would simply not update anything here, but for example, i leave the Value field blank then the update deletes the value from the deal and sets it to 0 - so i have to correct this by placing the value from the initial record on the field. But this should not be the expectation right? How can i know, which fields i would need to prepare with the data from the initial record, and which i could leave blank?
   
   
2. The same for the Stage / Phase, which is not declared as mandatory but when i left it blank it returns the error that the stage needs to be a number but i just wanted to leave the stage as it is - so i also put the stage of the initial record in.
   
   
3. What is also not clear to me, it seems that the close date is also updated by the current date - time, although i have placed a separate key in the set for this and it not even should do that, i would expect it for close won or close lost of the deal but not as update when i not even select it.
   
   
   
   
   
   
   
   
   
   

Maybe you can give me a bit of input here? Any help is much appreciated!

Thank you in advance, best regards
Christian

 

[Preeti Paryani]

Hello @Finspro

Thanks for the update.

We have made a small change due to which if the default fields are left empty they will not be updated with empty values but in case of any additional field, data is required to be mapped else they will be updated with empty values.

Also, as you have left an additional field named close time empty it got updated with the current date and time which caused the close date to be updated with the current date.

close date is also updated by the current date

 

[Finspro]

Hi @Preeti Paryani ,
thank you for the update, i will do a test and let you know.

This said, the additional field that you mentioned was only inserted because the update happened without it on the Deal Close Date, so i tried to achieve the field to stay empty, with an empty field but it did not work.

So i will check the current status and change history of that record.
Will come back soon with an update for you.

BR
Christian

 

[Finspro]

Hi @Preeti Paryani ,

i did a fresh test, for that a new deal has been created and even all steps from the existing workflow i deleted and setup new to have fresh setup.

For the update step, i left every field blank, except the ID for the Deal to be updated (it was mentioned as required) and the desired update for the custom field (Deal ID) which i also updated with the record ID.

Here are the screenshots so you can see i have no more updates:

BUT, as before, the Close Date and Close Time (reflected in the screenshot below as "Deal abgeschlossen am:") seem to get updated from blank to current date (maybe also time but here it shows the date), but i do not want that.

Please double check that as well.
It is crucial that nothing that is not mapped or selected to get updated gets not touched.

Also, would it be possible to get the fields for the update action not prepopulated with any data (in this case it was not even the data of the record i used in the trigger listening record, but just record number 1 from the database in pipedrive)?

Thank you for your feedback in advance.

BR
Christian

 

[Preeti Paryani]

Hello @Finspro

Kindly allow us some time to look into the issue. We will get back to you soon.

 

[Finspro]

Hello @Preeti Paryani ,

sure, will be happy to hear from you soon.

Best regards
Christian

 

[Preeti Paryani]

Hello @Finspro

Could you please create a new test to verify if the close time is now updated with the current date and time? We conducted a test yesterday, and it did not occur on our end.

 

[Finspro]

Hi @Preeti Paryani ,

just tested again for the workflow.
And i got this (all yellow stuff came through Pabbly)

So it means, now it even tries to set the Close Date (or time or both) 2 times, instead of once previously.
First it sets from empty to the current date, and then again like setting a second time.

So whatever you did, it made it worse.

Please check this again, this can not be used like this.

Thank you very much.

Please expect a little delay in my response this week as we are on business trip.
But i try to response as soon as possible.

Kind regards
Christian

 

[Preeti Paryani]

Hello @Finspro

Our team has made some changes. Can you please test and check if it's working fine for you?

 

[Preeti Paryani]

Hello @Finspro

Our team has added a new action for your convenience named "Update Deal with Custom fields". Kindly try it on your end and let us know if it works for you.

 

[Finspro]

Hi @Preeti Paryani ,
thank you so much for your answer on this. As mentioned i was away this week but i will try the proposed solution asap.
Can you please just verify, that i need to use another action for this?
Or can i still use the regular "update Deal" Action?

Thank you and regards
Christian

 

[Preeti Paryani]

Hello @Finspro

You can use the "Update Deal with Custom fields" action if you want to update the deal with custom fields.

 

[Finspro]

Hi @Preeti Paryani ,
i left the Workflow as it was before, just with Update Deal, not the new one.
It seems the previous not wanted action has been corrected there - i assume that was made as you reported above Oct 28, 2024?
However, i did not setup anything new, so can i expect this to work also with fresh setup then as it should?
Or do i have to do any changes manually?

If all is fine, we can close this for now.

Thank you for your feedback, Best regards
Christian