You can now return an account's non-active users with the non_active argument. Check out our documentation to learn more!

Today marks a huge milestone as we release the ability to build apps inside workdocs! As part of this release, we have a new set of queries and mutations to read and update workdocs via the API.

You can now query the content of a workdoc and its blocks, create new blocks inside a workdoc, update existing ones, or delete blocks. Check out our workdocs and document blocks documentation to find more details about these new queries and mutations.

You can also check out our developer blog for the full announcement or read through our workdocs app documentation to do a deep dive into the feature and build your first app!

We recently added the position argument or attribute to the update_group and create_group mutations. This new addition allows you to create a group with a specific position or update a group's position using a string that contains a numeric value. The higher the number, the lower the group sits; the lower the number, the higher the group sits.

Starting February 13th, if you create a column via the API with a title of 20 characters or less, the column ID will relate to the title. For example, if your column title is This is my column, then the column ID will be this_is_my_column.

If your title is more than 20 characters, the system will randomly generate a column ID based on the column_type and an ongoing index. It will not be related to the column title.

This update will only impact new columns, not existing ones!

We recently fixed unexpected API behavior that returned all users after running a teams query with an empty array for the ids argument. Now, if you send an empty array, it will return no users.

query {
  teams (ids:[]) {
    id
  }
}

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!

Please take note of the following updates to the boards object:

• The new add_teams_to_board mutation allows you to add teams to a board.
• We have deprecated the add_subscribers_to_board mutation. Please use the add_users_to_workspace or add_users_to_board mutations instead.

We recently added the country_code field to the account object. It will return the two-letter country code where the first account admin is located. Check out our documentation to learn more!

We added a new field and argument to the users object to expand its functionality:

1. The last_activity field returns the last date and time the user was active.
2. The name argument allows you to conduct a fuzzy search of users by name.

Check out all of the details about these updates in our documentation!

Due to popular demand, we recently released a new mutation that allows you to update a group! You can view this mutation's details, including the code samples, arguments, and accepted attribute values, in our documentation. Happy updating!

mutation {
  update_group (board_id: 12345678, group_id: "today", group_attribute: color, new_value: "red") { 
    id
  } 
}