Description We are experiencing an issue with the Incoming Webhook trigger in Confluence Cloud Automation (Webhook version 2.0). The webhook endpoint successfully receives the HTTP POST request and returns HTTP 200, and the automation flow is triggered successfully. However, the request payload is not available within the automation flow through the documented {{webhookData}} smart value. Environment * Confluence Cloud – Enterprise * Confluence Automation / Flows * Trigger: Incoming Webhook * Audit log reports: Webhook version 2.0 * Endpoint: api-private.atlassian.com/automation/webhooks/confluence/... Request We send the following JSON payload: { "repository": "ndt_fe", "content": "Test Frontend documentation from webhook" } Request headers include: Content-Type: application/json X-Automation-Webhook-Token: The webhook returns: HTTP/2 200 and the automation is successfully triggered. Expected behaviour The following smart values should resolve from the incoming POST payload: {{webhookData}} {{webhookData.repository}} {{webhookData.content}} For example: {{webhookData.repository}} should return: ndt_fe Actual behaviour All webhook smart values resolve to empty values. A Log action produces: webhookData=[] repository=[] content=[] As a result, conditions such as: {{webhookData.repository}} equals ndt_fe fail because the first value resolves to empty. Troubleshooting already performed We have verified that: * The webhook endpoint returns HTTP 200. * The Confluence automation flow is triggered successfully. * The Audit Log identifies the trigger as Webhook version 2.0. * curl --trace-ascii confirms that the JSON request body is actually transmitted to Atlassian. * Content-Type: application/json was explicitly specified. * {{webhookData}} , {{webhookData.repository}} , and {{webhookData.content}} were tested. * {{webhookResponse.body}} was also tested and resolves empty. * We also tested application/x-www-form-urlencoded using --data-urlencode ; the webhook still triggers but the values remain empty. * The Incoming Webhook audit-log entry does not display the request payload; it only displays Webhook version 2.0.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Confluence Automation Incoming Webhook v2.0 does not expose POST payload through {{webhookData}}

Adnan Karbelkar_ Vodafone

Description

We are experiencing an issue with the Incoming Webhook trigger in Confluence Cloud Automation (Webhook version 2.0).

The webhook endpoint successfully receives the HTTP POST request and returns HTTP 200, and the automation flow is triggered successfully. However, the request payload is not available within the automation flow through the documented {{webhookData}} smart value.

Environment

Confluence Cloud – Enterprise
Confluence Automation / Flows
Trigger: Incoming Webhook
Audit log reports: Webhook version 2.0
Endpoint: api-private.atlassian.com/automation/webhooks/confluence/...

Request

We send the following JSON payload:

<span>{
  "repository": "ndt_fe",
  "content": "Test Frontend documentation from webhook"
}</span>

Request headers include:

<span>Content-Type: application/json
X-Automation-Webhook-Token: <secret></span>

The webhook returns:

<span>HTTP/2 200</span>

and the automation is successfully triggered.

Expected behaviour

The following smart values should resolve from the incoming POST payload:

<span>{{webhookData}}
{{webhookData.repository}}
{{webhookData.content}}</span>

For example:

<span>{{webhookData.repository}}</span>

should return:

<span>ndt_fe</span>

Actual behaviour

All webhook smart values resolve to empty values.

A Log action produces:

<span>webhookData=[]
repository=[]
content=[]</span>

As a result, conditions such as:

<span>{{webhookData.repository}} equals ndt_fe</span>

fail because the first value resolves to empty.

Troubleshooting already performed

We have verified that:

The webhook endpoint returns HTTP 200.
The Confluence automation flow is triggered successfully.
The Audit Log identifies the trigger as Webhook version 2.0.
curl --trace-ascii confirms that the JSON request body is actually transmitted to Atlassian.
Content-Type: application/json was explicitly specified.
{{webhookData}}, {{webhookData.repository}}, and {{webhookData.content}} were tested.
{{webhookResponse.body}} was also tested and resolves empty.
We also tested application/x-www-form-urlencoded using --data-urlencode; the webhook still triggers but the values remain empty.
The Incoming Webhook audit-log entry does not display the request payload; it only displays Webhook version 2.0.

Accepted answers

Trudy P Claspill

Hello @Adnan Karbelkar_ Vodafone

Welcome to the Atlassian community.

Can you provide a screen image of your entire rule? Sometimes there is a context issue that isn't obvious.

Can you show us all the settings in your Incoming Webhook trigger?

How are you calling the webhook; through Postman, through a python script, through a custom integration provided by another application, ...?

Have you confirmed with an independent tool that there are no hidden characters in your JSON?

According to the following Atlassian article you should try webhookResponse on place of webhookData

https://support.atlassian.com/jira/kb/use-incoming-webhooks-with-smart-values-in-automation-for-jira/

All comments

Trudy P Claspill

Hello @Adnan Karbelkar_ Vodafone

Welcome to the Atlassian community.

Can you provide a screen image of your entire rule? Sometimes there is a context issue that isn't obvious.

Can you show us all the settings in your Incoming Webhook trigger?

How are you calling the webhook; through Postman, through a python script, through a custom integration provided by another application, ...?

Have you confirmed with an independent tool that there are no hidden characters in your JSON?

According to the following Atlassian article you should try webhookResponse on place of webhookData

https://support.atlassian.com/jira/kb/use-incoming-webhooks-with-smart-values-in-automation-for-jira/

Aron Gombas _Midori_

I think it is a known issue that others have reported with Confluence Cloud Automation incoming webhooks.

Here is one thing you can try.

Pass your data as URL query parameters instead of in the POST body. Append the values directly to your webhook URL like this:

https://api-private.atlassian.com/automation/webhooks/confluence/YOUR_WEBHOOK_ID?repository=ndt_fe&content=Test+Frontend+documentation

Then access them with {{webhookData.repository}} and {{webhookData.content}}.

Adnan Karbelkar_ Vodafone

Thanks Aron. I tried your suggestion and passed the values directly as URL query parameters, for example:

This is my Automation flow.

This is the command I run from the terminal using curl. ( I have redacted the URL and Webhook Token )

curl -sS -i \
   -X POST \
   -H 'X-Automation-Webhook-Token: *********************** \
      'https://api-private.atlassian.com/automation/webhooks/confluence/a/c?repository=ndt_fe&amp;content=Test Frontend documentation from webhook by Adnan' \
   -w '\n\nHTTP_STATUS=%{http_code}\n'

I get the following response status for the API .

HTTP/2 200 
content-type: application/json
content-length: 0
date: Fri, 14 Aug 2026 18:11:52 GMT
server: AtlassianEdge
x-envoy-attempt-count: 1
cache-control: no-cache, no-store, max-age=0, must-revalidate
pragma: no-cache
expires: 0
x-frame-options: DENY
x-trace-id: e5d9e1456a5049499dd15576de6e2fbe
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
atl-traceid: e5d9e1456a5049499dd15576de6e2fbe
atl-request-id: e5d9e145-6a50-4949-9dd1-5576de6e2fbe
strict-transport-security: max-age=63072000; preload
report-to: {"endpoints": [{"url": "https://dz8aopenkvv6s.cloudfront.net"}], "group": "endpoint-1", "include_subdomains": true, "max_age": 600}
nel: {"failure_fraction": 0.01, "include_subdomains": true, "max_age": 600, "report_to": "endpoint-1"}
x-cache: Miss from cloudfront
via: 1.1 8a37f712d19fe14896e6f4c568ac31c6.cloudfront.net (CloudFront)
x-amz-cf-pop: PNQ50-P1
x-amz-cf-id: v5lnIzb3HsvG4IK6lTUSeB5_r0yBcGpGes4a0D_wJZfbdoMXMm8-3Q==
server-timing: cdn-upstream-layer;desc="EDGE",cdn-upstream-dns;dur=0,cdn-upstream-connect;dur=0,cdn-upstream-fbl;dur=508,atl-edge;dur=503,atl-edge-internal;dur=2,atl-edge-upstream;dur=502,atl-edge-pop;desc="aws-ap-south-1",cdn-cache-miss,cdn-pop;desc="PNQ50-P1",cdn-rid;desc="v5lnIzb3HsvG4IK6lTUSeB5_r0yBcGpGes4a0D_wJZfbdoMXMm8-3Q==",cdn-downstream-fbl;dur=515

HTTP_STATUS=200

This is the Audit Log for the API call from the Atlassian Automation.

The webhook call succeeds with HTTP 200, and the Confluence Automation flow is triggered successfully.

However, the smart values are still empty in the audit log:

 → empty
<span>{{webhookData.content}}</span> → empty
<span>{{webhookData}}</span> → empty<span>{{webhookData.repository}}</span>

The audit log shows that the trigger is using Webhook version 2.0.

So in my case, neither the POST body nor the URL query parameters are being exposed through {{webhookData}}.

If you know of any different smart value for accessing query parameters specifically with Webhook v2.0, please let me know and I can try that as well.

Adnan Karbelkar_ Vodafone

Hi Trudy,

Thanks for the suggestions.

I am calling the webhook using curl from a macOS terminal.

I have also used curl --trace-ascii to inspect the actual request being transmitted, and the JSON body is being sent correctly without any hidden characters. The webhook returns HTTP 200, and the Confluence Automation flow is triggered successfully.

The payload being sent is similar to:

{
  "repository": "ndt_fe",
  "content": "Test Frontend documentation from webhook by Adnan"
}

I also tried the suggestion from the Atlassian article you shared.

I tested:

{{webhookData}}
{{webhookData.repository}}
{{webhookData.content}}

and also:

{{webhookResponse.body}}
{{webhookResponse.body.repository}}
{{webhookResponse.body.content}}

Unfortunately, all of them resolve to empty values in the Automation Audit Log.

For example:

webhookData=[] webhookResponseBody=[] repository=[] content=[]

The Incoming Webhook trigger in the Audit Log shows Webhook version 2.0.

I have also tried:

Sending the payload as application/json
Sending it as URL-encoded form data
Passing the values as URL query parameters

In every case the request returns HTTP 200 and triggers the flow, but the payload values are not available to the smart values.

I am attaching screenshots of the complete automation flow, Incoming Webhook configuration, and Audit Log.

Please let me know if you notice any context issue in the rule, or if there is another smart value/context that Webhook version 2.0 expects.

This is the Automation flow, I just first wanted the body paramter's so I have not built the flow further.

The command I run on the macos terminal (Redacted the Token and URL for security reason)

curl --trace-ascii /tmp/confluence-webhook.trace \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'X-Automation-Webhook-Token: **********************' \
  --data-raw '{"repository":"ndt_fe","content":"Test Frontend documentation from webhook"}' \
  'https://api-private.atlassian.com/automation/webhooks/confluence/a/**' \
  -w '\nHTTP_STATUS=%{http_code}\n'

The Audit Log for the above API call

I am not able to upload the trace file. I have that as well if you need it.

Trudy P Claspill

Hello @Adnan Karbelkar_ Vodafone

Having not worked with Confluence Automation Incoming Webhooks before I took a look at the information available directly within the Incoming Webhook dialog in Confluence Automation rules and noticed the following:

1. If you send information through --data with your POST method then that data is accessed through {{webhook.body}}, not {{webhookData}}

2. If you send information through parameters as part of the API then that data is accessed through {{webhook.parameters}}

Screenshot 2026-08-14 at 3.31.19 PM.png

So, try using those smart values (aligned with whether you are submitting a request body or API parameters) and see if you get the data. Let us know how that turns out.

Trudy P Claspill

Additionally {{webhookData}} is the smart value specified in documentation I found that talks about incoming webhooks in Jira Automation.

David Jonas_oj6h5a

Thank you @Trudy P Claspill your suggestion also helped solve my problem as well !

@Adnan Karbelkar_ Vodafone Atlassian need to get this fixed in the documentation please

Adnan Karbelkar_ Vodafone

@David Jonas - Totally agree, but I am not the one working for Atlassian and I am not aware how I could tell them to do it at this point. I will check the documentation to see if I can email this somehow to the concerned team and update you here once they acknowledge or if I have some information .

Have a Great Day.

Adnan Karbelkar_ Vodafone

@David Jonas - I have raised the below ticket with atlassian.

Adnan Karbelkar_ Vodafone

Discarded message as it was put in wrong thread.

Adnan Karbelkar_ Vodafone

@David Jonas

I received the response below and have replied to it. Hopefully, the documentation will be updated soon.

The Atlassian team has been very efficient, and I’m genuinely impressed by their quick response. Hats off to them! 🙂

I hope I’ve done everything I could from my side to help get this clarified and documented properly. I’ll sign off from here.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

cloud-automation