Hi everyone!
I’ve been experimenting with the change_multiple_column_values mutation to update the Files Column with external links (like Google Drive). While the documentation currently lists this as unsupported for this specific mutation, I found that it actually works—with one major catch regarding fileId.
The Method
I am using the following mutation:
mutation updateFileLink ($columnValues: JSON!) {
change_multiple_column_values(
item_id: "my_item_id",
board_id: "my_board_id",
column_values: $columnValues
) {
id
}
}
With this JSON as columnValues variable:
{
"file_column_id": {
"files": [
{
"fileId": "file1_id",
"fileType": "GOOGLE_DRIVE",
"linkToFile": "https://drive.google.com/...",
"name": "file1.pdf"
}
]
}
}
The Issue: The fileId Dependency
The mutation is successful and the link appears perfectly in the WebUI. However, I’ve run into a significant backend issue:
-
Omitting
fileId: If I don't provide afileIdin the mutation, the link still shows up in the UI. But, any subsequent API query to fetch that column's value crashes (it returns anullforfileIdwhich seems to break the internal GraphQL resolver). -
Reusing
fileId: If I manually provide a value forfileId(taken from already existing file) the query works. I’ve tested reusing the samefileIdacross multiple items and it "works," but this feels like just asking for trouble.
My Questions
Since the official add_file_to_column mutation is geared toward file uploads (assets) rather than external links, I’m wondering about three things:
-
Roadmap: Are there plans to officially support
FileLinkValuein thechange_multiple_column_valuesmutation? -
Safety: Is it "safe" (even if unsupported) to reuse a
fileIdfrom file already existing on the service, or will this cause orphaned metadata/collisions in the long run? -
Alternatives: Has anyone found a way to let the monday.com backend generate the
fileIdfor external links via API without it crashing the query?