Clickup Start and Due dates being overwritten even though blank

Questions
1

:bullseye: What is your goal?

When a customer fills out a form it updates my clickup task to booked in ( they complete the form their booking is made. It makes no changes to the start date or due date

:thinking: What is the problem & what have you tried?

I currently have a webhook that when someone submits a form from the forms app it updates my clickup task status from waiting on form to booked in am currently using the edit a task function to do so.

Starts with a webhook which has the clickup job task attached to the webhook in the form itself ( each form has a unique task id hidden field which is sent from clickup as required and the webhook includes this parameter. Then edit the task uses the clickup task id from webhook to change details on the task and the only thing i have changed is the status but because the others are blank i think it actually makes them blank properly.

If i have a date lets say start date July 4th at 9:00am, end date July 4th 10:00am and send the form it all works they fill it out it changes status to be booked in but then at the same time that status is changed it also sets the start date and due date to July 4th (no time just start and due on that date)

:clipboard: Error messages or input/output bundles

no errors as it functions correctly just the booking and due time is changed when i dont want it to

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

Screenshot 2026-07-03 153929.png
Screenshot 2026-07-03 153929.png757×915 50.5 KB

4

The reason is because it is updating the task in a way where there is no due date time. So it is doing what it should have done.

Try with mapping on in the above due date area and putting in the due date form a list a task module or something. It might work.

Just in case it doesn’t work, a quick fix would be to have an AI agent to take action and create due date time from task, which could potentially work.

Haven’t tried any of these, but these could help. Let me know if it works.

5

I ended up solving it by changing from edit task to simply edit task with custom fields. When using this option it has empty available as a selection in the due date and start date fields so it works perfect using it this way whereas using edit a task it doesn’t give you this option weird but it works at least!

6

This is not the correct module behavior at all and should be reported to Make as a bug and fixed.

I just reproduced it locally. The issue happens when the task has a start/due date time set and is caused by the module defaults of start/due date time being set to no and being sent in the call for some reason, essentially deleting the set times.

The Edit a Task with Custom Fields module has options to leave the times as empty where the Edit a Task module doesn’t. So yeah, switching to that one will avoid the issue for the moment.