FireHydrant (Independent Publisher)#4145
Draft
aaronmahbuild wants to merge 10 commits intomicrosoft:devfrom
Draft
FireHydrant (Independent Publisher)#4145aaronmahbuild wants to merge 10 commits intomicrosoft:devfrom
aaronmahbuild wants to merge 10 commits intomicrosoft:devfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
apiDefinition.swagger.json, by runningpaconn validatecommand.apiProperties.jsonhas a valid brand color and doesn't use an invalid brand color,#007ee5or#ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.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)
Test Results
Test Tab — All Operations (12/12 Green)
Connection Verified
Connector Overview
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 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 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