Did you know that you can also use the create_column mutation to add a status or dropdown column with custom labels to a board?

This method requires you to send the label values as JSON strings using the defaults argument, so ensure that your JSON is formatted properly to avoid errors. Check out our documentation to see a few examples!

You can now query and mutate the brand-new folders object via the API! Querying the new object will return metadata about one or a collection of folders and their contents. You can also use one of the new mutations to create, update, or delete folders. Check out our folders API reference for all of the details!

The brand-newmove_subitem webhook allows you to listen for when a subitem moves from one parent item to another. Check out our documentation to see the complete list of available event types!

The new out_of_office field for the users object allows you to check a user's out-of-office status. The out_of_office field also supports the following fields to give you additional information about the user's status:

• active
• disable_notifications
• end_date
• start_date
• type

Check out our documentation to see more info about the users object!

The position argument has also been deprecated for the update_group mutation. You can now use the group_attribute and new_value arguments to move the updated group before or after a specific group on the board. Check out our documentation to find all the details!

We recently deprecated the position argument for the create_group mutation. You can still specify the new group's location on the board using the recently released relative_to and position_relative_method arguments. You can find all of the details about these new arguments in our documentation!

mutation {
	create_group (board_id: 1234567890, group_name: "new group", relative_to: "test group", position_relative_method: before_at) {
		id
	}
}

We recently added the id argument to the create_column mutation, so you can now create a column with a custom ID! This argument is optional, and you will still receive an auto-generated ID if you choose not to use it.

If you send the id argument, ensure that your value meets the following requirements:

• [1-20] characters in length (inclusive)
• Only lowercase letters (a-z) and underscores (_)
• Must be unique - no other column on the board can have the same ID
• Can't be null, blank, or an empty string

If your value doesn't meet these requirements, the mutation will fail, and the column will not be created. Check out our documentation for more information!

Starting April 15th, 2023, we will deprecate connections from Windows Server 2012 R2, Windows 8.1, or earlier because they use weak ciphers. This update will not impact support for TLS 1.3.

Check out this document to find out which systems this update impacts, how to know if you are affected, and which ciphers you can use!

We recently fixed a bug that prevented users from creating a subitem via the API if no subitems were ever made via the web.

The bug fix first verifies that the board doesn’t already have a subitem column and that the user has the required permissions to edit the board structure. If so, the user can then create a board’s first subitem via the API!

We recently added two new webhook events - column_created and item_restored - that enable you to listen for when a column is created or when an item is restored from the trash/archives.