Skip to content

FireHydrant (Independent Publisher)#4145

Draft
aaronmahbuild wants to merge 10 commits intomicrosoft:devfrom
aaronmah:connector/firehydrant
Draft

FireHydrant (Independent Publisher)#4145
aaronmahbuild wants to merge 10 commits intomicrosoft:devfrom
aaronmah:connector/firehydrant

Conversation

@aaronmahbuild
Copy link
Copy Markdown

@aaronmahbuild aaronmahbuild commented Mar 6, 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 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.

FireHydrant — Independent Publisher Connector

Overview

FireHydrant is a leading incident management platform for engineering and DevOps teams. This connector enables you to manage the full incident lifecycle — declare, track, update, resolve, and close incidents — directly from Power Automate. Coordinate response teams, post status updates, and build automated workflows that keep your organization informed during incidents.

Publisher

Aaron Mah

Operations (12 total)

Operation Type Description
List Incidents Action Retrieves a list of incidents, optionally filtered by status, severity, or search query
Get Incident Action Retrieves the full details of a specific incident by its ID
Create Incident Action Declares a new incident with the specified name, severity, and optional details
Update Incident Action Updates fields of an existing incident (severity, description, customer impact)
List Severities Action Retrieves all severity levels configured in the organization
List Teams Action Retrieves all teams configured in the organization
Create Incident Note Action Adds a status update note to an incident's timeline
List Incident Timeline Action Retrieves the timeline of events for a specific incident
Resolve Incident Action Marks an incident as resolved, setting the resolved milestone timestamp
Close Incident Action Closes an incident, marking it as fully complete
List Users Action Retrieves all users in the organization
Get Current User Action Retrieves the profile of the currently authenticated bot user

Test Results

  • 12/12 operations tested successfully in PA environment (Community)
  • Swagger validation passed (validate-connector.js, exit code 0)
  • All 12 operations verified with green checkmarks in the Custom Connector test tab
  • 3/3 end-to-end scenario flows validated successfully
  • Auth type: API Key (Bearer Token)

Test Tab — All Operations (12/12 Green)

All 12 operations passed with green checkmarks in Custom Connector test tab

Connection Verified

Connection ready — API key authenticated and connected

Connector Overview

Connector overview showing all 12 operations

Scenario Flows (3/3 Passed)

End-to-end scenario flows validated in Power Automate using the FireHydrant connector with Microsoft Teams.


Scenario 1: Incident Declaration

Creates a new incident with severity lookup and team assignment, then posts an alert to Microsoft Teams.

Operations used: List Severities, List Teams, Create Incident, Get Incident, Post to Teams

Scenario 1 Designer

Scenario 1 Run Success — all 5 actions green


Scenario 2: Incident Status Update

Lists active incidents, retrieves timeline events for the latest incident, and posts a summary to Teams.

Operations used: List Incidents, List Incident Timeline, Post to Teams

Scenario 2 Designer

Scenario 2 Run Success — all 5 actions green


Scenario 3: Weekly Incident Digest

Lists all active incidents and the current user, formats a digest HTML table, and posts a weekly summary to Teams.

Operations used: List Incidents, Get Current User, Post to Teams

Scenario 3 Designer

Scenario 3 Run Success — all 6 actions green

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.

2 participants