---
agentTools:
  projectIndex: https://developers.wrike.com/llms.txt
---

# Custom Statuses and Workflows

Today we announced the release of Custom Workflows, where users are no longer confined to the four default task statuses (read all the details in [this blog post](https://www.wrike.com/blog/accelerate-business-wrikes-new-custom-workflows/)). Custom Statuses and Custom Workflows operations are already available through the API:

* Get a full list of existing Workflows using [\[GET\] /accounts/\{accountId}/workflows](https://wrike.readme.io/wrike-production/reference/getworkflowsempty)
* Add a new Custom Workflow using \[POST] [/accounts/\{accountId}/workflows](https://wrike.readme.io/wrike-production/reference/postworkflowsempty)
* Add or remove Custom Statuses from a Custom Workflow using [\[PUT\] /workflows/\{workflowId}](https://wrike.readme.io/wrike-production/reference/putworkflowssingle)

We have also added auth scopes related to managing Workflows (read the details on auth scopes in [our docs on OAuth](https://wrike.readme.io/wrike-production/docs/oauth-20-authorization)):

* amReadOnlyWorkflow, amReadWriteWorkflow: access to the Workflow endpoints is given only for apps that request these scopes during authorization. Access is either read-only or read/write, respectively.
* amReadOnlyWorkflow has also been added to the default auth scope, so by default users can retrieve a list of all existing Workflows in the account.

We have also updated the Custom Fields parameter returned in \[GET] /accounts: now you will know the type of Custom Field and can handle data input / output correctly, whether it is a boolean value, date, or any other type of data supported in Custom Fields.