Dropdown custom field in ClickUp is not transferring correctly to Google Sheets

Hi @Luthfi 

Good question.

For context, please post detailed screenshots with how your Zap steps are outlined and configured, thanks.

Hey there @Luthfi, hope you had a great week! Did you still need any assistance with this? We’d love to help you out if you do, please be sure to come back with some screenshots of your Zap setup so we can take a closer look. 😄

I’m having the same issue. I have dropdown values but it will only show numerical values (0,1,2,etc) based on the ordered list.

Hey there, @megan-mauto! Thanks for reaching out. 

Can you share some screenshots of the setup for this zap step with any personal details removed? That should help us troubleshoot with you.

Thanks!

I too am using Zapier to pull Custom Field data from a Dropdown field.

I need the term “Kosher Certification” to be used in other Zaps, but the Value that is easily pulled from ClickUp is “1” (which only refers to the order index associated with Kosher Certification). How can I get the term “Kosher Certification” without a complicated addition of steps like storage or tables?

Here is a clear view on how Zapier is pulling ClickUp data:

Hi there @philipio,

Unfortunately, I couldn’t figure out the cause of why this is happening with the custom fields on your ClickUp Zap. I recommend reaching out to our Support team so that they can take a closer look at the Zap and its logs to determine the cause of the issue.

You can reach our Support team here: https://zapier.com/app/get-help

Thank you for your understanding.

Having the same problem. The issue is that ClickUp is providing the INDEX of the dropdown value and not the LABEL of the Value. There is an array of all the LABELs provided by ClickUp. But there’s no field in Zapier to map the LABEL value. So it’s currently useless to try to send Dropdown values to Zapier. 

On another note, I wouldn’t have to do what I’m trying to do if ClickUp Formula custom fields would work with TEXT fields!!! 

Hi friends,

I did some digging into this, and it seems like the names of the custom fields are coming through but not their values. I have added you all as another interested members to the feature request. That does a few things:

• Bring this to the attention of the integration developers
• Help track interest in this feature being implemented
• Allows us to notify you via email if this feature becomes available in the future

While I don't have an ETA on when this feature might be implemented, we will notify you via email if it is!

Hopefully, this helps.

Adding my hat to the ring as someone affected by the inability to map the label of a dropdown in ClickUp. We have a lot of dropdown fields in ClickUp, so that severely limits our Zapier use cases there. Would be great to see this implemented at some point. 

Can you add me to the list please - I am also trying to create a zap that needs the value / label of custom dropdowns used and displayed…
Beryl

Thanks for reaching out here, @berylp. We can’t provide an ETA on when this will be resolved but I’ve added you to the list so we’ll definitely be in touch as soon as a fix is shipped. 

@SamB please can you add me to whatever I need to be added to, to get notified on progress on this issue?

Hi @Colin_C_C,

I have added you to the bug as another affected member. We will keep you in the loop via email once the bug has been fixed.

I appreciate your patience and understanding

I am having the same issue. Is this fixed? 

Hi @Matson T,

Unfortunately, the bug report is still open. I have added you to the bug report as another affected member. While we don’t have an exact ETA for the bug’s fix. We will keep you updated via email once the bug has been fixed.

Additionally, you can also reach out to ClickUp regarding this bug since they are the ones who owns and maintains their integration with Zapier.

I appreciate your patience and understanding.

So you are saying this bug is on the Click-Up side? I sent them a message. Do you know the Click UP bug ID? 

Hi @Matson T,

That’s correct. The Bug ID should be #132.

Hopefully, this helps!

Oh my ! 😱
I can’t believe we’re one year ahead and this bug’s still not fixed !
I spent days to design a new Clickup process and because of this bug nothing’s working. I can’t believe it.

I’m really sorry to hear how much trouble this has caused, ​@FCE. I completely understand how frustrating it must be to put so much effort into designing your ClickUp process only to be blocked by this long-standing issue.

While we can’t provide an estimate as to when the developers of the ClickUp app will get it sorted, you’ve been added to the list of folks affected by this so you’ll definitely get an email notification once it’s resolved. 

In the meantime, I just came across a potential workaround of using a lookup table in your Zap. In the lookup table, you would enter the names of all of the possible options of the dropdown field and their corresponding orderindex number. You can see an example of the list of the names and corresponding order index values in the screenshot shared by philipio earlier in this thread:

If you take a look at a recent Zap run for your own Zap that should show the names and orderindex values you’d need to use. Then you can use the output from the lookup table to provide the name of the option that’s been selected. If you’ve not used lookup tables in Zaps before you can find out more about how to set them up here: Create lookup tables in Zaps.

Hope that workaround helps for now. Please do reach out if you run into any trouble setting it up—we’d be happy to lend a hand if you get stuck! 🙂