Nick Potok: this is exciting. My understanding is that you aren’t able to pull data from custom fields of trigger tasks to use in future steps of a zap. Is there a different feature request for that? Thanks!

Nick Potok: that's great news but it's impossible to use the content saved into the custom field. Only the custom field names comma separated (capture)

Yair Adi: Yes, I am experiencing issues with this as well. I have a ticket into their technical support to investigate and find solutions.

Nick Potok: Hi Nick,

That sounds great but I see nothing new in the ClickUp Zapier module :/ so when / where will it show up ?

Thanks - looking forward to using it!

Nick Potok: Yeah, not being able to reference existing custom field data is very limiting here. If there is another request for this I will go upvote that.

Yair Adi: I can't use my custom fields either, the fields now show up as options, but unfortunately the contents of the field shows up as gibberish

Shena Hesselbein: Seems so, but that's what I thought this was going to let us do. In my workflow there's not much point in being able to see the custom fields but not access or use the data in them for Zaps. Fingers crossed this aspect of the feature will be implemented before too long.

Sophia K: Exactly. It’s useful for bringing data into ClickUp but useless for ClickUp to communicate with any other platform.

Nick Potok: Thank you so much for this. 💛 Seriously. Thank you!

Nick Potok: I am also experiencing the issue mentioned below. Thanks though!!!

Nick Potok: No, still no support.

Nick Potok: Are you getting feedback that some custom fields aren't displaying in Zapier, in my case phone no.

Nick Potok: I'm having the same problem as everyone else -- all of the contents of the custom fields come over in one field separated by a comma, dates come over as a UTC timestamp with 3 extra zeroes, and drop-down menu items come over as their placement in the list (therefore, the 4th option on the dropdown would come across as the 5, or the first option would come across as 0). So it comes out looking like a string of numbers and letters, as in the example below.

Example: 1641027600000,US,1500,TEST@EMAIL.COM,0,6000,PARTNER NAME,1643706000000,2,1646125200000,1648800000000,4,1651392000000

Yair Adi: is there any news about this issue?

Ernesto Argüelles: The answers from CU support by email is this: it is not an issue. That array is the expected behavior.

You must vote the other request asking for better integration with Zapier

Yair Adi: Not impossible, just not ideal. A code step and a little bit of JavaScript and you can sort out those values pretty easily :)

Todd Harper: What is "not impossible" ? I know to code and use this string of custom fields. But in Zapier is useless.

Nick Potok: Great, but it is simply UNUSABLE!

All the custom fields are put together in one line and your Text Formatter does not work.

It seems like you just released the feature for the sake of releasing it.

Thank you all for discussing what you’ve encountered and bringing this to our attention.

I’m looking further into this to update our documentation and look into solutions for any bugs.

I’ll send a message as soon as theres an update!

Yair Adi: Where is the other request? I didn't find it.

Todd Harper: Can you share the js code? I'm happy to implement but I'm a bit of a js newb.

Thanks, Nick Potok -- I want to make sure this request is being taken seriously. Is there a proper feature request for this? I've been back and forth with Support and no one seems to have a solution. Zapier suggested I hire a dev.

Shanda Packard: So, it's going to vary quite a bit based on the specific custom fields you're using, but let's say your fields/columns are named "CF1", "CF2", and "CF3" (which, more realistically for people in general, are things like "Email Address" and "Phone Number"...for you these are things like "Churn Date", "Country", "Deposit", etc.)

Create a Code by Zapier step and select JavaScript.

As Input Data, use "Task Custom Fields Name" and "Task Custom Fields Value" and save them as "CustomFieldKeys" and CustomFieldValues" respectively.

Then copy/paste everything between the slashes (//) below (obviously, replacing "CF1", "customField1", etc. with your actual fields and adding more / removing as necessary:

//

let customFieldKeys = inputData.CustomFieldKeys.split(",");

let customFieldValues = inputData.CustomFieldValues.split(",");

let customField1 = "";

let customField2 = "";

let customField3 = "";

let customField1Position = customfieldKeys.indexOf("CF1");

customField1 = customFieldValues.splice(customField1Position, 1).join(" ");

customFieldKeys.splice(customField1Position, 1);

let customField2Position = customfieldKeys.indexOf("CF2");

customField2 = customFieldValues.splice(customField2Position, 2).join(" ");

customFieldKeys.splice(customField2Position, 1);

let customField3Position = customfieldKeys.indexOf("CF3");

customField3 = customFieldValues.splice(customField3Position, 1).join(" ");

customFieldKeys.splice(customField3Position, 1);

output = [{customField1, customField2, customField3}]

//

NOTE: This solution assumes that each of your fields is completely filled out prior to triggering your Zap and that none of your fields will ever include commas...if either scenario above is true, we have to do some additional fancy work which is different on a case by case basis and you can certainly hire me to do it for you.

Todd Harper: Thank you so much! The ClickUp support team gave me a JS to use but yours looks better, so I'll give this a try. Unfortunately, my biggest challenge right now is that all fields are not entered at the time of the zap. Not sure if you can drop your email here but if you can, please do!

Shanda Packard: Definitely! Feel free to email me at todd@weddingtechbff.com :) Getting around not all fields being entered at the time the Zap runs can be pretty tricky TBH...but we can definitely take a peek and see if there's a solution!

Also, for anybody reading, here's a better version of the code above, which utilizes a function for the repeated lines of code, but does exactly the same thing:

let customFieldKeys = inputData.CustomFieldKeys.split(",");

let customFieldValues = inputData.CustomFieldValues.split(",");

let customField1 = "";

let customField2 = "";

let customField3 = "";

let customFieldPosition1;

let customFieldPosition2;

let customFieldPosition3;

function matchKeyValue(key, varValue, varPosition) {

varPosition = customFieldKeys.indexOf(key);

varValue = customFieldValues.splice(varPosition, 1).join(" ");

customFieldKeys.splice(varPosition, 1);

return varValue;

};

customField1 = matchKeyValue("CF1", customField1, customFieldPosition1);

customField2 = matchKeyValue("CF2", customField2, customFieldPosition2);

customField3 = matchKeyValue("CF3", customField3, customFieldPosition3);

output = [{customField1, customField2, customField3}];

Todd Harper: hello can I afford to send you an email with the problem similar to what you explained? unfortunately i am completely js fasting and i have about a 15 custom field that i can't use with zapier. and unfortunately you are the only one who has given a plausible solution.

Thanks even just for the answer