Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Updating required props in ClickUp components

See original GitHub issue

It appears we are flagging “workspace” and “space” props as optional in the Create Task action for ClickUp, but if those are not provided, then async options fails for the “folder” prop, which is required.

We should confirm which fields are required for all ClickUp components, and update accordingly.

Reported by a user here: https://pipedream-users.slack.com/archives/C01E5KCTR16/p1661955460385759

Issue Analytics

State:
Created a year ago
Comments:6

Top GitHub Comments

1reaction

andrewjschuangcommented, Oct 7, 2022

when i insert values manually

Hi @Hassan-Abbas-SQA can you try inserting the ID of the Custom Field?

1reaction

r-olearycommented, Sep 24, 2022

Additionally, it would be good to verify which fields you actually need for a given call. I am trying the “update_task_custom_field” action, and for some reason CU wants me to pick a workspace, space, folder, and list before I can set the task ID. BUT, the APi call from CU only requires task_id and field_id, so why do I even have to select all those other things? Just let me enter task and field ID.

Thanks.