Clickup node populate custom field drop down

Feature Requests
#1

Hi,

I’ve been using the clickup node for a while but there is a convenience thing that I’ve never worked out.
As the title says I have a list in clickup that contains a drop down custom field. Rather than creating the task in the list an d updating the drop down manually I was wondering if it’s possible to do that automatically when creating the task.

When I run a getAll on the task I get the ids of the custom field:

Note: Example with empty drop down field

{
    "id": "3fa52344-724d-4278-93cc-a1679ebf707b",
    "name": "Issue Type",
    "type": "drop_down",
    "type_config": {
        "new_drop_down": true,
        "options": [
            {
                "id": "5b741e49-64b5-48f8-8bd6-ba61a2590d9f",
                "name": "Defect",
                "color": "#e50000",
                "orderindex": 0
            },
            {
                "id": "2899d3d8-0b72-49e1-afa2-2c70c97bb83b",
                "name": "Change",
                "color": "#0231E8",
                "orderindex": 1
            }
        ]
    },
    "date_created": "1631654419877",
    "hide_from_guests": false,
    "required": false
}

If I select a value in clickup for the drop down and do a getAll again then there is an additional attribute “value” which relates to the “orderindex” I believe:

{
    "id": "3fa52344-724d-4278-93cc-a1679ebf707b",
    "name": "Issue Type",
    "type": "drop_down",
    "type_config": {
        "new_drop_down": true,
        "options": [
            {
                "id": "5b741e49-64b5-48f8-8bd6-ba61a2590d9f",
                "name": "Defect",
                "color": "#e50000",
                "orderindex": 0
            },
            {
                "id": "2899d3d8-0b72-49e1-afa2-2c70c97bb83b",
                "name": "Change",
                "color": "#0231E8",
                "orderindex": 1
            }
        ]
    },
    "date_created": "1631654419877",
    "hide_from_guests": false,
    "value": 1,
    "required": false
}

When I then try to set the value in the custom JSON fields on the createTask like this:

{
"id": "3fa52344-724d-4278-93cc-a1679ebf707b",
"value": "1"
}

then I get the following error:

{
"message": "400 - {"err":"Value must be an option index or uuid","ECODE":"FIELD_011"}",
"name": "Error",
"stack": "Error: Request failed with status code 400 at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15) at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:260:11) at IncomingMessage.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21)"
}

So my question is really if that is even possible what I want to do and if so what am I doing wrong?

Cheers,
Rich

Running n8n version:0.166.0

#2

Hi @Richard0815, that wouldn’t be currently possible using the Clickup node I believe. So for now I’ve converted your question into a feature request so you and other users can vote on having this logic implemented.

#3

Thanks for the answer and for converting it to a feature request. Vote +1!

Cheers,
Rich

1 Like
#4

No worries, I wish I had a more useful answer :see_no_evil:

#5

Vote +1, hoping of a way of updating dropdowns custom fields…