What are the differences between custom_fields_original and custom_fields in the ClickUp App

When I use the ClickUp “List all tasks” action, there are two structures in my my output bundle : one collection “custom_fields” and one array “custom_fields_original”. The collection contains most usefull shortcup (item that I can drag and drop to destination fields) BUT it is not exhaustive : it contains only a small shortlist of my CU Customs fields. I have no idea where is that shortlist decided (why one field and not another). I tried reordering Customs fields on the CU side, but with effect on the Make side). The custom_fields_original arrays looks like the way to go, but it requires much more function writing to get to the same data.
Would someone know how to influence the content of the custom_fields collection?

Hi @pvk,

Welcome to the community! Can you show us what the output bundle of the List all Tasks module looks like? I am not familiar with what you receive.

Please, follow these steps when asking a question, and you’ll be more likely to get a helpful answer:

:writing_hand: Give us a detailed explanation of what you’re trying to achieve

:footprints: Tell us about any steps you’ve tried so far

:camera_flash: Include screenshots of:

  • your scenario flow and setup (functions, mappings, variables, etc.)

  • module configurations and outputs

  • any error messages you are getting

:card_file_box: Share the blueprint of the scenario you are asking a question about. (this does not contain any connection or personal information)

Certified Make Expert and Partner
Book a consult with me