Incoming Webhook URL Change broke GitLab

[Nathan H_]

The URL change coming in May has got us to update or webhook rules in GitLab in preparation. Now that they have a new URL and secret token the gitlab tests are failing with an HTTP 400. I've used curl and can successfully hit the API and can confirm it in the automation audit logs. A 400 error is generic and I'm having troubles figuring this out on my own. 

Is there additional GitLab configurations now needed for for the web hooks? Mostly just need merge request to trigger my Jira automations. 

[Nathan H_ · Accepted solution]

A custom header is needed in the GitLab web hook:

1. Select, Add custom header
   1. Header name: X-Automation-Webhook-Token
   2. Header value: <Add you secret here>

[Vikrant Yadav]

@Nathan H_  Welcome to Atlassian Community!

Have you tested Automation incoming webhook URL and Token in postman ? 
In postman also getting 400 error code. 

https://support.atlassian.com/automation/kb/check-if-the-incoming-webhook-trigger-in-an-automation-rule-is-correct/

[Vikrant Yadav]

Or you try this webhookURL\Token

[Nathan H_]

I have not as the way I read the article it was an alternative to curl, is there a benefit to using Postman over Curl? If not, then I would prefer not to install extra software and create additional accounts. 

[Nathan H_]

I'm using the same secret for both API URL's. This is the output from gitlab:

Hook executed successfully but returned HTTP 400 {"errorMessage":null,"message":null,"warningMessages":[],"errorMessages":["Missing token"],"errors":{},"status":400}