Webhook not received by Power Automate endpoint

Jakob Gillinger
Contributor
June 6, 2023

I've created a webhook targeting an endpoint provided by a Power Automate workflow using the "When a HTTP request is received"-trigger. However, performing an action assigned to the webhook does not trigger the flow.

I've set up an identical webhook targeting webhook.site - a service used for testing webhooks - and that one works perfectly fine. Since the service logs the received request, I also copied it, removed the "host"-header and sent it to the endpoint using Thunder Client, which did trigger the flow.

I've had a conversation with a Power Automate support member, and they said that HTTP requests sent by webhooks are different from requests sent by clients. I can't really tell what makes it different, but I also can't tell what request is being sent to the endpoint exactly.

1 answer

1 accepted

4 votes
Answer accepted
Jakob Gillinger
Contributor
June 6, 2023

After a call with someone from Power Automate support, I was able to find the problem: The URL provided by Power Automate already had / encoded as %2F. After changing them back to /, the webhook triggered the flow successfully.

Roberto Ialino
Contributor
July 18, 2024

Hi @Jakob Gillinger could you kindly share the solution since I have this problem ?

https://community.atlassian.com/t5/Jira-questions/Webhook-not-received-by-MS-Power-Automate-endpoint-Workflow-app/qaq-p/2757377

 About %2F -> / i resolved but still not works.

Thanks a lot in advance.

Roberto

Jakob Gillinger
Contributor
July 18, 2024

I'm sorry, but that issue looks unrelated - after the fix I've mentioned, I had no further problems with my workflow.

Roberto Ialino
Contributor
July 18, 2024

Many thanks for the reply.
Yes I know it's not related unfortunately, but can you share your solution, I want to try if feasible.

For example, what did you insert inside these two red arrows?

Many thanks in advance

Roberto

 

http flow.png

Philipp Thyme
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 29, 2024

Hey @Roberto Ialino

I also struggled with somehow converting the Jira Connector to Power Automate.

The solution can be adapted:

  1. Use the trigger "When a Teams webhook request is received" instead of "When a HTTP request is received"
  2. Replace %2F with / in the webhook url
  3. Don't add any action yet, and use the webhook in Jira. Try to trigger it with a new issue or sth else.
  4. Afterwards check the successful triggered flow and Copy the output of the trigger
  5. Click edit and add the action "Parse JSON"
  6. Content: triggerBody()
    Scheme: <this is individual ... generate it from sample data ... paste the output you should have in the clipboard>
  7. Add the action "Compose"
    Content: <create an adaptive card of your choice, e.g.>
    • {
      "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
      "type": "AdaptiveCard",
      "version": "1.3",
      "body": [
      {
      "type": "TextBlock",
      "text": "[<key>: <summary>](https://jira/browse/)",
      "weight": "Bolder",
      "wrap": true,
      "color": "Accent",
      "size": "Medium"
      },
      {
      "type": "FactSet",
      "facts": [
      {
      "title": "Priority:",
      "value": "<name>"
      },
      {
      "title": "Issue Type:",
      "value": "<name>"
      },
      {
      "title": "Reporter:",
      "value": "<displayName>"
      },
      {
      "title": "Status:",
      "value": "<name>"
      }
      ]
      }
      ]
      }
  8. Add the action "Post card in a chat or channel" and use the Compose element
Like John Sheetz likes this
Jeremiah
Contributor
September 26, 2024

Nice find! You'll find them hidden in the query params, not the main URL. For example, my URL was fine until the query param

sp=%2Ftriggers%2Fmanual%2Frun

which I then changed to 

sp=/triggers/manual/run

and it worked! Thanks a lot for finding this!

Like John Sheetz likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events