Incoming Webhook in Atlassian Studio/Jira Automation triggers and creates issue, but {{webhookData}}

Imran Malik

I have set up an Incoming Webhook rule in Atlassian Automation (Studio) integrated with Chatwoot. When an event occurs (e.g., adding a label in Chatwoot), Chatwoot sends a JSON POST request to the generated webhook URL with Content-Type: application/json.

The automation rule triggers successfully, runs, and creates a Jira issue. However, all smart values derived from {{webhookData}} evaluate to empty/blank strings.

Observed Behavior:

1. The rule executes every time Chatwoot sends the payload.
2. Executing a Log action with {{webhookData}} or {{webhookData.id}} outputs completely blank text in the Audit Log.
3. The created issue summary and description display empty strings where variables like {{webhookData.id}} or {{webhookData.meta.sender.name}} should be.
4. Testing locally via cURL (curl -X POST <URL> -H "Content-Type: application/json" -d '{...}') yields the exact same result: status 200/success execution in Audit Log, but {{webhookData}} remains empty.

Imran Malik

yes, the chatwoot that trigger the Jira webhook send payload as java object rather than json. Thats why body is returning empty values and rovo suggests to fix it at chatwoot so I ask chatwoot for this waiting for their response. But good thing is I know now what's the issue. Thanks Matthew for the quick response.