[Clickup node] Due date update always fails

Describe the problem/error/question

I constantly receive the “correct” response, but due date is always null

What is the error message (if any)?

No error, the result is the original task, still without due date

Please share your workflow

Share the output returned by the last node

I’m getting list of tasks, then applying filter, get a filtered list of tasks - and for them, i’d like to set due date the same as creation date (they are kinda high priority stuff to do)

Information on your n8n setup

  • n8n version: 0.236.2
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): browser, Chrome
  • Operating system: Windows

If to try to set the priority, i can see that priority was set successfully. But no due date, for some reason.

Hey @yavetal,

I have just given this a quick go and it looks to be working if the date is selected in the field so it looks like the issue might be with the date you are sending.

For example if you are using the created date that ClickUp returns whcih would be something like 1691652065654 you would need to format it so your expression might need to look something like {{ DateTime.fromMillis( Number($json.date_created) ) }}.

You can see this in action in the workflow below.

2 Likes

Crazy stuff, Jon!

Taken their API docs says “due_date integer ”

(for some reason, forgot to add the link to the original post)

Thanks a lot, got it to work now

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.