Custom Field - File Attachment
completed
O
Oscar Six
We currently use custom files to organise and title file attachments within a task, especially when viewing tasks in the Table view.
It would be ideal for the API to support uploading files to these Custom Fields so I can create a script to automatically download the text documents our writing team creates via Google Docs, run them through our automation tools and upload them to ClickUp automatically for the rest of the team.
Hope this is enough information,
Oscar Six
Senior Technical Officer, Crimson Sky
Log In
Rafa
This order is marked as complete, but the endpoint they delivered doesn't do what it promises. I confirm the problem that people reported in July: POST /api/v3/workspaces/ {ws} /custom_fields/ {field} /attachments returns HTTP 500 “context deadline exceeded” for any file over 15-20 MB, and the documented attachment limit is 1 GB.
I tested Workspace Business Plus on 25/08, from two different networks (office and a VPS in a datacenter): 15 MB goes up, 20, 30, 60, 120 and 300 MB all fail, always about 3 seconds after the body finishes climbing. That is, it's not a connection timeout on my end, it's the backend of you giving up processing the file.
And there is no outline through the API: the same file goes up normally through the interface and as a task attachment through v2 (I tested up to 600 MB), but the task attachment is rejected as a field value (FIELD_250) and is not uploaded via a signed URL to the field. In practice, for any real media file, especially video, the functionality does not exist via API.
Reopen this or provide visibility of the correction somewhere. Automation that needs to fill in a file field with rendering or video delivery is blocked until that endpoint respects the 1 GB limit.
Marlon Sena
Erra Faye Zabat The v3 endpoint has a ~3s gateway timeout on body transmission - any file taking >3s to upload fails with 500 "context deadline exceeded".
On typical connections even 5MB fails; the documented 1GB would need ~340 MB/s.
Same files work perfectly via v2 and the ClickUp web app.
Ticket filed with traces.
E
Erra Faye Zabat
updated the status to
completed
Hey, everyone!
We recently updated our API so everyone can now upload files to the File Custom Field! To do so, you'll need to run the Create an Attachment API first to generate an attachment/ object ID. You'll then use the generated attachment/ object ID in the Set Custom Field Value endpoint. The API call for this is located here
Since everyone can now upload File Custom Fields via the API, we'll mark this feature request as complete!
Tom Solid
We're heavily using ClickUp via API. That after all those years it's still not possible to upload a file to a custom field via API in the time of AI and MCPs is a reason to move on to any other alternative. No matter which tool I'd switch to, Airtable, Notion etc. they all allow uploading files to specific fields for years already. To see 'Not on the roadmap' is a shocker.
D
Diego Alvarez-Rua
In our company it would be of great help when it comes to digitizing files
S
Sarah Alba
This will be a great feature!
T
Tzipora Mermelstein
It would make everything so much easier! I'm definitely interested...
B
Breindy Frank
This addition would be great!
E
Esty Deutsch
We would love to have this addition.
C
Chany Fischer
I would love to have custom fields file attachments set up; it will make everything easier.
Load More
→