Skip to content

Workast (Independent Publisher)#4150

Draft
aaronmahbuild wants to merge 4 commits into
microsoft:devfrom
aaronmah:connector/workast
Draft

Workast (Independent Publisher)#4150
aaronmahbuild wants to merge 4 commits into
microsoft:devfrom
aaronmah:connector/workast

Conversation

@aaronmahbuild
Copy link
Copy Markdown

@aaronmahbuild aaronmahbuild commented Mar 8, 2026

  • 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 attest that 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.

Workast — Independent Publisher Connector

Overview

Workast is a lightweight task and project management tool designed for messaging-platform teams. This connector enables Power Automate users to create, assign, and track tasks across Workast spaces — bridging Microsoft Teams workflows with Workast's task management capabilities. It supports 11 operations covering users, spaces, tasks, lists, members, and comments. Auth uses API Key (Bearer token).

Publisher

Aaron Mah

Operations (11 total)

Operation Type Description
Get Current User Action Retrieves profile information for the authenticated user
List Spaces Action Returns all spaces accessible to the authenticated user
Get a Space Action Retrieves details of a specific space by its ID
List Tasks in Space Action Returns tasks within a specific space with filtering and pagination
Create a Task Action Creates a new task in the specified space
Get a Task Action Retrieves full details of a single task by its ID
Update a Task Action Updates an existing task's fields (title, description, dates)
Delete a Task Action Permanently removes a task by its ID
List Lists in Space Action Returns all lists (columns/sections) within a specific space
List Members in Space Action Returns all members of a specific space
Add Comment to Task Action Adds a text comment to an existing task

Test Results

  • 7/7 core operations tested successfully in PA environment (Community)
  • Swagger validation passed (paconn validate equivalent — exit code 0)
  • 3 end-to-end scenario flows validated
  • UpdateTask excluded from PA testing — API returns 404 on both PUT/PATCH; operation included in swagger for future API fixes
  • ListListsInSpace, ListMembersInSpace, AddCommentToTask — additional operations added to swagger; verified at API level

Test Tab — All Operations

All operations passed — 7/7 green checkmarks

Scenario Flows

Scenario 1: Teams Message → Workast Task
Uses: ListSpaces, CreateTask, Teams PostMessage
Scenario 1 — Run Success

Scenario 2: Daily Task Digest to Teams
Uses: ListSpaces, ListTasksInSpace, Teams PostMessage
Scenario 2 — Run Success

Scenario 3: Form Submission → Task with Comment
Uses: ListSpaces, CreateTask, GetTask, Teams PostMessage
Scenario 3 — Run Success

@aaronmahbuild aaronmahbuild requested a review from a team as a code owner March 8, 2026 11:51
@aaronmahbuild
Copy link
Copy Markdown
Author

Test Screenshots

Test Tab — All Operations (7/7 green checkmarks)

All operations passed

Scenario 1: Teams Message → Workast Task

Uses: ListSpaces, CreateTask, Teams PostMessage
Scenario 1 — Run Success

Scenario 2: Daily Task Digest to Teams

Uses: ListSpaces, ListTasksInSpace, Teams PostMessage
Scenario 2 — Run Success

Scenario 3: Form Submission → Task with Comment

Uses: ListSpaces, CreateTask, GetTask, Teams PostMessage
Scenario 3 — Run Success

@aaronmahbuild aaronmahbuild marked this pull request as draft March 9, 2026 16:37
@vmanoharas
Copy link
Copy Markdown
Contributor

Hi @aaronmahbuild,

Thank you for submitting the connector and it is still in work in progress stage, please let us know once complete.

However, our Independent publisher connector certification process has been changed. Please follow the instructions from the below links and submit connector package.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip

@vmanoharas
Copy link
Copy Markdown
Contributor

Hi @aaronmahbuild,

Thank you for submitting the connector. However, our Independent publisher connector certification process has been changed. Please follow the instructions from the below links and submit connector package.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip

Additionally, this connector is in draft version, please change it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants