Skip to content

fix: aligned flow detection and API urls after recent changes - #11

Merged
rithala merged 2 commits into
masterfrom
hotfix/new-url-schema
Mar 5, 2026
Merged

fix: aligned flow detection and API urls after recent changes#11
rithala merged 2 commits into
masterfrom
hotfix/new-url-schema

Conversation

@rithala

@rithala rithala commented Mar 5, 2026

Copy link
Copy Markdown
Owner

No description provided.

Power Automate migrated API calls from *.api.flow.microsoft.com to
*.api.powerplatform.com with a new path format and API version. This
broke flow detection, token capture, and all API operations.

- Add powerplatform.com to webRequest listener and host_permissions
- Extract flow IDs from new /powerautomate/flows/{id} path format
- Resolve environment IDs from tab URLs (encoded in subdomain in new API)
- Track API URLs and tokens per-tab to support multiple environments
- Use api-version=1 for new API, keep api-version=2016-11-01 for legacy
- Route flow GET/PATCH through new API, validation through legacy API
- Enable extension action per-tab instead of globally
- Remove jwt-decode dependency (no longer tracking token expiry)
@rithala
rithala merged commit 4be5eb7 into master Mar 5, 2026
1 check failed
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