added new script to export flows with http triggers#870
Merged
Conversation
Member
|
Hey @siddharth-vaghasia awesome script and quite timely due to the Microsoft changes. Thank you for sharing with the community. |
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
2 participants
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.
This PR adds a new sample script to identify all Power Automate flows using the trigger “When an HTTP request is received” and extract their callback URLs.
Since the Office 365 CLI currently does not return callback URLs directly, the script leverages:
m365 flow list command to enumerate flows
Custom API calls to api.flow.microsoft.com to fetch trigger details and callback URLs
This script is useful for organizations auditing their flows after the recent Power Automate trigger URL changes.