Hey everyone,
I just wanted to alert the community about a serious issue I encountered with the “Edit a Task with Custom Fields” module in Make.com for ClickUp.
The Issue
If you leave a Location-type custom field empty in the module, instead of being ignored, Make actively clears the existing value in ClickUp.
- Normally, when a custom field is left unset, it should remain unchanged.
- However, for Location-type fields, the module explicitly sets them as empty, causing unintended data loss.
- I discovered this when updating a completely different custom field (a dropdown), and suddenly, existing Location-type field values disappeared from my tasks. This behavior does not affect other custom field types, making it particularly dangerous since it’s not immediately obvious.
Why This Matters
- If you aren’t aware of this, you could be losing critical data without realizing it.
- Even if you do notice missing data, the cause might not be obvious.
- Until this is fixed, I strongly recommend double-checking your workflows if they involve updating a task in a List where Location-type fields exist.
What’s Next?
I’ve already reported this to Make support, but I wanted to warn everyone in case you’re experiencing the same issue.
- This post might increase support requests, but I believe it’s more important to help people recognize the issue before they lose data.
- If you’ve encountered the same problem, please comment below to help Make prioritize a fix.
I’ll update this post if I receive any official response. Stay safe with your data! 
