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.
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.
Hi @Jakob Gillinger could you kindly share the solution since I have this problem ?
About %2F -> / i resolved but still not works.
Thanks a lot in advance.
Roberto
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm sorry, but that issue looks unrelated - after the fix I've mentioned, I had no further problems with my workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Roberto Ialino,
I also struggled with somehow converting the Jira Connector to Power Automate.
The solution can be adapted:
{
"$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>"
}
]
}
]
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.