Issue Summary

Currently, there is no option to send an X-Automation-Webhook-Token header with native webhooks.

Reference: Update on Incoming Webhooks Trigger for Atlassian Automation Rules

This is reproducible on Cloud: Yes

Steps to Reproduce

1. Create an automation with the trigger - Incoming webhook
2. Create a webhook from System > Webhooks that will trigger the above automation rule.

Expected Results

The webhook should trigger the automation rule.

Actual Results

The webhook can't trigger the automation rule. 

Workaround

The recommended approach to trigger Automation rules from Jira events is to use a Jira-specific trigger in the Automation rule, rather than the incoming webhook trigger. There are a number of triggers available to that effect, like "Issue created" or "Issue transitioned". That approach is more reliable, secure and powerful.

Nevertheless, if using a Jira-specific trigger is not a feasible option and you really want to use an incoming webhook trigger, you can insert a slash at the end of the URL and add the secret after this. For example, https://URL/SECRET. This will allow you to update your rules without the need for a HTTP header. However, we recommend using the header if possible, as it provides more security for your secret.