Rootly (Independent Publisher)

[aaronmahbuild]

• 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 (14 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
Acknowledge Alert	Action	Acknowledges an open alert (⚠️ known issue — see below)
Resolve Alert	Action	Resolves an alert (⚠️ known issue — see below)
List Action Items	Action	Retrieves all action items for a specific incident
Create Action Item	Action	Creates a new action item for an incident
Update Action Item	Action	Updates an existing action item (⚠️ known issue — see below)
List Teams	Action	Retrieves all teams defined in the organization

Known Issues (3 operations)

Operation	Issue	Details
Acknowledge Alert	HTTP 404	Alert sub-action endpoints may require specific alert state or plan tier. Path confirmed correct per Rootly API docs.
Resolve Alert	HTTP 404	Same root cause as Acknowledge Alert.
Update Action Item	HTTP 404	PATCH on nested action item path returns 404. API may not support PATCH for action items.

These operations are included for completeness and will work once Rootly addresses the underlying API behavior. The remaining 11 operations all pass successfully.

Test Results

• 11/14 operations tested successfully in PA environment (3 are documented known issues)
• Swagger validation passed (validate-connector.js + swagger-cli)
• 3 end-to-end scenario flows validated

Test Tab — All Operations

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 2: Incident Digest to Teams
A scheduled recurrence lists active incidents, formats an HTML digest table, and posts to a Teams channel.

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

[aaronmah]

This PR has been superseded by #4155 (from aaronmah:connector/rootly).

The connector was updated: 3 operations that returned HTTP 404 (acknowledgeAlert, resolveAlert, updateActionItem) were removed. The connector now has 11 clean operations with 11/11 passing and 3/3 scenario flows validated.

Please review PR #4155 instead.

[aaronmah]

Closing in favor of #4155 (updated connector with 11 operations, submitted from aaronmah fork).