Clickup automation - filtering multiple returned values

[megabunch]

Your Task History ID

IjU3NjUwNTY1MDYzMzA0MzU1MjZkNTUzNzUxMzUi_pc

I am trying to create an automation with Clickup using API, and the JSON is returning multiple tasks with a custom field called "Schedule Date"

There are around 30 tasks in total in the response https://share.cleanshot.com/dYwY9QWH

I want to to able to look at this value for all 30 tasks, and if the date has passed (based on today's date) to change the status of the task.

I've managed to get the API call pulling the task data, and can see the dates in the JSON returned but I can't figure out how to search all 30 tasks without manually creating a router for each one...

Can this be done with iterator with an array or using text formatter?

I can see that I have all of the data I need there, but I don't know how to search the entire Clickup GET query to look for any dates that have passed in all 30 tasks that have been returned.

The field is always called "Custom Fields 5 Date Created" and the only thing that varies is the task number.

For example here's Task 26: https://share.cleanshot.com/GPrfsX5H and here's Task 27: https://share.cleanshot.com/dYwY9QWH

Can anyone help me and is there a way to search the entire result for dates that have already passed?

Thanks a lot!

 

[ArshilAhmad]

Hi @megabunch,

We have added some steps to your workflow. Please try adding the step that will help you change the status of your task in ClickUp as the final step and see if that gives you the desired result.

Pabbly - Online Marketing & Sales Software

Automate your sales and marketing with Pabbly. Unite email marketing, lead capture, WordPress themes, subscription all at one place.

connect.pabbly.com

 

[megabunch]

Hi @ArshilAhmad thanks so much for taking a look at this!

I've added the final step to update the tasks as requested - will this process all of them in the array using iterator?

Also I'm not quite sure the filter logic is set up as we intended as it is using different fields: https://share.cleanshot.com/rHntC674

To confirm, we want to only update tasks where the custom field "schedule date" is in the past (compared with today's date).

I think it's schedule date "value" that we need to use instead of date created: https://share.cleanshot.com/J6d91tfL and that's the one that needs to be compared with today's date.

Here is an example task: https://share.cleanshot.com/83DWrSVC

To confirm what we want to do is:

1. Get all tasks from Clickup for a certain list using API with status "scheduled"
2. Review "schedule date" custom field for every task returned and see if it's in the past (i.e. schedule date is greater than today's date)
3. If that's true - update each task status to "complete" via task id.

Thanks a lot for your fast response and help... let me know if you have any questions!

 

[megabunch]

We tried editing the field ourselves @ArshilAhmad but it seems it's not showing in the "Custom Fields" Iterator for some reason.

We can see it in the returned JSON from Clickup here: https://share.cleanshot.com/zMnwN9PQ

But we cannot see it inside the Iterators you have created: https://share.cleanshot.com/xnvlBsXL

Thanks a lot!

 

[ArshilAhmad]

Please share a larger screenshot showing in which action step you are getting the 'Value' field.

 

[megabunch]

Hi @ArshilAhmad we can see the Schedule Date "value" field returned inside the API call in Step 3 inside the Tasks array.

CleanShot 2024-06-27 at 11.44.40

Screenshot

share.cleanshot.com

CleanShot 2024-06-27 at 11.45.47

Screenshot

share.cleanshot.com

We can also see it inside Step 4 in the Tasks iterator inside "custom fields" here: https://share.cleanshot.com/pgdsMdM6

However it doesn't show anywhere in Step 5 (the 2nd "custom fields" iterator you added: https://share.cleanshot.com/Yz6zkytY

This means we cannot select it as a filter inside Step 6.

Let me know if you need any more details.... thanks very much.

 

[Supreme]

Please wait, we are checking on it.

 

[ArshilAhmad]

Thank you for sharing this information. Please allow us some time to look into this concern. We will get back to you with an update soon.