Asana API Integration

These are the list of integration use cases supported by Knit for Asana API as part of the TICKETING category

Delete a Specific Project

ID: delete_a_specific_project
Operation: write
Entities: authentication, project, error
Summary: This API endpoint allows you to delete a specific, existing project in Asana by making a DELETE request to the specified URL with the project's globally unique identifier (project_gid) as a path parameter. The request requires an 'accept' header with the value 'application/json'. Optionally, you can include the 'opt_pretty' query parameter to receive a prettified response. Upon successful deletion, the API returns a 200 status code with an empty data object. If there are errors, such as missing or malformed parameters, authentication issues, or access restrictions, the API returns appropriate error messages with status codes ranging from 400 to 500, each providing detailed error information and guidance.
Input Fields: Input Fields
Output Fields: Output Fields

Delete a Story

ID: delete_a_story
Operation: write
Entities: story, user
Summary: The 'Delete a Story' API endpoint allows users to delete a story in Asana. The user must have created the story to delete it. The endpoint requires the 'story_gid' path parameter, which is the globally unique identifier for the story. An optional query parameter 'opt_pretty' can be used to format the response in a more readable way. The request must include an 'accept' header specifying 'application/json'. On successful deletion, the API returns a 200 status code with an empty data object. If there are errors, such as missing parameters or authentication issues, the API returns appropriate error messages with status codes like 400, 401, 403, 404, or 500, along with detailed error information.
Input Fields: Input Fields
Output Fields: Output Fields

Delete Membership

ID: delete_membership
Operation: write
Entities: goal, project, membership
Summary: The Delete Membership API allows you to delete a specific, existing membership for a goal, project, or portfolio by making a DELETE request to the specified URL. The request requires the 'membership_gid' path parameter, which is a globally unique identifier for the membership. Optionally, you can include the 'opt_pretty' query parameter to format the response in a more readable way. The API returns an empty data object upon successful deletion, indicated by a 200 status code. In case of errors, the API provides detailed error messages and help links to assist in troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Delete a Specific Section in Asana

ID: delete_specific_section_in_asana
Operation: write
Entities: section, project, error
Summary: This API endpoint allows you to delete a specific section in Asana by making a DELETE request to the specified URL. The section must be empty to be deleted, and the last remaining section cannot be deleted. The request requires the 'section_gid' path parameter, which is the globally unique identifier for the section. An optional query parameter 'opt_pretty' can be used to format the response in a more readable way. The response will return an empty data block on success, or an error message with details if the request fails due to various reasons such as missing parameters, authentication issues, or server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Delete a Specific Tag in Asana

ID: delete_specific_tag_in_asana
Operation: write
Entities: tag, response, error
Summary: This API endpoint allows you to delete a specific tag in Asana by making a DELETE request to the specified URL with the tag's globally unique identifier (tag_gid) as a path parameter. The request can optionally include a query parameter 'opt_pretty' to format the response in a more readable way. The response will return an empty data object upon successful deletion. In case of errors, the response will include detailed error messages and help information. Possible error responses include 400 for malformed requests, 401 for unauthorized access, 403 for forbidden actions, 404 for not found resources, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Delete a Specific Task in Asana

ID: delete_specific_task_in_asana
Operation: write
Entities: user, task, system
Summary: This API endpoint allows you to delete a specific task in Asana by making a DELETE request to the specified URL with the task's unique identifier (task_gid) in the path. The task is moved to the user's trash and can be recovered within 30 days. The request can include an optional query parameter 'opt_pretty' to format the response in a readable way. The response will return an empty data object on success, or an error message with details if the request fails due to issues like missing parameters, authentication errors, or access restrictions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Compact Project Membership Record

ID: get_compact_project_membership_record
Operation: read
Entities: membership, project, user
Summary: This API endpoint retrieves a compact project membership record for a single membership in Asana. It currently supports only project memberships. The request requires the membership_gid as a path parameter and can optionally include additional fields in the response using the opt_fields query parameter. The response includes details about the membership, such as the member's access level, the project they belong to, and their role within the project. The API returns a JSON object with the membership details, and it handles various error responses for invalid requests, authentication issues, and server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Compact Project Records

ID: get_compact_project_records
Operation: read
Entities: workspace, project, team
Summary: The Get Compact Project Records API endpoint allows users to retrieve compact project records from Asana. The endpoint supports filtering projects using query parameters such as 'limit', 'offset', 'workspace', 'team', 'archived', and 'opt_fields'. The response includes a list of project objects with basic details like 'gid', 'resource_type', and 'name'. If pagination is used, the response will also include a 'next_page' object with details for fetching subsequent pages. The API returns JSON formatted data and supports optional fields to customize the response.
Input Fields: Input Fields
Output Fields: Output Fields

Get Compact Project Records for a Team

ID: get_compact_project_records_for_a_team
Operation: read
Entities: workspace, project, team
Summary: This API endpoint retrieves compact project records for all projects within a specified team in Asana. The request is made to the URL 'https://app.asana.com/api/1.0/teams/{team_gid}/projects' using the GET method. The request requires an 'accept' header with the value 'application/json'. The 'team_gid' path parameter is mandatory to specify the team. Optional query parameters include 'limit' to define the number of results per page, 'offset' for pagination, 'archived' to filter projects by their archived status, and 'opt_fields' to specify additional fields to include in the response. The response includes an array of project objects, each with a 'gid', 'resource_type', and 'name'. If pagination is used, a 'next_page' object may be included in the response, providing details for fetching subsequent pages.
Input Fields: Input Fields
Output Fields: Output Fields

Get Compact Project Records for All Projects in a Workspace

ID: get_compact_project_records_for_all_projects_in_a_workspace
Operation: read
Entities: workspace, project, team
Summary: This API endpoint retrieves compact project records for all projects within a specified workspace in Asana. The request is made using the GET method to the URL 'https://app.asana.com/api/1.0/workspaces/{workspace_gid}/projects', where 'workspace_gid' is the globally unique identifier for the workspace. The response includes compact project objects by default, but additional fields can be included using the 'opt_fields' query parameter. The API supports pagination through 'limit' and 'offset' query parameters. The response contains an array of project objects, each with a 'gid', 'resource_type', and 'name'. If pagination is used, a 'next_page' object may be included in the response, providing details for fetching the next set of results. The API may return various error responses, including 400 for malformed requests, 401 for authentication issues, 403 for access issues, 404 for not found errors, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Compact Tag Records

ID: get_compact_tag_records
Operation: read
Entities: workspace, tag
Summary: The Get Compact Tag Records API endpoint returns compact tag records for a filtered set of tags. It supports filtering through query parameters such as 'limit' for pagination, 'offset' for pagination offset, 'workspace' to filter tags by workspace, and 'opt_fields' to include additional optional fields in the response. The response includes an array of tag objects with properties like 'gid', 'resource_type', and 'name'. If pagination is used, a 'next_page' object is included in the response to fetch subsequent pages. The API handles various error responses with appropriate HTTP status codes and detailed error messages.
Input Fields: Input Fields
Output Fields: Output Fields

Get Compact Tag Records for a Workspace

ID: get_compact_tag_records_for_a_workspace
Operation: read
Entities: workspace, tag, task
Summary: This API endpoint retrieves compact tag records for a specified workspace in Asana. The request is made to the URL https://app.asana.com/api/1.0/workspaces/{workspace_gid}/tags using the GET method. The API accepts query parameters such as 'limit' to specify the number of results per page, 'offset' for pagination, and 'opt_fields' to include additional fields in the response. The response includes an array of tag objects, each with properties like 'gid', 'resource_type', and 'name'. If pagination is used, a 'next_page' object is included in the response, providing the offset, path, and URI for the next set of results. The API returns a 200 status code for successful requests, and various error codes (400, 401, 403, 404, 500) for different types of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Compact Task Records

ID: get_compact_task_records
Operation: read
Entities: workspace, project, task
Summary: The Get Compact Task Records API endpoint allows users to retrieve compact task records based on various filters. The endpoint requires a GET request to 'https://app.asana.com/api/1.0/tasks'. Users can filter tasks using query parameters such as 'limit', 'offset', 'assignee', 'project', 'section', 'workspace', 'completed_since', 'modified_since', and 'opt_fields'. The response includes an array of task objects with properties like 'gid', 'resource_type', 'name', 'resource_subtype', and 'created_by'. Pagination is supported through the 'next_page' object in the response, which provides 'offset', 'path', and 'uri' for fetching subsequent pages. The API returns a 200 status code for successful requests, while errors such as 400, 401, 403, 404, and 500 are handled with appropriate error messages.
Input Fields: Input Fields
Output Fields: Output Fields

Get Complete Tag Record

ID: get_complete_tag_record
Operation: read
Entities: workspace, tag, user
Summary: The Get Complete Tag Record API endpoint retrieves the full details of a specific tag in Asana using its globally unique identifier (tag_gid). The request is made using the GET method to the URL https://app.asana.com/api/1.0/tags/{tag_gid}. The API accepts an optional query parameter 'opt_fields' to specify additional fields to include in the response. The response includes detailed information about the tag, such as its name, color, notes, creation time, followers, associated workspace, and a permalink URL. The API returns a 200 status code with the tag details on success, and various error codes (400, 401, 403, 404, 500) with corresponding error messages and help links in case of failure.
Input Fields: Input Fields
Output Fields: Output Fields

Get Complete Task Record

ID: get_complete_task_record
Operation: read
Entities: user, project, task
Summary: The Get Complete Task Record API retrieves the full details of a single task from Asana using its globally unique identifier (task_gid). The API endpoint is accessed via a GET request to 'https://app.asana.com/api/1.0/tasks/{task_gid}'. The request requires an 'accept' header with the value 'application/json'. Optionally, a 'opt_fields' query parameter can be included to specify a comma-separated list of additional fields to include in the response. The response includes detailed information about the task, such as its name, status, assignee, dependencies, and custom fields. The API also provides error responses for various HTTP status codes, including 400, 401, 403, 404, and 500, each with a descriptive error message and a help URL for further information.
Input Fields: Input Fields
Output Fields: Output Fields

Get Full Record for a Single Team

ID: get_full_record_for_a_single_team
Operation: read
Entities: workspace, project, team
Summary: This API endpoint retrieves the full record for a single team in Asana. The request is made using the GET method to the URL https://app.asana.com/api/1.0/teams/{team_gid}, where {team_gid} is the globally unique identifier for the team. The request requires an 'accept' header with the value 'application/json'. Optionally, a 'opt_fields' query parameter can be included to specify additional properties to be returned in the response. The response includes detailed information about the team, such as its name, description, visibility, and various access levels. In case of errors, the API returns appropriate HTTP status codes along with detailed error messages.
Input Fields: Input Fields
Output Fields: Output Fields

Get Portfolio Membership Details

ID: get_portfolio_membership_details
Operation: read
Entities: portfolio membership, user, portfolio
Summary: This API endpoint retrieves the complete portfolio record for a single portfolio membership in Asana. It requires the portfolio_membership_gid as a path parameter to identify the specific portfolio membership. The request can include optional query parameters to specify additional fields to be included in the response. The response includes details about the portfolio membership, such as the globally unique identifier, resource type, portfolio details, user details, and access level. The API returns a JSON object with the portfolio membership data or an error message if the request fails.
Input Fields: Input Fields
Output Fields: Output Fields

Get Portfolio Memberships

ID: get_portfolio_memberships
Operation: read
Entities: portfolio membership, user, portfolio
Summary: The Get Portfolio Memberships API endpoint returns a list of portfolio memberships in a compact representation. The request must specify either a portfolio, portfolio and user, or workspace and user. By default, the response includes compact portfolio membership objects, but additional fields can be included using the 'opt_fields' query parameter. The response includes details about the portfolio, user, and access level. Pagination is supported, and the 'next_page' object provides information for fetching additional results if available. The API handles various error responses, including 400 for malformed requests, 401 for authentication issues, 403 for access denial, 404 for unknown actions or non-existent objects, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Project Task Counts

ID: get_project_task_counts
Operation: read
Entities: milestone, project, task
Summary: The 'Get Project Task Counts' API endpoint retrieves an object containing task count fields for a specified project in Asana. By default, all fields are excluded, and you must use the 'opt_fields' query parameter to specify which fields to include in the response. The available fields include 'num_completed_milestones', 'num_completed_tasks', 'num_incomplete_milestones', 'num_incomplete_tasks', 'num_milestones', and 'num_tasks'. The endpoint is accessed via a GET request to 'https://app.asana.com/api/1.0/projects/{project_gid}/task_counts', where 'project_gid' is the globally unique identifier for the project. The response includes the task counts in a JSON object under the 'data' key. The API also handles various error responses, including 400 (bad request), 401 (unauthorized), 403 (forbidden), 404 (not found), and 500 (server error), each providing detailed error messages and guidance.
Input Fields: Input Fields
Output Fields: Output Fields

Get Projects for a Task

ID: get_projects_for_a_task
Operation: read
Entities: workspace, project, task
Summary: This API endpoint retrieves a compact representation of all projects associated with a specific task in Asana. The request is made using the GET method to the URL 'https://app.asana.com/api/1.0/tasks/{task_gid}/projects', where 'task_gid' is the globally unique identifier for the task. The response includes a list of projects, each with a globally unique identifier (gid), resource type, and name. The response can be customized to include additional fields by using the 'opt_fields' query parameter. The API returns a paginated response if a limit is specified, with details for fetching the next page if more results are available. Error responses include detailed messages and help links for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Search Tasks in Asana Workspace

ID: get_search_tasks_in_asana_workspace
Operation: read
Entities: workspace, user, task
Summary: The Asana Task Search API endpoint allows premium users to perform advanced searches within a specified workspace. Users can filter tasks using complex criteria, similar to the Asana web app's advanced search feature. The endpoint requires a valid workspace_gid and supports optional query parameters to customize the response fields. The response includes task objects with properties like gid, resource_type, name, and created_by. The API supports pagination by sorting results by creation time. It is important to note that only premium users or users in premium teams can access this feature, and rate limits apply.
Input Fields: Input Fields
Output Fields: Output Fields

Get Section Details

ID: get_section_details
Operation: read
Entities: section, project, task
Summary: The Get Section Details API endpoint retrieves the complete record for a single section in Asana. It requires the section's globally unique identifier (section_gid) as a path parameter. The API supports an optional query parameter 'opt_fields' to specify additional fields to include in the response. The response includes details about the section such as its name, creation time, and associated project information. The API returns a JSON object with the section's data, and handles various error responses including missing parameters, authentication issues, and access restrictions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Sections of a Project

ID: get_sections_of_a_project
Operation: read
Entities: section, project, task
Summary: This API endpoint retrieves the compact records for all sections within a specified project in Asana. The request requires the project_gid as a path parameter to identify the project. Optional query parameters include 'limit' to specify the number of results per page, 'offset' for pagination, and 'opt_fields' to include additional fields in the response. The response includes an array of section objects, each with a globally unique identifier (gid), resource type, and name. If pagination is used, a 'next_page' object may be included in the response to facilitate fetching additional pages. Error responses provide detailed messages and guidance for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Get Stories for a Task

ID: get_stories_for_a_task
Operation: read
Entities: user, story, task
Summary: This API endpoint retrieves the compact records for all stories associated with a specific task in Asana. The request is made using the GET method to the URL 'https://app.asana.com/api/1.0/tasks/{task_gid}/stories', where 'task_gid' is the globally unique identifier for the task. The API supports query parameters such as 'limit' to specify the number of results per page, 'offset' for pagination, and 'opt_fields' to include additional fields in the response. The response includes an array of story objects, each containing details like 'gid', 'resource_type', 'created_at', 'created_by', 'resource_subtype', and 'text'. If pagination is used, a 'next_page' object is included in the response to fetch subsequent pages. The API handles various error responses, including 400 for malformed requests, 401 for authentication issues, 403 for access denial, 404 for non-existent resources, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Subtasks of a Task

ID: get_subtasks_of_a_task
Operation: read
Entities: user, task, subtask
Summary: The 'Get Subtasks of a Task' API endpoint allows users to retrieve a compact representation of all subtasks associated with a specific task in Asana. The endpoint requires the task's globally unique identifier (task_gid) as a path parameter. Optional query parameters include 'limit' to specify the number of results per page, 'offset' for pagination, and 'opt_fields' to customize the fields included in the response. The response includes an array of task objects, each with properties such as 'gid', 'resource_type', 'name', 'resource_subtype', and 'created_by'. If pagination is used, a 'next_page' object is included in the response, providing details for fetching subsequent pages. The API returns various HTTP status codes to indicate success or specific errors, such as 400 for malformed requests, 401 for authentication issues, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Tags for a Task

ID: get_tags_for_a_task
Operation: read
Entities: workspace, tag, task
Summary: This API endpoint retrieves a compact representation of all tags associated with a specific task in Asana. The request is made using the GET method to the URL 'https://app.asana.com/api/1.0/tasks/{task_gid}/tags', where 'task_gid' is the globally unique identifier for the task. The request requires an 'accept' header with the value 'application/json'. Optionally, a 'opt_fields' query parameter can be included to specify additional fields to be returned in the response. The response includes an array of tag objects, each containing a 'gid', 'resource_type', and 'name'. If pagination is used, a 'next_page' object may be included in the response. Error responses may include status codes 400, 401, 403, 404, and 500, each with a detailed error message and help information.
Input Fields: Input Fields
Output Fields: Output Fields

Get Task Dependencies

ID: get_task_dependencies
Operation: read
Entities: user, task, dependency
Summary: The Get Task Dependencies API endpoint retrieves the compact representations of all dependencies of a specified task in Asana. The request is made using the GET method to the URL 'https://app.asana.com/api/1.0/tasks/{task_gid}/dependencies', where 'task_gid' is the globally unique identifier for the task. The request requires an 'accept' header with the value 'application/json'. Optionally, a 'opt_fields' query parameter can be included to specify additional fields to be returned in the response. The response includes an array of task objects, each with properties such as 'gid', 'resource_type', 'name', 'resource_subtype', and 'created_by'. If pagination is used, a 'next_page' object may be included in the response, providing details for fetching subsequent pages. Error responses may include status codes 400, 401, 402, 403, 404, and 500, each with a detailed error message.
Input Fields: Input Fields
Output Fields: Output Fields

Get Task Dependents

ID: get_task_dependents
Operation: read
Entities: user, task, dependent
Summary: The Get Task Dependents API endpoint retrieves the compact representations of all dependents of a specified task in Asana. The request requires the task's globally unique identifier (task_gid) as a path parameter. Optionally, a query parameter 'opt_fields' can be used to specify additional fields to include in the response. The response includes an array of task objects, each with properties such as 'gid', 'resource_type', 'name', 'resource_subtype', and 'created_by'. If pagination is used, a 'next_page' object is included in the response to fetch additional pages.
Input Fields: Input Fields
Output Fields: Output Fields

Get Tasks by Tag

ID: get_tasks_by_tag
Operation: read
Entities: user, tag, task
Summary: This API endpoint retrieves the compact task records for all tasks associated with a specified tag in Asana. The request is made using the GET method to the URL 'https://app.asana.com/api/1.0/tags/{tag_gid}/tasks', where 'tag_gid' is the globally unique identifier for the tag. The response includes compact task objects by default, but additional fields can be included using the 'opt_fields' query parameter. The response contains an array of task objects, each with properties such as 'gid', 'resource_type', 'name', 'resource_subtype', and 'created_by'. Pagination is supported, and if more results exist, a 'next_page' object is included in the response with details for fetching the next set of results. Error responses include status codes and detailed error messages.
Input Fields: Input Fields
Output Fields: Output Fields

Get Tasks for a Project

ID: get_tasks_for_a_project
Operation: read
Entities: user, project, task
Summary: This API endpoint retrieves the compact task records for all tasks within a specified project in Asana, ordered by their priority within the project. The endpoint requires the project_gid as a path parameter to identify the project. Optionally, you can customize the response by specifying the opt_fields query parameter to include additional fields in the response. The response includes an array of task objects, each with properties such as gid, resource_type, name, resource_subtype, and created_by. If pagination is used, the response will also include a next_page object with details for fetching the next set of results.
Input Fields: Input Fields
Output Fields: Output Fields

Get Tasks in a Section

ID: get_tasks_in_a_section
Operation: read
Entities: user, section, task
Summary: This API endpoint retrieves the compact section records for all tasks within a specified section in Asana's board view. The request is made using the GET method to the URL https://app.asana.com/api/1.0/sections/{section_gid}/tasks, where {section_gid} is the globally unique identifier for the section. The response includes compact task objects by default, but additional fields can be included using the 'opt_fields' query parameter. The response contains an array of task objects, each with properties such as 'gid', 'resource_type', 'name', 'resource_subtype', and 'created_by'. Pagination information is provided in the 'next_page' object if applicable. The API returns various HTTP status codes to indicate success or specific errors, such as 400 for malformed requests, 401 for authentication issues, 403 for access denial, 404 for non-existent resources, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Team Membership Details

ID: get_team_membership_details
Operation: read
Entities: user, team membership, team
Summary: The Get Team Membership Details API endpoint retrieves the complete team membership record for a specified team membership in Asana. The request requires the 'team_membership_gid' path parameter to identify the specific team membership. Optionally, the 'opt_fields' query parameter can be used to specify additional fields to include in the response. The response includes details about the user's connection to the team, such as user and team information, and flags indicating if the user is a guest, has limited access, or is an admin. The API returns various HTTP status codes to indicate success or specific errors, with detailed error messages and help links provided in the response body.
Input Fields: Input Fields
Output Fields: Output Fields

Get Team Membership Records

ID: get_team_membership_records
Operation: read
Entities: user, team membership, team
Summary: The Get Team Membership Records API endpoint allows users to retrieve compact team membership records from Asana. The endpoint supports optional query parameters such as 'team', 'user', 'workspace', and 'opt_fields' to customize the response. The 'team' parameter is a globally unique identifier for the team, while 'user' can be a string identifying a user, and 'workspace' is a globally unique identifier for the workspace. The 'opt_fields' parameter allows users to include additional fields in the response. The API returns a JSON object containing an array of team membership records, each with details about the user, team, and their roles. The response also includes pagination information if applicable. Error responses include detailed messages and help links for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Get Team Memberships for a Team

ID: get_team_memberships_for_a_team
Operation: read
Entities: user, team membership, team
Summary: This API endpoint retrieves the compact team memberships for a specified team in Asana. The request is made using the GET method to the URL 'https://app.asana.com/api/1.0/teams/{team_gid}/team_memberships', where 'team_gid' is the globally unique identifier for the team. The request requires an 'accept' header with the value 'application/json'. Optionally, a 'opt_fields' query parameter can be included to specify additional fields to be returned in the response. The response includes an array of team membership objects, each containing details about the user, team, and membership status (such as 'is_guest', 'is_limited_access', and 'is_admin'). The response may also include pagination information if applicable. Error responses include detailed messages and help links for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Get Team Users

ID: get_team_users
Operation: read
Entities: workspace, user, team
Summary: The Get Team Users API endpoint returns compact records for all users that are members of a specified team in Asana. The results are sorted alphabetically and limited to 2000 users. To retrieve more results, the /users endpoint should be used. The API accepts a 'team_gid' path parameter to specify the team and an optional 'opt_fields' query parameter to include additional fields in the response. The response includes user objects with properties such as 'gid', 'resource_type', and 'name'. The API returns various HTTP status codes to indicate success or different types of errors, with detailed error messages and help links provided in the response body.
Input Fields: Input Fields
Output Fields: Output Fields

Get Teams in Workspace

ID: get_teams_in_workspace
Operation: read
Entities: workspace, organization, team
Summary: The 'Get Teams in Workspace' API endpoint retrieves compact records for all teams within a specified workspace that are visible to the authorized user. The request is made using the GET method to the URL 'https://app.asana.com/api/1.0/workspaces/{workspace_gid}/teams', where 'workspace_gid' is a required path parameter representing the globally unique identifier for the workspace. The response can be customized by including optional query parameters such as 'opt_fields', which allows the inclusion of additional properties in the response. The API returns a JSON object containing an array of team objects, each with properties like 'gid', 'resource_type', and 'name'. Pagination details are provided in the 'next_page' object if applicable. Error responses include detailed messages and help links for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Get User Details

ID: get_user_details
Operation: read
Entities: photo, workspace, user
Summary: The Get User Details API endpoint retrieves the full user record for a single user identified by the provided user_gid. The request requires an 'accept' header specifying 'application/json'. Optionally, a 'opt_fields' query parameter can be included to specify additional fields to be returned in the response. The response includes user details such as gid, resource_type, name, email, photo, and workspaces. The API returns a JSON object with the user's information, and handles various error responses with appropriate HTTP status codes and error messages.
Input Fields: Input Fields
Output Fields: Output Fields

Get User Favorites in Asana

ID: get_user_favorites_in_asana
Operation: read
Entities: workspace, favorite, user
Summary: The 'Get User Favorites in Asana' API endpoint retrieves all of a user's favorites within a specified workspace and of a given type. The results are ordered as they appear in the user's Asana sidebar. This endpoint only returns favorites for the current user associated with the authentication token. The API accepts a 'user_gid' path parameter to specify the user and an optional 'opt_fields' query parameter to include additional fields in the response. The response includes a list of favorite resources with their 'gid', 'resource_type', and 'name'. Pagination details are provided if applicable. Error responses include detailed messages and help links for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Get User Records from Asana

ID: get_user_records_from_asana
Operation: read
Entities: workspace, user, organization
Summary: This API endpoint retrieves user records for all users in all workspaces and organizations accessible to the authenticated user. The response can be customized using the 'opt_fields' query parameter to include additional fields such as email, name, and photo. The API returns a list of user objects, each containing a globally unique identifier (gid), resource type, and name. Pagination is supported through the 'next_page' attribute in the response. The API handles various error responses, including 400 for malformed requests, 401 for authentication issues, 403 for access denial, 404 for unknown actions or non-existent objects, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get User Task List

ID: get_user_task_list
Operation: read
Entities: workspace, user, user task list
Summary: The Get User Task List API endpoint retrieves the full record for a user's task list in Asana. It requires the user's globally unique identifier (user_gid) as a path parameter. The API supports an optional query parameter 'opt_fields' to specify additional fields to include in the response. The response includes details about the user task list, such as its globally unique identifier, resource type, name, owner, and workspace. The API returns a JSON response with a 200 status code on success, and various error codes (400, 401, 403, 404, 500) with detailed error messages in case of failure.
Input Fields: Input Fields
Output Fields: Output Fields

Get User Task List Details

ID: get_user_task_list_details
Operation: read
Entities: workspace, user, user task list
Summary: This API endpoint retrieves the full record for a user task list in Asana. It requires the 'user_task_list_gid' as a path parameter to identify the specific user task list. The request can include optional query parameters 'opt_fields' to specify additional fields to be included in the response. The response includes details such as the globally unique identifier, resource type, name, owner, and workspace of the user task list. The API returns various HTTP status codes to indicate success or different types of errors, such as missing input, authentication issues, or access restrictions.
Input Fields: Input Fields
Output Fields: Output Fields

Get User Task List Tasks

ID: get_user_task_list_tasks
Operation: read
Entities: workspace, user, task
Summary: This API endpoint retrieves a compact list of tasks from a user's 'My Tasks' list in Asana. It requires the 'user_task_list_gid' as a path parameter to identify the specific user task list. The response can be customized using the 'opt_fields' query parameter to include additional fields in the task objects. The API returns both complete and incomplete tasks by default, but tasks can be filtered using query parameters. The response includes task details such as 'gid', 'resource_type', 'name', and 'resource_subtype', along with pagination information if applicable. Access control is enforced, and private tasks will be filtered out if the authenticated user does not have access.
Input Fields: Input Fields
Output Fields: Output Fields

Get User Team Memberships

ID: get_user_team_memberships
Operation: read
Entities: user, team membership, team
Summary: The Get User Team Memberships API endpoint retrieves the compact team membership records for a specified user in Asana. The request requires the user's globally unique identifier (user_gid) as a path parameter and the workspace's globally unique identifier as a query parameter. Optionally, additional fields can be included in the response by specifying them in the 'opt_fields' query parameter. The response includes an array of team membership objects, each containing details about the user's connection to a team, such as the user's ID, name, team ID, team name, and roles within the team (e.g., is_guest, is_admin). The API also supports pagination, providing a 'next_page' object when more results are available. Error responses include detailed messages and help links for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Get Users in Workspace

ID: get_users_in_workspace
Operation: read
Entities: workspace, user, organization
Summary: This API endpoint retrieves the compact records for all users in a specified workspace or organization in Asana. The results are sorted alphabetically and limited to 2000 users. To retrieve more results, the /users endpoint should be used. The request can include optional query parameters to customize the response by specifying a comma-separated list of fields to include. The response includes a list of user objects, each containing a globally unique identifier (gid), resource type, and name. The API also handles various error responses, providing detailed error messages and help links for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Get User's Teams

ID: get_users_teams
Operation: read
Entities: user, organization, team
Summary: This API endpoint retrieves the compact records for all teams to which a specified user is assigned in Asana. The request is made using the GET method to the URL 'https://app.asana.com/api/1.0/users/{user_gid}/teams', where 'user_gid' is the globally unique identifier for the user. The response includes compact team objects by default, but additional fields can be included using the 'opt_fields' query parameter. The response contains an array of team objects, each with a 'gid', 'resource_type', and 'name'. If pagination is used, a 'next_page' object may be included in the response. The API also handles various error responses, including 400 (bad request), 401 (unauthorized), 403 (forbidden), 404 (not found), and 500 (server error), each providing detailed error messages and guidance.
Input Fields: Input Fields
Output Fields: Output Fields

Get Workspace Details

ID: get_workspace_details
Operation: read
Entities: workspace, project, task
Summary: The Get Workspace Details API endpoint retrieves the full workspace record for a specified workspace in Asana. The request requires the workspace_gid as a path parameter to identify the workspace. Optionally, the opt_fields query parameter can be used to specify additional properties to include in the response, such as email_domains, is_organization, and name. The response includes the workspace's globally unique identifier (gid), resource type, name, email domains, and organization status. The API returns various HTTP status codes to indicate success or failure, with detailed error messages and help links provided in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Workspaces

ID: get_workspaces
Operation: read
Entities: workspace, project, task
Summary: The Get Workspaces API endpoint returns the compact records for all workspaces visible to the authorized user. By default, the response includes 'compact' workspace objects, but additional fields can be included using the 'opt_fields' query parameter. The request requires an 'accept' header with 'application/json' as the media type. The response includes a list of workspaces, each with a globally unique identifier (gid), resource type, and name. If pagination is required, the response will include a 'next_page' object with details for fetching the next set of results. Error responses include detailed messages and help links for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Add Dependencies to a Task in Asana

ID: post_add_dependencies_to_task
Operation: write
Entities: task, dependency
Summary: This API endpoint allows you to mark a set of tasks as dependencies of a specified task in Asana, provided they are not already dependencies. The task can have a maximum of 30 dependents and dependencies combined. The request requires the task_gid as a path parameter to identify the task to operate on. Optionally, you can use the opt_pretty query parameter to format the response in a more readable way. The request body must include a list of task gids to set as dependencies. On success, the API returns an empty object with a 200 status code. Errors may occur due to missing or malformed parameters, invalid authentication tokens, or access restrictions, and are returned with appropriate status codes and error messages.
Input Fields: Input Fields
Output Fields: Output Fields

Add Dependents to a Task in Asana

ID: post_add_dependents_to_task
Operation: write
Entities: task, dependents, dependency
Summary: This API endpoint allows you to mark a set of tasks as dependents of a specified task in Asana, provided they are not already dependents. The task can have a maximum of 30 dependents and dependencies combined. The request requires the task_gid as a path parameter to identify the task to operate on. Optionally, you can use the opt_pretty query parameter to format the response in a more readable way. The request body must include a JSON object with a 'data' property containing an array of task gids to be added as dependents. On success, the API returns a 200 status code with an empty data object. In case of errors, the API returns appropriate status codes (400, 401, 402, 403, 404, 500) with detailed error messages and help links.
Input Fields: Input Fields
Output Fields: Output Fields

Add Tag to Task in Asana

ID: post_add_tag_to_task
Operation: write
Entities: tag, task
Summary: This API endpoint allows you to add a tag to a specific task in Asana. The request requires the task's unique identifier (task_gid) as a path parameter and the tag's unique identifier (tag) in the request body. Optionally, you can include the 'opt_pretty' query parameter to format the response in a more readable way. The request headers must include 'accept' and 'content-type' set to 'application/json'. On success, the API returns an empty data object with a 200 status code. In case of errors, it returns detailed error messages with appropriate HTTP status codes such as 400, 401, 403, 404, and 500.
Input Fields: Input Fields
Output Fields: Output Fields

Add Task to Project in Asana

ID: post_add_task_to_project
Operation: write
Entities: section, project, task
Summary: This API endpoint allows you to add a task to a specified project in Asana. The task is identified by the 'task_gid' path parameter, which is required. You can specify the project to add the task to in the request body, which is also required. Optional parameters include 'insert_after', 'insert_before', and 'section', which allow you to specify the position of the task within the project. The 'opt_pretty' query parameter can be used to format the response in a more readable way. The API returns an empty data block on success, indicated by a 200 status code. Error responses include detailed messages and help links for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Add Task to Section in Asana

ID: post_add_task_to_section
Operation: write
Entities: section, project, task
Summary: This API endpoint allows you to add a task to a specific, existing section in Asana. The task will be inserted at the top of the section unless an 'insert_before' or 'insert_after' parameter is specified. The endpoint does not work for separators (tasks with the resource_subtype of section). The request requires the 'section_gid' path parameter to specify the section, and optionally accepts a 'opt_pretty' query parameter for pretty formatting of the response. The request body must include the 'task' to be added, and optionally 'insert_before' or 'insert_after' to specify the task's position. The response will return a 200 status code with an empty object on success, or an error message with details if the request fails.
Input Fields: Input Fields
Output Fields: Output Fields

Add User to Asana Team

ID: post_add_user_to_asana_team
Operation: write
Entities: user, team membership, team
Summary: The 'Add User to Asana Team' API allows a user who is a member of a team to add another user to the same team. The user being added must exist in the same organization as the team. The API requires the team_gid as a path parameter to identify the team. Optional query parameters can be used to specify additional fields to include in the response. The request body must include a user identification object specifying the user to be added. Upon successful addition, the API returns the complete team membership record for the newly added user, including details such as user ID, team ID, and user roles within the team. The API handles various error responses, including missing or malformed parameters, authentication issues, and access permissions.
Input Fields: Input Fields
Output Fields: Output Fields

Add User to Workspace

ID: post_add_user_to_workspace
Operation: write
Entities: workspace, user, organization
Summary: This API endpoint allows you to add a user to a workspace or organization in Asana. The user can be identified by their globally unique user ID or their email address. The request requires a valid authentication token and the workspace_gid as a path parameter. Optionally, you can specify additional fields to include in the response using the opt_fields query parameter. The request body must include a data object with a user identifier. On success, the API returns the full user record for the invited user. Possible error responses include 400 for malformed requests, 401 for authentication issues, 403 for access denial, 404 for unknown actions or non-existent objects, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Create a New Section in a Project

ID: post_create_new_section_in_project
Operation: write
Entities: section, project, task
Summary: This API endpoint allows you to create a new section within a specified project in Asana. The request is made to the URL https://app.asana.com/api/1.0/projects/{project_gid}/sections using the POST method. The request requires headers specifying 'accept' and 'content-type' as 'application/json'. The path parameter 'project_gid' is required to identify the project. An optional query parameter 'opt_fields' can be used to specify additional fields to include in the response. The request body must include the 'name' of the section to be created, and optionally, 'insert_before' or 'insert_after' to specify the position of the new section. The response returns the full record of the newly created section, including its 'gid', 'resource_type', 'name', 'created_at', and associated 'project' details. Error responses include status codes 400, 401, 403, 404, and 500, each providing detailed error messages and help resources.
Input Fields: Input Fields
Output Fields: Output Fields

Create a New Subtask in Asana

ID: post_create_new_subtask
Operation: write
Entities: user, project, task
Summary: This API endpoint allows you to create a new subtask and add it to a parent task in Asana. The request is made using the POST method to the URL 'https://app.asana.com/api/1.0/tasks/{task_gid}/subtasks', where 'task_gid' is the globally unique identifier of the parent task. The request headers must include 'accept' and 'content-type' set to 'application/json'. The request body must contain the 'data' object with properties such as 'name', 'resource_subtype', 'assignee', 'custom_fields', 'followers', 'projects', 'tags', and 'workspace'. The response returns the full record for the newly created subtask, including details like 'gid', 'resource_type', 'name', 'created_by', 'approval_status', 'assignee_status', 'completed', 'due_at', 'due_on', 'external', 'html_notes', 'hearted', 'likes', 'memberships', 'modified_at', 'notes', 'num_hearts', 'num_likes', 'num_subtasks', 'start_at', 'start_on', 'actual_time_minutes', 'assignee', 'assignee_section', 'custom_fields', 'followers', 'parent', 'projects', 'tags', 'workspace', and 'permalink_url'.
Input Fields: Input Fields
Output Fields: Output Fields

Create a New Tag in a Workspace or Organization

ID: post_create_new_tag
Operation: write
Entities: workspace, tag, user
Summary: This API endpoint allows you to create a new tag in a specified workspace or organization in Asana. The tag is created with a name, optional color, notes, and followers. The request requires a valid workspace_gid path parameter and a JSON body containing the tag details. Optional query parameters can be used to include additional fields in the response. The response returns the full record of the newly created tag, including its globally unique identifier, name, color, notes, creation time, followers, associated workspace, and permalink URL. Error responses provide detailed messages and help links for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Create a New Task in Asana

ID: post_create_new_task
Operation: write
Entities: workspace, user, task
Summary: The 'Create a New Task in Asana' API allows users to create a new task by sending a POST request to the /tasks endpoint. The request must include a JSON body with the task details, such as name, notes, due date, assignee, and workspace. Optional query parameters can be used to specify additional fields to include in the response. The response includes detailed information about the created task, including its unique identifier, name, status, and associated projects and tags. The API also supports custom fields and allows for the inclusion of external metadata.
Input Fields: Input Fields
Output Fields: Output Fields

Create Project Template Asynchronously

ID: post_create_project_template_asynchronously
Operation: write
Entities: job, project, task
Summary: This API endpoint creates and returns a job that will asynchronously handle the creation of a project template in Asana. The request requires a POST method to the URL https://app.asana.com/api/1.0/projects/{project_gid}/saveAsTemplate, where {project_gid} is the globally unique identifier for the project. The request headers must include 'accept' and 'content-type' set to 'application/json'. The request body must include a 'data' object with 'name' and 'public' fields, and optionally 'team' or 'workspace' fields. The response returns a job object with details about the asynchronous process, including the status and identifiers for the new project, task, and project template. The API also supports optional query parameters to include additional fields in the response.
Input Fields: Input Fields
Output Fields: Output Fields

Create a Team in Asana Workspace

ID: post_create_team_in_asana_workspace
Operation: write
Entities: workspace, organization, team
Summary: This API endpoint allows you to create a new team within the current workspace in Asana. The request is made to the URL 'https://app.asana.com/api/1.0/teams' using the POST method. The request headers must include 'accept' and 'content-type' set to 'application/json'. You can optionally specify query parameters 'opt_fields' to include additional properties in the response. The request body must include the 'data' object with details about the team, such as 'name', 'description', 'organization', and various access levels. The response will include the details of the created team, including its 'gid', 'name', 'description', 'organization', and other properties. In case of errors, the response will contain error messages and additional information.
Input Fields: Input Fields
Output Fields: Output Fields

Duplicate Asana Project

ID: post_duplicate_asana_project
Operation: write
Entities: job, project, task
Summary: This API endpoint allows you to duplicate an existing Asana project. It creates and returns a job that will asynchronously handle the duplication process. The request requires a project_gid path parameter to specify the project to be duplicated. Optional query parameters can be used to include additional fields in the response. The request body must include the name of the new project and can optionally specify the team, elements to include in the duplication, and scheduling options for auto-shifting dates. The response includes a job object with details about the duplication process, including the status and identifiers for the new project and tasks. Error responses provide detailed messages and links to documentation for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Duplicate Asana Task

ID: post_duplicate_asana_task
Operation: write
Entities: job, project, task
Summary: This API endpoint allows you to duplicate an existing task in Asana. It creates and returns a job that will asynchronously handle the duplication process. The request requires a task_gid path parameter to specify the task to be duplicated. Optional query parameters can be used to include additional fields in the response. The request body must include the name of the new task and a list of fields to be duplicated. The response returns a job object with details about the duplication process, including the status and any new project or task created. Error responses provide detailed messages and help links for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Move Sections Relative to Each Other in a Project

ID: post_move_sections_relative_to_each_other
Operation: write
Entities: section, project
Summary: This API endpoint allows you to move sections relative to each other within a project in Asana. The endpoint requires a POST request to the URL https://app.asana.com/api/1.0/projects/{project_gid}/sections/insert, where {project_gid} is the globally unique identifier for the project. The request must include headers specifying 'accept' and 'content-type' as 'application/json'. The body of the request should contain a 'data' object with a 'section' field specifying the section to reorder. You can optionally include 'before_section' or 'after_section' to specify the position relative to other sections. The API returns an empty data block on success. Errors may occur due to missing or malformed parameters, invalid authentication, or access issues, and are returned with detailed error messages and help links.
Input Fields: Input Fields
Output Fields: Output Fields

Remove Custom Field Setting from Project

ID: post_remove_custom_field_setting_from_project
Operation: write
Entities: custom field setting, project
Summary: This API endpoint allows you to remove a custom field setting from a specified project in Asana. The request requires the project_gid as a path parameter, which is the globally unique identifier for the project. Optionally, you can include the opt_pretty query parameter to format the response in a more readable way. The request body must include the custom_field to be removed, specified within a data object. The response will return a 200 status code with an empty data object on success. In case of errors, various status codes such as 400, 401, 403, 404, and 500 may be returned, each with a detailed error message and help information.
Input Fields: Input Fields
Output Fields: Output Fields

Remove Tag from Task

ID: post_remove_tag_from_task
Operation: write
Entities: tag, task
Summary: The 'Remove Tag from Task' API endpoint allows users to remove a specific tag from a task in Asana. The request is made using the POST method to the URL 'https://app.asana.com/api/1.0/tasks/{task_gid}/removeTag', where 'task_gid' is the unique identifier of the task. The request headers must include 'accept' and 'content-type' set to 'application/json'. The path parameter 'task_gid' is required and specifies the task to operate on. An optional query parameter 'opt_pretty' can be included to format the response in a readable format. The request body must contain the 'tag' to be removed, specified by its 'gid'. On success, the API returns a 200 status code with an empty data object. In case of errors, appropriate status codes and error messages are returned, detailing the nature of the error and providing guidance on how to resolve it.
Input Fields: Input Fields
Output Fields: Output Fields

Remove Task from Project

ID: post_remove_task_from_project
Operation: write
Entities: project, task
Summary: The 'Remove Task from Project' API endpoint allows users to remove a specified task from a project in Asana. The task will still exist in the system but will no longer be associated with the specified project. The API requires the 'task_gid' as a path parameter to identify the task to be operated on. An optional query parameter 'opt_pretty' can be used to format the response in a more readable format. The request body must include the 'project' field specifying the project to remove the task from. On success, the API returns an empty data block with a 200 status code. In case of errors, appropriate error messages and codes are returned, detailing the nature of the error and providing guidance on how to resolve it.
Input Fields: Input Fields
Output Fields: Output Fields

Remove User from Team in Asana

ID: post_remove_user_from_team
Operation: write
Entities: team member, user, team
Summary: This API endpoint allows a user to remove themselves or another user from a specified team in Asana. The user making this call must be a member of the team. The request requires the 'team_gid' path parameter, which is the globally unique identifier for the team. Optionally, the 'opt_pretty' query parameter can be used to format the response in a more readable way. The request body must include a 'data' object with a 'user' field, which identifies the user to be removed. The response will return a 204 status code with an empty object on success. Various error responses (400, 401, 403, 404, 500) provide detailed error messages and guidance on how to resolve issues.
Input Fields: Input Fields
Output Fields: Output Fields

Remove User from Workspace or Organization

ID: post_remove_user_from_workspace
Operation: write
Entities: workspace, user, organization
Summary: This API endpoint allows an admin to remove a user from a specified workspace or organization in Asana. The user to be removed can be identified by their globally unique user ID or email address. The request requires the workspace_gid as a path parameter and optionally accepts a query parameter opt_pretty for formatted output. The request body must include a data object with a user field specifying the user to be removed. On success, the API returns a 204 status code with an empty data object. Possible error responses include 400 for malformed requests, 401 for authentication issues, 403 for access denial, 404 for unknown actions or non-existent objects, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Unlink Dependencies from a Task

ID: post_unlink_dependencies_from_task
Operation: write
Entities: task, dependency
Summary: This API endpoint allows you to unlink a set of dependencies from a specified task in Asana. The request requires the task_gid as a path parameter to identify the task to operate on. Optionally, you can include the opt_pretty query parameter to format the response in a more readable way. The request body must include a list of task gids that are to be unlinked as dependencies. On success, the API returns a 200 status code with an empty data object. In case of errors, various status codes such as 400, 401, 402, 403, 404, and 500 may be returned, each with a detailed error message and help information.
Input Fields: Input Fields
Output Fields: Output Fields

Unlink Dependents from a Task

ID: post_unlink_dependents_from_task
Operation: write
Entities: task, dependent
Summary: This API endpoint unlinks a set of dependents from a specified task in Asana. The request requires the task_gid as a path parameter to identify the task to operate on. Optionally, a query parameter opt_pretty can be used to format the response in a readable manner. The request body must include a list of dependent task gids to be removed. On success, the API returns an empty object with a 200 status code. Errors may occur due to missing or malformed parameters, invalid authentication, or access restrictions, and are returned with appropriate status codes and error messages.
Input Fields: Input Fields
Output Fields: Output Fields

Update an Existing Section in Asana

ID: put_update_existing_section
Operation: write
Entities: section, project, task
Summary: This API endpoint allows you to update an existing section in Asana by making a PUT request to the specified URL with the section's globally unique identifier (section_gid). The only field that can be updated is the 'name' field, and you can optionally specify the position of the section using 'insert_before' or 'insert_after'. The request can include optional query parameters to specify additional fields to be included in the response. The response returns the complete updated section record, including its globally unique identifier, resource type, name, creation time, and associated project details. Error responses provide detailed messages and guidance for troubleshooting.
Input Fields: Input Fields
Output Fields: Output Fields

Update an Existing Task in Asana

ID: put_update_existing_task
Operation: write
Entities: user, project, task
Summary: This API endpoint allows you to update a specific, existing task in Asana by making a PUT request to the URL for that task. You can update only the fields provided in the data block, leaving unspecified fields unchanged. It is recommended to specify only the fields you wish to change to avoid overwriting changes made by others. The request includes headers for content type and acceptance, path parameters for the task GID, optional query parameters for including additional fields, and a request body with the task data to update. The response returns the complete updated task record, including details such as task name, completion status, due dates, and custom fields.
Input Fields: Input Fields
Output Fields: Output Fields

Update Tag Properties in Asana

ID: put_update_tag_properties
Operation: write
Entities: workspace, tag, user
Summary: The Update Tag Properties in Asana API allows users to update the properties of a tag in Asana. The endpoint is accessed via a PUT request to https://app.asana.com/api/1.0/tags/{tag_gid}, where {tag_gid} is the globally unique identifier for the tag. The request can include optional query parameters to specify additional fields to include in the response. The request body must include the 'data' object with properties such as 'name', 'color', and 'notes' to update the tag. The response returns the complete updated tag record, including properties like 'gid', 'resource_type', 'name', 'color', 'notes', 'created_at', 'followers', 'workspace', and 'permalink_url'. The API handles various error responses, including 400 for malformed requests, 401 for authentication issues, 403 for access denial, 404 for non-existent resources, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Update Team in Asana Workspace

ID: put_update_team_in_asana_workspace
Operation: write
Entities: workspace, project, team
Summary: This API endpoint allows you to update a team within the current Asana workspace. The request requires the team_gid path parameter to specify which team to update. Optional query parameters can be used to include additional fields in the response. The request body must include the team data to be updated, such as the team's name, description, visibility, and various access levels. The response will return the updated team details. Possible error responses include 400 for malformed requests, 401 for authentication issues, 403 for access denial, 404 for non-existent resources, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Update Workspace Details

ID: put_update_workspace_details
Operation: write
Entities: workspace, project, task
Summary: This API endpoint allows you to update the details of a specific, existing workspace in Asana by making a PUT request to the specified URL. The only field that can be modified is the workspace's name. The request must include the workspace's globally unique identifier (workspace_gid) in the path parameters. Optional query parameters can be used to specify additional fields to include in the response. The request body must contain the updated workspace name within a 'data' object. The response will return the complete, updated workspace record. Possible response codes include 200 for success, 400 for malformed requests, 401 for authentication errors, 403 for access issues, 404 for non-existent resources, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields