Skip to content

Rootly (Independent Publisher)#4155

Open
aaronmah wants to merge 2 commits into
microsoft:devfrom
aaronmah:connector/rootly
Open

Rootly (Independent Publisher)#4155
aaronmah wants to merge 2 commits into
microsoft:devfrom
aaronmah:connector/rootly

Conversation

@aaronmah
Copy link
Copy Markdown

@aaronmah aaronmah commented Mar 12, 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.

Rootly — Independent Publisher Connector

Overview

Rootly is an AI-powered incident management platform that helps engineering teams declare, manage, and resolve incidents. This connector enables Power Automate makers to create and track incidents, manage alerts, and follow up on post-incident action items — connecting Rootly's incident lifecycle to the broader Microsoft ecosystem including Teams, Azure DevOps, SharePoint, and Planner.

This connector provides action operations only. Polling triggers for incidents and alerts are planned for a future version.

Publisher

Aaron Mah

Operations (11 total)

Operation Type Description
List Incidents Action Retrieves a list of incidents with optional filtering by status and severity
Create Incident Action Creates a new incident with a title and severity
Get Incident Action Retrieves the details of a specific incident by its ID
Update Incident Action Updates an existing incident's status, severity, or other fields
List Severities Action Retrieves all severity levels defined in the organization
List Services Action Retrieves all services from the service catalog
List Alerts Action Retrieves a list of alerts with optional filtering
Create Alert Action Creates a new alert from an external source
List Action Items Action Retrieves all action items for a specific incident
Create Action Item Action Creates a new action item for an incident
List Teams Action Retrieves all teams defined in the organization

Test Results

  • 11/11 operations tested successfully in PA environment
  • Swagger validation passed (validate-connector.js + swagger-cli)
  • 3 end-to-end scenario flows validated
  • Screenshot validation ✅ 4/4 screenshots verified (green checkmarks present, no red failure indicators)

Test Tab — All Operations

All operations passed

Scenario Flows

Scenario 1: Incident Report to Rootly
A Microsoft Forms submission triggers incident creation in Rootly with severity lookup, then posts a Teams notification.

Scenario 1 Run Success

Scenario 2: Incident Digest to Teams
A scheduled recurrence lists active incidents, formats an HTML digest table, and posts to a Teams channel.

Scenario 2 Run Success

Scenario 3: Action Items Review
A daily recurrence chains List Incidents → List Action Items → filters open items → formats and posts to Teams.

Scenario 3 Run Success

@aaronmah aaronmah mentioned this pull request Mar 12, 2026
10 tasks
@aaronmah aaronmah marked this pull request as ready for review March 13, 2026 01:20
@aaronmah aaronmah requested a review from a team as a code owner March 13, 2026 01:20
@vmanoharas
Copy link
Copy Markdown
Contributor

Hi @aaronmah,

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

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