Microsoft Power-Automate url pattern changed

[LaFeev]

https://github.com/caronc/apprise/blob/dca2f7aad827f5d86b9e9cdfd8dea869f98f2fae/apprise/plugins/workflows.py#L383C13-L383C57

The structure of the power-automate webhook URL as issued to me through MS Teams, is different from the one referenced above. The result is a 404 "The request URI --- does not match any known API routes".

My webhook (anonymized): https://default9876a89769878976b9786d76.73.environment.api.powerplatform.com:443/powerautomate/automations/direct/workflows/09870a09879087d987987b78/triggers/manual/paths/invoke/?api-version=1&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=fKJHT897_0987HK789687DFK7698DFDFjh989

Existing pattern:
https://HOST:PORT/workflows/ABCD/triggers/manual/path/...sig=DEFG

New pattern:
https://HOST:PORT/powerautomate/automations/direct/workflows/ABCD/triggers/manual/path/...sig=DEFG

I took a stab at adding a query param for use with the shorthand URLs, and implemented a flag for power automation so that a different URL pattern could be used if desired. Default behavior remains same as existing code. I'll create a PR shortly.

[chusiang]

Thank you for fix this, I have same problem now.

[alphafalcon]

Is there a rough time frame for a release with the fix?

I'm trying to judge whether trying to build the apprise-api container with the fix is worth the time investment.

[caronc]

I appologize for the delay; the reasons are entirely personal. That said, today is a holiday in Canada. I've finally got some time to myself. I'll bundle up a small release (as not much has happened to the code base - again entirely my fault). But at least it will address this concern for you all. v1.9.5 will hopefully be visible to you all in the next couple of hours. 🙏

Edit: Release v1.9.5 has been prepared and includes this update in it

[gdha]

@caronc @LaFeev Testing apprise v1.9.5 (RPM build from sources) with MS Teams Workflows URL.

• Using the full workflow URL works fine.
• Using the workflows://default3ac94b33913548219502eafda6592a.35.environment.api.powerplatform.com:443/$workflow/$signature syntax fails with a message:
  WARNING - Failed to send Workflows notification: Page not found., error=404
  Is the syntax above of the short workflow naming wrong?

[LaFeev]

@caronc @LaFeev Testing apprise v1.9.5 (RPM build from sources) with MS Teams Workflows URL.

• Using the full workflow URL works fine.
• Using the workflows://default3ac94b33913548219502eafda6592a.35.environment.api.powerplatform.com:443/$workflow/$signature syntax fails with a message:
  WARNING - Failed to send Workflows notification: Page not found., error=404
  Is the syntax above of the short workflow naming wrong?

At the moment you'll need to refer to the PR for documentation of the new feature #1407. If you use the shorthand URL you need to supply a query parameter as the power-automate URL pattern isn't default behavior.

i.e. workflows://host:port/wfid/sig/?pa=yes

[chusiang]

Thanks @LaFeev,

Just record my workflows line changes.

- workflow_url = "workflows://prod-18.westus.logic.azure.com:443/34da*************************cf5/soSL*************************************q4/"
+ workflow_url = "workflows://default1107***********************6f7.e6.environment.api.powerplatform.com:443/34da*************************cf5/Cn9**************************************tw/?pa=yes"