How to parse and use the JSON data that is sent by webhook to a teams channel?

(1) Share

Report

Posted on by SS-03041020-0

Dear all

I am at a loss and need help.

I try to send a webhook (with JSON data) from an external source to a teams channel. It works as I do get a message in the teams channel from the external source, however, I can't parse and use the JSON data trasmitted (to post it in the teams channel message).

The interesting data I want to use in the teams message is in the body/text object in the webhook - and optimally I would like to use the different objects within said data to design a message into the teams channel.
But I can't even put the whole JSON line in the message to begin with (let alone parse it for the individual pieces of information, which is the goal I am striving for).

Can you help me figure out what I am missing?

My Flow:

See attached file

My JSON configuration/data (somewhat obfuscated):

The original JSON info from the webhook (the "body" being the interesting part for me):

{
    "headers": {
        "Accept": "*/*",
        "Host": "obfuscated",
        "Max-Forwards": "10",
        "X-ARR-LOG-ID": "obfuscated",
        "CLIENT-IP": "obfuscated",
        "DISGUISED-HOST": "obfuscated",
        "X-SITE-DEPLOYMENT-ID": "obfuscated",
        "WAS-DEFAULT-HOSTNAME": "obfuscated",
        "X-Forwarded-Proto": "https",
        "X-AppService-Proto": "https",
        "X-ARR-SSL": "obfuscated",
        "X-Forwarded-TlsVersion": "1.3",
        "X-Forwarded-For": "obfuscated",
        "X-Original-URL": "obfuscated",
        "X-WAWS-Unencoded-URL": "obfuscated",
        "Content-Length": "194",
        "Content-Type": "application/json"
    },
    "body": {
        "text": "<pre>{\n \"content\": \"obfuscated\".\n \"message\": \"\",\n \"time\": \"%%log_time%%\",\n \"username\": \"%%log_user%%\",\n \"source IP\": \"%%log_srcip%%\"\n}</pre>"
    }
}

The JSON information in the "parse JSON" action:

raw inputs:
{
    "content": {
        "text": "<pre>{\n \"content\": \"obfuscated\".\n \"message\": \"\",\n \"time\": \"%%log_time%%\",\n \"username\": \"%%log_user%%\",\n \"source IP\": \"%%log_srcip%%\"\n}</pre>"
    },
    "schema": {
        "type": "object",
        "properties": {
            "content": {
                "type": "string"
            },
            "message": {
                "type": "string"
            },
            "time": {
                "type": "string"
            },
            "username": {
                "type": "string"
            },
            "source IP": {
                "type": "string"
            }
        }
    }
}


raw ouputs:
{
    "body": {
        "text": "<pre>{\n \"content\": \"obfuscated\".\n \"message\": \"\",\n \"time\": \"%%log_time%%\",\n \"username\": \"%%log_user%%\",\n \"source IP\": \"%%log_srcip%%\"\n}</pre>"
    }
}

Categories:

Building flows

flow1_obfuscated.png

I have the same question (0)

All responses (6)

Answers (1)

Suggested answer

SwatiSTW 741 Super User 2025 Season 2 on at

Like (0)

Report

The problem is that the JSON you want is inside a string field called text, and it includes <pre> tags. So Power Automate can't directly parse it. You need to extract that string, clean it, and parse it again.

1. First Parse JSON to extract the text field from the incoming webhook
Schema to use:
 {
 "type": "object",
 "properties": {
 "text": {
 "type": "string"
 }
 }
 }
2. Add a Compose action to remove <pre> and </pre> from the text
Expression to use:
 replace(replace(body('Parse_JSON')?['text'], '<pre>', ''), '</pre>', '')
3. Add a second Parse JSON action, use output from the Compose as input
Content field:
 outputs('Compose')
Schema to use:
 {
 "type": "object",
 "properties": {
 "content": { "type": "string" },
 "message": { "type": "string" },
 "time": { "type": "string" },
 "username": { "type": "string" },
 "source IP": { "type": "string" }
 }
 }
4. In the Teams message action, use dynamic content from the second Parse JSON
Example message:
 New Log Entry 
 User: @{outputs('Parse_JSON_2')?['username']} 
 Message: @{outputs('Parse_JSON_2')?['message']} 
 Time: @{outputs('Parse_JSON_2')?['time']} 
 Source IP: @{outputs('Parse_JSON_2')?['source IP']}

This will show each field correctly in the Teams message.

Was this reply helpful? Yes No
SS-03041020-0 12 on at

Like (0)

Report

@SwatiSTW

Thank you very much for your reply and your advice - thanks to you I am several steps further.

Unfortunately, I am still making a mistake along the path as now the second "parse json" fails.

In the "componse" action I only have one single configuration available, which is called "inputs". I put in the expression you mentioned = replace(replace(body('Parse_JSON')?['text'], '<pre>', ''), '</pre>', '').

However, I have the feeling this wasn't correct on my part.

The error message now reads:

InvalidJSON. The 'content' property of actions of type 'ParseJson' must be valid JSON. The provided value cannot be parsed: 'Unexpected character encountered while parsing value: o. Path '', line 0, position 0.'.

And the raw output of the "compose" action reads as follows:

"replace(replace(body('Parse_JSON')?['text'], '<pre>', ''), '</pre>', '')"

Do you have any advice?

P.S.:

The output of the first "parse json" looks extremly promising:

<pre>{
"content": "obfuscate".
"message": "",
"time": "%%log_time%%",
"username": "%%log_user%%",
"source IP": "%%log_srcip%%"
}</pre>

Was this reply helpful? Yes No
Chriddle 8,434 Super User 2025 Season 2 on at

Like (0)

Report
The JSON within the property "text" is invalid.

Assuming it is an editing error and after cleaning:

Compose: The original JSON

Parse JSON:

Content:

json( slice( body('Compose')['text'], 5, -6 ) )

Schema:

{ "type": "object", "properties": { "content": { "type": "string" }, "message": { "type": "string" }, "time": { "type": "string" }, "username": { "type": "string" }, "source IP": { "type": "string" } } }

Was this reply helpful? Yes No
SS-03041020-0 12 on at

Like (0)

Report
Dear @Chriddle and @SwatiSTW

As suggested by @Chriddle I added another "parse json" action after the "compose" action with the configuraiton that was suggested and with the following result (raw input):

{ "content": "json(\n\tslice(\n\t\tbody('Compose')['text'],\n\t\t5,\n\t\t-6\n\t)\n)", "schema": { "type": "object", "properties": { "content": { "type": "string" }, "message": { "type": "string" }, "time": { "type": "string" }, "username": { "type": "string" }, "source IP": { "type": "string" } } } }

While I was able to save that flow in power automate, it now gives me the following error message when the flow is triggered:

InvalidJSON
The 'content' property of actions of type 'ParseJson' must be valid JSON. The provided value cannot be parsed: 'Unexpected character encountered while parsing value: j. Path '', line 0, position 0.'.

It appears that the "content" part of the second "parse json" can't be a json slice operation? Or am I missing some special flag needed for the slice json operation to be valid in the "content" part of the "parse json" action?

Again, the output of the compose is promising (it just has the <pre> tags still in it):

"<pre>{\n \"content\": \"AdminLogin on Fortigate\".\n \"message\": \"\",\n \"time\": \"%%log_time%%\",\n \"username\": \"%%log_user%%\",\n \"source IP\": \"%%log_srcip%%\"\n}</pre>"

Was this reply helpful? Yes No
Verified answer

Chriddle 8,434 Super User 2025 Season 2 on at

Like (0)

Report

The problem is that the text isn't valid JSON.
Instead of a comma, there's a period.

I fixed this in advance in last week's proposed solution.

Can you fix the input?

Was this reply helpful? Yes No
SS-03041020-0 12 on at

Like (0)

Report

@Chriddle

Please accept my sincere apologies - you are absolutely right and I have missed that in your post.

I corrected the input (I indeed made a typo - should have been a comma) and from there things look amazingly better with all your input.

Thanks to you I am busy with finetuning, but not with troubleshooting anymore.

To all, thanks a lot for your help - it is very much appreciated

Was this reply helpful? Yes No