monday.com api column value malformed
Fix monday.com's malformed column values: each column type wants its value in a specific JSON shape, and the API rejects anything else. Use when column updates fail as malformed, when a value works for one column type but not another, or when previously working updates break. Not for authentication errors, board access errors, or rate limits.
TL;DR
Monday.com columns are typed, and the API validates the value's shape against the column type: a date column wants a date object, a status column wants an index or label object, a numbers column wants a plain number. 'Malformed' means the shape is wrong, not the data. Read the column's type, format the value to match, and retry.
The query
monday.com api column value malformedUse this when
- Column updates fail as malformed
- A value works for one column type but not another
- Previously working updates start failing
Not for
- Monday.com authentication errors
- Board access or permission errors
- Monday.com rate limits
Steps
1. Read the column's type and settings
Query the board's columns and note each target column's type and settings. Status columns have label indexes; date columns have formats; dropdowns have ids. The type dictates the shape.
Expected output: the column type and settings for every column you write.
2. Format the value to the type's shape
Build the value exactly as the type expects: status as a label or index object, date as a date string object, numbers as raw numbers, text as a plain string. Test one column at a time until each returns success.
Expected output: a successful update for each column type you use.
3. Stop sending display strings
The board shows 'Working on it'; the API may want the label's index. Display values and API values differ per type. Always send the API shape, never what the UI renders.
Expected output: no UI display strings in API payloads.
4. Re-check after board changes
When someone changes a column's type or relabels statuses, the expected shape changes with it. Re-read the column definitions on a schedule instead of assuming they never change.
Expected output: column definitions refreshed and payloads still valid.
Variant phrasings
monday.com changecolumnvalue error
Steps 1 and 2: type first, then the exact shape.
monday.com api status column update
Step 3's display-vs-API distinction; status is the worst offender.
Why it happens
Monday.com's UI is forgiving: it lets you type dates and pick statuses however you like, then normalizes. The API is not forgiving: it validates the JSON shape strictly. Integrations built by copying what the UI shows send display values, and the API rejects them as malformed because the shape, not the content, is wrong.
Edge cases
- Column ids (not titles) are the stable reference. Titles get renamed.
- Some columns are read-only through the API (formula, auto-number). Check before writing.
- Batch mutations validate each item independently. One malformed item doesn't have to kill the batch; check partial results.
Provenance
Resolved from the public thread: https://vectle.com/posts/pstJno7ZXFfa82OGsSnyhYuA
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.