Allows you to create a new board. After the mutation runs you can query back all the board data as shown in the Querying boards section.

To see all the available template ID's go to monday.labs and activate the "Developer mode" feature. You will then be able to see the template ID's in the create board from template screen.

Below are the list of options to mutate a board. After the mutation runs you can query back all the board data as shown in the Querying boards section.

Allows you to add subscribers to a board. You can define if users will be added as regular subscribers or as owners of the board.

Allows you to delete subscribers from a board.

The duplicate board mutation duplicates a board with all of its items and groups, to a specific workspace/folder of your choice. The query will return data of the board created as well as whether the process is synchronous or asynchronous. Please note that an asynchronous duplication process may take some time to complete, therefore the initial returned data might be partial.

Allows to add a new column to the different board through the API. After the mutation runs you can query back the column data as shown in the Querying columns section.

The data of each item is stored in columns. The change simple column value mutation allows you to change the value of a column in a specific item (row), with a string.

Each column has a certain type, and different column types expect a different set of parameters to update their values.
When sending data to a particular column, use a string. To check how to send the data for each column please see changing simple column values section

You can also use the simple values in create_item, create_sub_item and change_multiple_column_values mutations.
You can combine simple and regular values in your mutation. This is useful when you want to update columns that do not support simple column values. .

After the mutation runs you can query the board data, as shown in the Querying columns section.

The data of each item is stored in columns. The change column value mutation allows you to change the value of a column in a specific item (row).

Each column has a certain type, and different column types expect a different set of parameters to update their values. When sending data to a particular column, use a JSON-formatted string (if you’re using Javascript, you can use JSON.stringify() to convert a JSON object into a string). To check how to send the data for each column please see changing column values section.

After the mutation runs you can query back the column data as shown in the Querying columns section.

This mutation allows you to update multiple columns values of a specific Item (row).

Each column has a certain type, and different column types expect a different set of parameters to update their values. When sending data in the column_values argument, use a string.

The column_values argument is built in the following form (example with text and status columns):

Code example

{\"text\": \"New text\", \"status\": {\"label\": \"Done\"}}

NOTE: You can use also simple values in this mutation, combined with regular values, or just simple values. Example (where status is set with simple value) :

Code example

{\"text\": \"New text\", \"status\": \"Done\"}

After the mutation runs you can query back all the columns data as shown in the Querying columns section.

This mutation allows you to update the title of an existing column.

After the mutation runs you can query back all the columns data as shown in the Querying columns section.

The duplicate group mutation duplicates a group with all of its items. After the mutation runs you can query back all the group data as shown in the Querying groups section.

The create group mutation creates a new empty group. After the mutation runs you can query back all the group data as shown in the Querying groups section.

The archive group mutation archives a group with all of its items. After the mutation runs you can query back all the group data as shown in the Querying groups section.

The delete group mutation deletes a group with all of its items. After the mutation runs you can query back all the group data as shown in the Querying groups section.

You can create a new item in the different boards through the API with the create item mutation.

The data of each item is stored in the board’s columns, each of which holds a particular piece of information. Each column has a certain type, and different column types expect a different set of parameters to update their values. When sending data to a particular column, use a JSON-formatted string (if you’re using Javascript, you can use JSON.stringify() to convert a JSON object into a string).

NOTE: You can use also simple values in this mutation, combined with regular values, or just simple values.
To check how to send the data for each column please see changing column values section and changing simple column values section.

After the mutation runs you can query back the item data as shown in the Querying items section.

You can create a new subitem for any parent item through the API with the create subitem mutation.

Subitems are technically created under a different board, which is NOT the same board as parent item's board. You can query the identifier of this board through the regular Board resolver of the subitem. Using this board ID and subitem ID you can apply any actions to the subitem as to a regular item, f.e. archive it, delete, change column_values, etc.

NOTE: For creating subitems via the API, the board should already have subitems column or at least one subitem created, otherwise you will receive an error.

After the mutation runs you can query back all the subitem data the same as for a regular item as shown in the Querying items section.

This mutation allows one to clear all updates on a specific item, including replies and likes. After the mutation runs you can query back the item data as shown in the Querying items section.

This mutation allows one to move a item between groups in the same board. After the mutation runs you can query back the item data as shown in the Querying items section.

This mutation allows one to archive a single item. After the mutation runs you can query back the item data as shown in the Querying items section.

This mutation allows one to delete a single item. After the mutation runs you can query back the remaining items data as shown in the Querying items section.

This mutation allows one to duplicate a single item. After the mutation runs you can query back the item data as shown in the Querying items section.

The create update mutation allows one to add an update to a item. After the mutation runs you can query back the update data as shown in the Querying updates section.

The delete update mutation allows one to delete an update of an item. After the mutation runs you can query back the remaining updates data as shown in the Querying updates section.

Notifications are sent in the platform in response to various triggers such as due dates, updates, and more. By default, each notification within the platform will also be sent out as an email to the recipient (this can be customized in the user’s profile settings).

The create notification mutation allows to trigger a notification within the platform (will also send out an email if the recipient's email preferences allow). Keep in mind that notifications are async and you will not be able to query their ID's back after sending then out.

The tags mutation allows you to create new tags or receive their data if they already exist. Private boards require separate tags so if you wish to use your tags in a private board use the 'board_id' argument. No need to send this argument for public boards.

Add a file to an existing update. The file will be appended to the bottom of the update.

Add a file to a file column value.

The mutation allows you to create a new webhook. After the mutation runs, a webhook subscription will be created based on a specific event. Every time the event happens on your board, the webhook will send data about the event to the subscribed URL.

The URL will have to pass a verification test, where we will send a json POST body request containing a challenge field. We expect you to return the token as a challenge field on your response json body to that request.

The webhooks that you can subscribe to via the API are:

* Some of the events also accept the "config" field. This field is used to pass configuration for the event. Currently, the only event that requires the config field is 'change_specific_column_value'. To use this event, pass a JSON object that contains the column ID you wish to subscribe to.

For example: {"columnId": "status1"}

The delete webhook mutation deletes a webhook. After the mutation runs it will no longer report events to the URL given.

Allows you to create a new workspace. After the mutation runs you can create boards in it as shown in the Creating boards section.