Name of the task. This is generally a short sentence fragment that fits on a line in the UI for maximum readability, but it can be longer. Optional for updates - Asana allows partial updates.
True if the task is liked by the authorized user, false if not.
Free-form textual information associated with the task (i.e., its description).
The UTC date and time on which this task is due (e.g., '2023-09-15T02:06:58.147Z'). Null if the task has no due time. This takes an ISO 8601 date string and should not be used together with `due_on`.
The localized date on which this task is due (e.g., '2023-09-15'). Null if the task has no due date. This takes a date with YYYY-MM-DD format and should not be used together with `due_at`.
The GID of the user to assign the task to. Can be the string 'me' to assign to the authenticated user, or an email address.
The UTC date and time on which work begins for the task (e.g., '2023-09-14T09:00:00.000Z'). Null if the task has no start time. This takes an ISO 8601 date string in UTC and should not be used together with `start_on`. *Note: `due_at` must be present in the request when setting or unsetting the `start_at` parameter.*
The localized date on which work begins for the task (e.g., '2023-09-14'). Null if the task has no start date. This takes a date with YYYY-MM-DD format and should not be used together with `start_at`. *Note: `due_on` or `due_at` must be present in the request when setting or unsetting the `start_on` parameter.*
True if the task is currently marked complete, false if not.
The GID of the workspace to associate the task with. This is usually only required if the task is being moved between workspaces, which is a rare operation.
The notes of the task with rich text formatting. Content is automatically converted to Asana-compatible XML. Supported tags: <strong>, <em>, <u>, <s>, <code>, <pre>, <blockquote>, <ol>, <ul>, <li>, <a>, <h1>, <h2>, <hr/>. Note: <br> tags are auto-converted to newlines (not supported by Asana). <b> and <i> are converted to <strong> and <em>. Unsupported tags (div, span, p, etc.) are stripped but their content is preserved. Ampersands (&) are auto-escaped to &. Content is auto-wrapped in <body> tags if not present.
The GID of the custom type for the task. This is relevant for tasks using specific task type configurations.
An object (not a JSON string) where each key is the GID of a custom field and its corresponding value is the new value for that custom field. The value can be an enum GID, string, number, object, or array, depending on the custom field type. For date-type custom fields, you can pass: (1) a plain date string 'YYYY-MM-DD' which will be converted to {'date': 'YYYY-MM-DD'}, (2) an ISO 8601 datetime string like '2024-08-23T22:00:00.000Z' which will be converted to {'date_time': 'ISO-string'}, or (3) a properly formatted object with either 'date' OR 'date_time' key (not both). Use ASANA_GET_CUSTOM_FIELDS_FOR_WORKSPACE to fetch available custom fields for your workspace.
Reflects the approval status of this task. This field is kept in sync with `completed`, meaning `pending` translates to false while `approved`, `rejected`, and `changes_requested` translate to true. If you set `completed` to true, this field will be set to `approved`.
Options: pending, approved, rejected, changes_requested
Deprecated: Scheduling status of this task for the user it is assigned to. This field can only be set if the assignee is non-null. Do not include this field when updating tasks without an assignee. Setting this field to `inbox` or `upcoming` inserts it at the top of the section, while other options will insert at the bottom.
Options: today, upcoming, later, new, inbox
The GID of the assignee's section in their 'My tasks' list where the task should be placed. This is applicable only if the task is assigned to a user and the section exists and is visible in their 'My tasks' list. This field is returned in the response only if the request is made by the task's assignee.
The subtype of this resource. Different subtypes retain many of the same fields and behavior, but may render differently in Asana or represent resources with different semantic meaning. The `milestone` resource_subtype represents a single moment in time and tasks with this subtype cannot have a start_date.
Options: default_task, milestone, approval
custom_type_status_option
STRINGThe GID of the status option for the custom task type. This is used in conjunction with `custom_type`.