Asana (Independent Publisher)

[aaronmahbuild]

Asana — Independent Publisher Connector

Overview

Asana is a work management platform used by millions of teams worldwide. This independent publisher connector extends the existing certified Asana connector with 13 complementary operations that close the biggest capability gaps in Power Automate — including task updates, search, section management, subtasks, tags, and project status reporting. It does not duplicate any operations from the certified connector; instead, it fills the gaps that prevent PA makers from building advanced Asana workflows.

• I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
• I attest that the connector works and I verified by deploying and testing all the operations.
• I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• I attest that I have added response schemas to my actions, unless the response schema is dynamic.
• I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.
• I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
• Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

Publisher

Aaron Mah — GitHub

Prerequisites

• An Asana account (free or paid)
• An Asana Personal Access Token (PAT) — create one here
• Search Tasks requires a paid Asana plan (Premium, Business, or Enterprise)

Operations (13 total)

#	Operation	Type	Description
1	Update Task	Action	Updates an existing task (name, assignee, due date, notes, completion status)
2	List Tasks in Project	Action	Returns tasks in a project with rich field support via opt_fields
3	Search Tasks	Action	Searches tasks in a workspace with advanced filters (text, assignee, dates, tags)
4	List Sections in Project	Action	Returns all sections (kanban columns) in a project
5	Add Task to Section	Action	Moves a task to a specific section/workflow stage
6	Create Subtask	Action	Creates a subtask under an existing parent task
7	List Subtasks	Action	Returns all subtasks of a parent task
8	List Projects	Action	Returns projects in a workspace, optionally filtered by team
9	Add Tag to Task	Action	Adds an existing tag to a task
10	List Tags in Workspace	Action	Returns all tags in a workspace
11	Create Status Update	Action	Creates a project/portfolio/goal status update
12	List Status Updates	Action	Returns status updates for a project/portfolio/goal
13	Delete Task	Action	Permanently deletes a task

Test Results

• 13/13 API operations validated against live Asana API
• 13/13 operations tested successfully in PA Test tab
• 3/3 end-to-end scenario flows validated in Power Automate
• paconn validate passed

Test Tab — All Operations

Scenario Flows

Scenario 1: Daily Sprint Digest to Teams
Recurrence → List Sections → List Tasks in Project → Compose → Post to Teams

Scenario 2: Forms Request → Subtask Breakdown
Forms trigger → Search Tasks → Create Subtask ×3 → Teams notification

Scenario 3: GitHub PR Merged → Update Asana Task & Move to Done
GitHub trigger → Update Task → List Sections → Add to Section → Teams notification

[vmanoharas]

Hi @aaronmahbuild,

Thank you for your interest in submitting the Asana connector under the Independent Publisher (IP) program.

After review, we’re unable to proceed with this submission because Asana already exists as an official Microsoft connector in the Power Platform connector catalog.

As per the Independent Publisher certification policy, new Independent Publisher connectors cannot be created for services that already have an existing Microsoft or certified connector.
This requirement is documented publicly here: https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#step-1-verify-connector-isnt-already-built