Learn how to read, filter, update, and clear the deprecated team column using the platform API
The team column has been deprecated and replaced by the people column. The people column supports assigning both users and teams to an item. New boards use the people column by default.
If you are building a new integration, use the people column instead.
The team column stores a reference to a single monday.com team assigned to an item. It uses the team column type internally and returns values as TeamValue in the GraphQL schema.
Via the API, the team column supports read, filter, create, update, and clear operations.
| Column Type | Implementation Type | Supported Operations |
|---|---|---|
team | TeamValue |
|
The team column does not support
change_simple_column_value. Usechange_multiple_column_valuesfor all updates and clears.
Queries
Team columns can be queried through the column_values field on items using an inline fragment on TeamValue.
query {
items(ids: [1234567890, 9876543210]) {
name
column_values {
... on TeamValue {
id
team_id
text
value
updated_at
}
}
}
}const query = `
query ($itemIds: [ID!]) {
items(ids: $itemIds) {
name
column_values {
... on TeamValue {
id
team_id
text
value
updated_at
}
}
}
}
`;
const variables = { itemIds: [1234567890, 9876543210] };
const response = await mondayApiClient.request(query, variables);Fields
You can use the following fields to specify what information your TeamValue implementation will return.
| Field | Description |
|---|---|
column Column! | The column the value belongs to. |
id ID! | The column's unique identifier. |
team_id Int | The ID of the assigned team. Returns null if no team is assigned. |
text String | The assigned team's name as text. Returns null if no team is assigned. |
type ColumnType! | The column's type (team). |
updated_at Date | The date when the column value was last updated. Returns null if the column was set during item creation and never subsequently updated. |
value JSON | The column's raw value as a JSON string. See value structure below. |
Value structure
The value field returns a JSON string. Its structure depends on how the value was set:
When set during item creation:
{
"team_id": 51166
}After being updated via change_multiple_column_values:
{
"team_id": 51166,
"changed_at": "2026-03-21T10:52:28.626Z"
}| Key | Type | Description |
|---|---|---|
team_id | number | The unique ID of the assigned team. |
changed_at | string | ISO 8601 timestamp of when the value was last changed. Only present after a mutation update. |
Example response
{
"data": {
"items": [
{
"name": "Task A",
"column_values": [
{
"id": "team",
"team_id": 51166,
"text": "Engineering",
"value": "{\"team_id\":51166,\"changed_at\":\"2026-03-21T10:52:28.626Z\"}",
"updated_at": "2026-03-21T10:52:28+00:00"
}
]
}
]
}
}You can find a team's ID by using the Teams queries, checking which teams a user belongs to via the User object, or opening the team's page in monday.com and copying the number at the end of the URL.
Filter
You can filter items by the team column using the items_page object. Filters match against team IDs.
| Operator | Compare Value | Description |
|---|---|---|
any_of | An array of team IDs (e.g., [51166]) | Returns items assigned to any of the specified teams. |
not_any_of | An array of team IDs (e.g., [51166]) | Excludes items assigned to any of the specified teams. |
is_empty | [] | Returns items with no team assigned. |
is_not_empty | [] | Returns items that have a team assigned. |
Examples
Filter by team
query {
boards(ids: 1234567890) {
items_page(
query_params: {
rules: [
{
column_id: "team"
compare_value: [51166]
operator: any_of
}
]
}
) {
items {
id
name
column_values {
... on TeamValue {
team_id
text
}
}
}
}
}
}Exclude specific teams
query {
boards(ids: 1234567890) {
items_page(
query_params: {
rules: [
{
column_id: "team"
compare_value: [51166]
operator: not_any_of
}
]
}
) {
items {
id
name
}
}
}
}Filter by unassigned items
query {
boards(ids: 1234567890) {
items_page(
query_params: {
rules: [
{
column_id: "team"
compare_value: []
operator: is_empty
}
]
}
) {
items {
id
name
}
}
}
}Mutations
Update value
You can update a team column using change_multiple_column_values. Pass a JSON object with the team_id.
The team column does not support
change_simple_column_value. Attempting to use it will return an error: "column type TeamColumn is not supporting changing the column value with simple column value."
change_multiple_column_values
change_multiple_column_valuesmutation {
change_multiple_column_values(
item_id: 9876543210
board_id: 1234567890
column_values: "{\"team\": {\"team_id\": 51166}}"
) {
id
name
}
}const query = `
mutation ($boardId: ID!, $itemId: ID!, $columnValues: JSON!) {
change_multiple_column_values(
board_id: $boardId
item_id: $itemId
column_values: $columnValues
) {
id
name
}
}
`;
const variables = {
boardId: 1234567890,
itemId: 9876543210,
columnValues: JSON.stringify({
team: { team_id: 51166 }
})
};
const response = await mondayApiClient.request(query, variables);Set team on item creation
You can assign a team when creating an item by passing the team column value in the column_values argument.
mutation {
create_item(
board_id: 1234567890
item_name: "New task"
column_values: "{\"team\": {\"team_id\": 51166}}"
) {
id
name
}
}Clear
You can clear a team column using change_multiple_column_values by passing null.
mutation {
change_multiple_column_values(
item_id: 9876543210
board_id: 1234567890
column_values: "{\"team\": null}"
) {
id
name
}
}Reading column configuration
The team column has no configurable settings. The settings field returns an empty JSON object.
The
settings_strfield is deprecated as of API version 2025-10. Use the typedsettingsobject instead, which returns structured JSON rather than a JSON-encoded string.
query {
boards(ids: 1234567890) {
columns(ids: ["team"]) {
id
title
settings
}
}
}Example settings response
settings response{}Get column type schema
You can retrieve the JSON schema for the team column's settings programmatically using the get_column_type_schema query.
query {
get_column_type_schema(
type: team
)
}{
"data": {
"get_column_type_schema": {
"schema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"settings": {
"type": "object",
"description": "Column specific settings",
"properties": {},
"additionalProperties": false
}
}
}
}
}
}The team column has no configurable settings, so the schema contains an empty properties object.
