Create-Only: Array of tag GIDs. GIDs are long numeric strings (e.g., '1210124791807961'). Obtain tag GIDs via ASANA_GET_TAGS action. Use 'addTag'/'removeTag' for updates.
Indicates if the task is liked by the authorized user.
Default: false
Free-form textual description of the task. Mutually exclusive with 'html_notes' - if both are provided, html_notes takes precedence.
UTC due date and time (ISO 8601). Null if no due time. Mutually exclusive with 'due_on'.
Localized due date (YYYY-MM-DD). Null if no due date. Mutually exclusive with 'due_at'.
GID of parent task for subtasks. GIDs are long numeric strings (e.g., '1210124791807961'). Null for top-level tasks.
User GID to assign the task. GIDs are long numeric strings (e.g., '1210124065021206'). Use 'me' for current user, or obtain user GIDs via ASANA_GET_USERS_FOR_WORKSPACE action.
Create-Only: Array of project GIDs for association. GIDs are long numeric strings (e.g., '1210124791807961'). Obtain project GIDs via ASANA_GET_WORKSPACE_PROJECTS action or from project URLs in Asana UI (the numeric ID in the URL). Do NOT use placeholder strings like '<project_gid>' - only actual numeric GIDs are valid. Use 'addProject'/'removeProject' for updates.
UTC start date and time (ISO 8601). Null if no start time. Mutually exclusive with 'start_on'. `due_at` is required if `start_at` is set/unset.
Localized start date (YYYY-MM-DD). Null if no start date. Mutually exclusive with 'start_at'. `due_on` or `due_at` is required if `start_on` is set/unset.
Indicates if the task is complete.
Default: false
Create-Only: Array of user identifiers (GID, email, 'me') for followers. GIDs are long numeric strings (e.g., '1210124065021206'). Use 'addFollowers'/'removeFollowers' actions for updates.
Workspace/organization GID. Must be a numeric GID string (e.g., '1205766922013215'). Unlike 'assignee', 'me' is NOT supported. Obtain workspace GIDs via ASANA_GET_CURRENT_USER action (returns accessible workspaces). Required unless 'parent' or 'projects' specified.
Task notes with HTML formatting for rich text. Mutually exclusive with 'notes' - if both are provided, html_notes takes precedence. Must be valid XML wrapped in <body> tags. Supported tags: <strong>, <em>, <u>, <s>, <code>, <ol>, <ul>, <li>, <a> (with href attribute), <blockquote>, <pre>, <h1>, <h2>, <hr/>. Special characters (<, >, &) in text content must be XML-escaped (<, >, &). Attribute values must be properly quoted (href="url").
GID of a custom_type. GIDs are long numeric strings (e.g., '1210124791807961').
Object mapping custom field GIDs to their values. CRITICAL: Custom fields must be explicitly added to a project before they can be used on tasks in that project. The same custom field name can have different GIDs in different workspaces. Workflow: (1) Use ASANA_GET_A_PROJECT with opt_fields='custom_field_settings.custom_field' to get custom fields available on your target project, OR use ASANA_GET_CUSTOM_FIELDS_FOR_WORKSPACE to get workspace-level fields (note: workspace fields still need to be added to projects), (2) Find the correct GID from that list, (3) Use it here. GIDs are long numeric strings (e.g., '1210124791807961'). Values depend on field type: enum fields use option GIDs (numeric strings), text fields use strings, number fields use numbers. For DATE fields, pass either a date string (YYYY-MM-DD) or ISO 8601 datetime string - these will be auto-converted to the required object format. Alternatively, pass date values as objects: {'date': 'YYYY-MM-DD'} for date-only or {'date_time': 'ISO8601'} for datetime.
Approval status (e.g., 'pending', 'approved'). Only relevant for tasks with resource_subtype='approval'. Synchronized with 'completed': 'pending' means incomplete; 'approved', 'rejected', 'changes_requested' mean complete. Setting 'completed' to true sets this to 'approved'.
Options: pending, approved, rejected, changes_requested
Deprecated: Scheduling status for the assignee (e.g., 'upcoming', 'today'). Should only be set if assignee is provided. 'inbox'/'upcoming' place task at top of assignee's list section; others at bottom.
Options: today, upcoming, later, new, inbox
GID of assignee's 'My tasks' section. CRITICAL: Must be a numeric GID string (e.g., '1210124791807961'), NOT a section name like 'Today' or 'Later'. Section names will be rejected by the API. Only writable if section is visible in the user's 'My tasks'. To obtain section GIDs, use the ASANA_GET_A_USER_TASK_LIST action with the user's GID and opt_fields='sections,sections.name'.
Subtype of the task (e.g., 'default_task', 'milestone'). Milestone tasks cannot have a 'start_date'.
Options: default_task, milestone, approval
Default: "default_task"
custom_type_status_option
STRINGGID of a custom_type_status_option. GIDs are long numeric strings (e.g., '1210124791807961').