Pipedrive - Person is not found although it got linked

[Finspro]

Hi there,

again to this workflow: IjU3NjYwNTZlMDYzMjA0MzY1MjY4NTUzZDUxMzUi_pc

i linked the Person from find / create step to update and to link deal to person, but it wont take it:

this is what i mapped and it runs on error.

Also, is the delay a paying step? Thought it is a free task.

Thanks for your help.

BR
Christian

 

[ArshilAhmad]

In the 'Find or Create a Person' action step, you get two different labels associated with the Person ID—i.e., the label when a person is found is different from the one when a person is created. This breaks the mapping during automation.

Instead of using the 'Find or Create a Person' action step, we recommend adding 'Find Person' as the second step in your workflow. Afterward, add a Router to your workflow with two routes:

• Route 1: Use this route to update the person using the 'Update Person' action event if the person already exists in your Pipedrive account. Then, add the remaining steps to create a deal and add a note to that deal.
• Route 2: Use this route to add a person through the 'Create a Person' action step and add the rest of the steps.

 

[Finspro]

Good morning @ArshilAhmad

thank you for this reply - i had thought something like this and of course will try out the router.
But - to be honest, then please remove the double step feature that will lead to confusion here.
As this action "Find or Create" will then only work when the person is there and gets updated and never for finding it - as the payload can not be split into either data a or data b and you need the router then anyways.

This should be reviewed internally.

This being said, i wonder, are we able to get a scenario that might do this:

Router checks if contact exists or not then goes one of two routes but after the both paths they go both to continue on same next step?
Trigger --> Router --> Path A or Path B and then
Path A handled --> Create Deal (Step4) or
Path B handled --> Create Deal (Step4)

or would it be always to have all steps also under each path?


Will setup with route and let you know my feedback.

BR
Christian

 

[Preeti Paryani]

Hi @Finspro,

Thank you for your feedback regarding the "Find or Create Person" action. We will inform our technical team about your input.

Regarding your question, yes, the steps need to be included under each path in the router. If both Path A and Path B ultimately lead to the same next step (like "Create Deal" in Step 4), you will need to replicate the action in both paths. Each path should independently contain the necessary steps to continue to the next action.

Router checks if contact exists or not then goes one of two routes but after the both paths they go both to continue on same next step?
Trigger --> Router --> Path A or Path B and then
Path A handled --> Create Deal (Step4) or
Path B handled --> Create Deal (Step4)

 

[Finspro]

Hi @Preeti Paryani ,

thank you for your feedback, will build it this way, but doing these steps i encounter the next issue. Which may be also data based but in this case i am not sure how to handle this as this might always be coming.

When i contact that is in Pipedrive but not active yet (might got deleted but is in temp state from the application for some time) the system tells us the contact was found but not handles us any data:

So in this case i could trace that the mentioned account is deleted but still in system, but the step reports it as success.
Do you have an advise how i can use the information to realize the contact is not active anymore in system and would be recreated accordingly?

Thank you in advance.
Regards
Christian

 

[Preeti Paryani]

Hello @Finspro,

Regarding the issue you're encountering, the Pipedrive API is structured to handle scenarios like this. When you search for a person and whether they don't exist or are in a temporary or deleted state, the API will return a response indicating that the person doesn't exist.

 

[Finspro]

Hi @Preeti Paryani ,

ok, got it. So what would be the recommended procedure here?
I can not use the success result, as both times there would be one (existing or deleted but still in system).
So i assume i should check the ID behind the account if existing, or do you have a better approach?

Thanks,
Christian

 

[Preeti Paryani]

Hello @Finspro,

Yes, you got it right! You can check whether the ID exists in the result of the Find Person action. Based on this, you can set up the routes accordingly to determine if the contact is active or needs to be recreated.

So i assume i should check the ID behind the account if existing, or do you have a better approach?

 

[Finspro]

Hi @Preeti Paryani ,
ok will check that and let you know afterwards.

BR
Christian

 

[Finspro]

Hi @Preeti Paryani and @ArshilAhmad ,
just wanted to give feedback, i do the workflow now with Find Person (as Find and Create will not work correctly as intended (Please check that and maybe adjust this action or replace accordingly).

Then i go into router for Existing or New Contact (checking exiting ID in System).
There for Existing, i update the person with new contact data otherwise create new one, then create a deal and then need to update the deal because in the actions not all options are available in one action, which is sad and causes unneeded additional tasks.
After that i create a note.

That is working this way as expected, but as i said, the setup of the current actions are not very convinient and waste tasks and nerves and should really be reviewed, as Pipedrive is a really often used CRM out there.

If you would want to, i would offer you also more user feedback and tests on these changes.
But i want to say thank you anyway for your responsiveness and overall taking care of my concerns.

Regards
Christian

 

[ArshilAhmad]

hank you for the update. We are glad the workflow is working as expected. Is there a reason why you have used the 'Create Deal' and 'Update Deal with Custom Fields' action steps instead of using the 'Create Deal with Custom Fields' action step?

 

[Finspro]

Hi @ArshilAhmad ,
as i mentioned, not all fields of the deal are covered in one step, so i had to use both to get all information handled, that is why i told in the other case that we have a waste of tasks due to this situation.

Do you need more details on the fields?
Will that be reviewed?

BR
Christian

 

[ArshilAhmad]

Yes, we would like to know the exact field for which you are using the 'Create Deal' and 'Update Deal with Custom Fields' action steps instead of the 'Create Deal with Custom Fields' action step.

 

[Finspro]

Good evening @ArshilAhmad ,
of course, the fields i have available in Create Deal are:

• Title
• Creation Date
• Status
• Pipeline ID
• Stage
• Owner
• Organization
• Person ID
• Probability
• Value
• Currency
• Label
• Visible to

With the Update Deal with Custom Fields i need to fill / update at this moment (later need to use this for other fields as well):

• Source (custom field source not the standard)
• Name Interessent (might differ in our use case from linked Person)
• Telefon (might differ in our use case from linked Person)
• Email Adresse (might differ in our use case from linked Person)
• Eingangsdatum

So, i have exact the same fields also available in Create Deal with Custom Fields - but this is not the question here.
Our problem is, i have not all fields of regular Create Deal action available in both actions for ..... with custom fields.

Missing is for example:

• Pipeline ID
• Stage ID

Other fields have not the same settings, as they offer for example a picklist selection for Owner, or Label etc. so this is also not consistent for me.

 

[ArshilAhmad]

Thank you for sharing this information. Please allow us some time to look into this concern. We will get back to you with an update soon.

 

[Finspro]

Thank you @ArshilAhmad , looking forward for your information

 

[Preeti Paryani]

Hello @Finspro,

The parameter to enter the Pipeline ID is not provided by the API itself, which is why it cannot be included in the required action.

Upon reviewing the "Get All Deal Fields" action, we have observed that the Stage ID is associated with the "Phase" field. Therefore, you can add the Stage ID under the "Phase" field. You can retrieve the required Stage ID using the "Get All Stages" action.

Please refer to the attached images for further details. Let us know if you need any additional clarification.

 

[Finspro]

Good morning @Preeti Paryani ,
thank you for your feedback - so lets say, even with the mentioned steps, i will not be able to save the one extra step right?
The Pipeline is one of the most needed fields, so i need that first, so i need to use the basic step first.

BR
Christian

 

[Preeti Paryani]

Hello @Finspro,

If you only enter the Stage ID, it will still be added to Pipedrive, as the stage is interlinked with the pipeline in Pipedrive. Please try using the action without the Pipeline ID and let us know if it works fine for you.

 

[Finspro]

Hi @Preeti Paryani

Ok, i will test that.

But .... userfriendly is a bit different though

Thank you for your tip with that

Have a nice evening.
Regards
Christian