How to create subitem on monday.com

Feature Requests
1

The idea is:

To be able to create subitems in Monday.com for an existing item using the n8n Monday.com node. Currently, there’s a built-in UI in n8n for creating regular items, but subitem creation doesn’t seem to be directly supported.

My use case:

I want to automatically add subitems under existing Monday.com items based on incoming data. This is useful for organizing nested tasks, email threads, or detailed line items under a parent item in Monday.com.

I think it would be beneficial to add this because:

Creating subitems is a core feature of Monday.com that helps structure information hierarchically. Supporting this directly in the n8n node would make Monday.com automations more complete and reduce the need for manual workarounds like custom GraphQL.

2

this would be nice. The http node works for now:
Send Body - Using JSON
Replace xxxxxxx with parent IDand Name of Submitem
{
“query”: “mutation ($parentItemId: ID!, $itemName: String!, $columnValues: JSON) { create_subitem (parent_item_id: $parentItemId, item_name: $itemName, column_values: $columnValues) { id name created_at } }”,
“variables”: {
“parentItemId”: xxxxxxx,
“itemName”: “New Subitem”,
“columnValues”: “{}”
}
}

4 Likes
3

God bless you so so so so so so much for this

4

Hi, can i ask. do you have any idea how to upload binary file to monday.com column? thanks

5

This works for me — this uploads to file column.

HTTP Node

Method: POST
URL: https://api.monday.com/v2/file
Send BOdy - Enabled
Body Content Type: Form-Data

Body Parameters
Parameter Type: Form Data
Name: query
Value: 
mutation add_file($file: File!) { add_file_to_column (item_id: {{ ITEMID of the Monday Row Item }}, column_id: "COLUMN ID OF the Monday FILE Column", file: $file) { id } }

Parameter Type: n8n Binary File
Name: variables[file]
Input Data Field Name: NAME OF YOUR BINARY FILE (not name of the file)

you can loop this to add mulple files in the same row

1 Like
6

appreciate so much

7

Hello @RiL, Thank you so much for this but I have encountered an issue with my columnValues because I want to pass a data from a form trigger node then it will create a subitem depending on what is the form data. I have a problem with my columnValues the error says: JSON parameter needs to be valid JSON [item 0]

8

can you show the workflow for this part? you can copy and paste into response so that the workflow is with nodes is shown like my last post. Its hard to tell whats going on with just description.

9
10

Hello @RiL here is the workflow I have been working on.

11

Try this

{
  "query": "mutation ($parentItemId: ID!, $itemName: String!, $columnValues: JSON!) { 
    create_subitem (
      parent_item_id: $parentItemId, 
      item_name: $itemName, 
      column_values: $columnValues
    ) { 
      id 
      name 
      created_at 
    } 
  }",
  "variables": {
    "parentItemId": {{ $json.parentItemId }},
    "itemName": "{{ $json.itemName }}",
    "columnValues": "{\"long_text_mksaegan\": \"{{ $json.columnValues.long_text_mksaegan }}\", \"long_text_mksamr47\": \"{{ $json.columnValues.long_text_mksamr47 }}\", \"status_1\": \"{{ $json.columnValues.status_1 }}\", \"date_1\": {\"date\": \"{{ $json.columnValues.date_1 }}\"}, \"numbers_1\": {{ $json.columnValues.numbers_1 }}}"
  }
}
  • You’re wrapping parentItemId in quotes, making it a string.
  • You’re using JSON.stringify() inside an expression that’s already wrapped in quotes.
  • trying to access $json['Problem and Concerns'] but those fields don’t exist at the root level - they’re nested inside $json.columnValues.
1 Like
12

Hi @RiL thank you so much for the replies, unfortunately there’s still something missing because I have this output:
[
{
“data”: null,
“errors”: [
{
“message”: “Variable $columnValues of type JSON! was provided invalid value”,
“locations”: [
{
“line”: 1,
“column”: 50
}
],
“path”: ,
“extensions”: {
“value”: “{“long_text_mksaegan”: “TestP”, “long_text_mksamr47”: "TestJD}”,
“problems”: [
{
“path”: ,
“explanation”: “Syntax error in JSON input”
}
],
“service”: “monolith”
}
}
],
“extensions”: {
“request_id”: “7bbb1837-f211-9974-a0fa-b98922c62649”
}
}
]

13

I somehow can create a subitem but without the columnValues data.

14

Assuming you did you modify the JSON body provided? Might be missing a } somewhere or maybe your Monday output has a special character that breaks the JSON string.
Since its does create the subitem, then you know where the issue is.
I would test each column by column, first by manually typing in the value rather than referencing it, then reference the previous node, you will see where it errors out.

1 Like
15

image
image1821×773 140 KB

16

It’s good on the Result but every time I run it. This is the output:
JSON parameter needs to be valid JSON

17

This one works but without the columnValues:

image
image1812×759 113 KB

18

dont do stringify, the pasted example does not have it.
Like I said before do one column at a time….
I asume long_text_mksaegan is the column id of a column that will accept string of text such as “Problem”. Then test it without any $json reference. If it works then do each column. I wont be repeating this.

“columnValues”: "{\"long_text_mksaegan\":\"Problem\"}"
1 Like
19

I got it now @RiL thank you so much for your help! Can we connect in LinkedIn?