Skip to main content

Cannot get dropdown fields in Pipedrive to be recognised as custom fields in zapper 

everything i try does not work, I am using a dropdown field, when i test text custom fields they are fine. 

{{xxxxxxxxxx__custom_fields__SMS_Consent__SMS_Consent_value}}

tired lowercase 
extra spaces between values 
 

any ideas please

 



 

This post has been edited by a moderator to remove Zap ID number. Please remember that this is a public forum and avoid sharing Zap IDs or Zap links.

Hi and welcome to the Community ​@DI_will! 😁

It looks like you’ve got some underscores where there should just be spaces in the field names.

e56584833addc19c713fe379aa402ec6.png

16f1f6c0c5214b1757dfaffbbc57eba9.png
 

Can you try using {{nodeid__custom_fields__SMS Consent__SMS Consent value}} instead? Be sure to replace nodeid with the ID of the Pipedrive step

Let me know how it goes!


​Hey there ​@DI_will, just checking in! Did replacing the underscores with spaces in the field names do the trick?

I’d be happy to assist further if you’re still stuck at all, want to make sure you’re all set 🙂