: the board_relation texts are null on a "get an item" query

Hi, since the last update of Monday API, we have a problem with the “get an item” query on a node N8N. The “text” field of the board relation is null instead of the name of the item linked. Is it normal ?

An example :
“id”: “board_relation”,
“text”: null,
“type”: “board_relation”,
“value”: “{“changed_at”:“2023-12-18T08:01:45.805Z”,“linkedPulseIds”:[{“linkedPulseId”:5155760508}]}”,
“column”: {
“title”: “Centres de travaux”,
“archived”: false,
“description”: null,
“settings_str”: “{“allowCreateReflectionColumn”:false,“boardIds”:[5155059365]}”

n8n Version : 1.22.6
Database (default: SQLite)
Running via Docker

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
  • n8n version: 1.22.6
  • Database (default: SQLite): SQlite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Linux

Hi @Olivier_MORIN, I am very sorry you’re having trouble.

I do, however, believe this is not an n8n problem but simply comes down to the values you are getting from here.

Some fields in just do not have a text representation from the looks of it, and board_relation appears to be among them. I could see the same behaviour for subitems for example, whereas fields such as project_owner or date would have a text value:

This was using the HTTP Request node to send a raw query rather than using n8n’s node to avoid any n8n-built logic kicking in. Or in other words, this behaviour comes down to rather than n8n.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.