Issue Summary

Invoking an incoming webhook request configured within an Automation rule via the System webhook results in a silent failure.

Steps to Reproduce

1. Create an automation rule with incoming webhook request in Jira A instance
2. add a Log action just to log the webhook data delivered. 
3. Configure the Webhook as system webhook in Jira B instance
4. Use event Issue created in System Webhook. 
5. Create an issue so the System webhook is sent to Jira A instance

Expected Results

Automation rule is triggered as the incoming webbhook url was used in the system webhook.

Actual Results

Automation rule is not triggered.
In the backend we can analyze the log and they fail with

Error response code 400 when sending webhook to https://api-private.atlassian.com/automation/webhooks/jira/a/xxxxx/xxxxx?triggeredByUser=removedValue

Reason for failure
The new Incoming webhook endpoint starting 29th Jan 2025 requires EITHER the use the  X-Automation-Webhook-Token header OR to append the secret to the URL, as described in https://support.atlassian.com/cloud-automation/docs/configure-the-incoming-webhook-trigger-in-atlassian-automation/ . If the secret is not provided by one of those two means, a 400 response is expected. In system webhook there is no option to add additional headers, therefore it is necessary to append the secret to the URL as described in the documentation.

FR closed : JRACLOUD-22079