Hi @DennisDrzosga 

Good question.

The field description and error both indicate the Lead ID must be AT LEAST 2 characters.

Check to see if the Lead ID you are trying to test with still exists in Pipedrive.

Yes, but the URL of PipeDrive Show me the following: 

https://deeprojects.pipedrive.com/leads/inbox/6403f7d0-b6de-11ed-ba12-2990a070e908
 

And a LeadID with only 2 Characters wouldn’t make much sense or?

Best Regards Dennis
 

@DennisDrzosga

Check if this Lead exists: https://deeprojects.pipedrive.com/leads/inbox/4510bb00-b6df-11ed-af2c-d5554906f2e

The reason for the error may be that the Lead ID you are trying to test with in the Zap no longer exists. (e.g. the lead could have been deleted or is dummy data)

The Lead exists. The Problem is the two Chars Lead-ID. 

I think that something in the Zap is not correct. 

@DennisDrzosga

I’d recommend opening a ticket with Zapier Support about this because it could be a BUG: https://zapier.com/app/get-help

Leads in Pipedrive are a newer feature and use different types of IDs, than Deals, Persons, Orgs, etc.

However, the ID field expects a # as indicated by the 123 icon next to the field label, which is likely contributing to the encountered error.

The workaround would be to use the Pipedrive API: https://developers.pipedrive.com/docs/api/v1/Leads#getLead

App APIs can be used in Zaps with the Webhooks app as an action step: https://zapier.com/apps/webhook/help

There is also BETA Zap action available for Pipedrive that can help with this API: https://help.zapier.com/hc/en-us/articles/12899473501453-Create-an-API-request-in-your-Zaps#limitations-0-0

Hello, I have exactly the same problem. The lead ID is a UUID, but a number (integer) is expected.

I solved it for the moment by searching for the lead title instead of the ID. Here it’s working, but it’s just q quick fix. The lead ID is more unique.

Yes, i have fixed by using an webhook for searching the lead ID. 

Thats the best solution so far i think. 

Best Regards Dennis

Hi friends @DennisDrzosga and @shopstudio,

We're so happy to hear that you managed to solve the issue. Thanks a bunch for sharing your solutions! It'll undoubtedly be a fantastic help to our other amazing Community members who might encounter a similar problem.

If you have any other questions, please don’t hesitate to reach out. We’re always happy to help! 

Hi,

one year later, this is still not solved, but I found a better workaround that I share with you.

Instead of picking the ID field that is incorrectly labeled as “int” (as below):

You need to manually type “ID” as a custom field (as below):

And it works without the hassle of calling pipedrive API manually.

But it’s really disappointing that 1 year later Pipedrive hasn’t fixed this.

Thanks so much for taking the time to share that helpful workaround @Antoine Driard. We really appreciate it!  

I’ve added a note to the bug report for this issue sharing details of the workaround you found. Hopefully it will get resolved soon. We’ll be in touch with any updates on this.

Thanks for everyone’s continued patience here. Please do give Antoine’s workaround a try to see if it solves things for you too!  

Hey folks, I’m very pleased to announce that the bug has been fixed! 

The team have recently released an update which should resolve the issue of not being able to find a lead when searching by the Lead ID, Person ID, Organization ID or Owner ID. To take advantage of this fix you’ll want to ensure you’re running the latest version of the Pipedrive app on Zapier. 

That said, if you’re still experiencing issues when running the latest version please do reach out in the Community or get in touch with Support directly to make us aware. 

In the meantime, happy Zapping!