Azure Automation
An Azure service that is used to automate, configure, and install updates across hybrid environments.
How to create Webhook for Azure Runbook
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 90%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDI%3C/text%3E%3C/svg%3E)
Daniel Ispanovits
5
Reputation points
Hi,
I started having issues with adding Webhooks to existing Azure Runbooks.
No matter what parameters I use it fails with the following:
An error occurred while creating the Webhook 'CreatePlan'.
Error details:
{"stack":"BatchResponseItemError: Batch response item http error 400\n at t (https://portal.azure.com/Content/Dynamic/orGwOI0pWnf6.js:27:815)\n at new t (https://portal.azure.com/Content/Dynamic/orGwOI0pWnf6.js:47:12370)\n at https://portal.azure.com/Content/Dynamic/orGwOI0pWnf6.js:47:4954\n at Array.forEach (<anonymous>)\n at https://portal.azure.com/Content/Dynamic/orGwOI0pWnf6.js:47:3209","message":"Batch response item http error 400","type":"FxAjaxBatchResponseItemError","baseTypes":["FxAjaxBatchResponseItemError","MsPortalFx.Errors.Error"],"extension":"Microsoft_Azure_Automation","errorLevel":2,"timestamp":61189.69999998808,"name":"BatchResponseItemError","innerErrors":[],"content":{"Message":"The request is invalid.","ModelState":{"webhook.properties.parameters":["Invalid argument specified. Argument parameters cannot be null."]}},"headers":{"Pragma":"no-cache","x-ms-request-id":"<removed PII>","x-ms-operation-identifier":"tenantId=<removed PII>,objectId=<removed PII>","x-ms-ratelimit-remaining-subscription-writes":"199","x-ms-ratelimit-remaining-subscription-global-writes":"2999","x-ms-correlation-request-id":"<removed PII>","x-ms-routing-request-id":"UKSOUTH:20250916T152703Z:<removed PII>","Strict-Transport-Security":"max-age=31536000; includeSubDomains","X-Content-Type-Options":"nosniff","X-Cache":"CONFIG_NOCACHE","X-MSEdge-Ref":"Ref A: D172807DB8E84C6099605234CBF85D70 Ref B: AMS231032609047 Ref C: 2025-09-16T15:27:02Z","Cache-Control":"no-cache","Date":"Tue, 16 Sep 2025 15:27:02 GMT"},"httpStatusCode":400}.
Is this a bug or has something changed recently?
Azure Automation
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 68%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBY%3C/text%3E%3C/svg%3E)
Bharath Y P 1,350 Reputation points Microsoft External Staff Moderator2025-09-17T00:21:39.1333333+00:00 Hello Daniel Ispanovits,
You’re trying to create a Webhook for an existing Azure Automation Runbook, but the creation fails with a 400 Bad Request with the error message "Invalid argument specified. Argument parameters cannot be null."
This means Azure Automation expected Runbook parameters to be passed in when creating the webhook, it may be parameters were defined incorrectly or required parameter was missing, also if the null values were sent when they are not allowed.
The error you're seeing, "Argument parameters cannot be null", is a known validation requirement. It means that while the Azure portal UI allows you to add a webhook without specifying any parameters, the underlying API call is failing because the parameters field is required and cannot be null.
To resolve this is to manually add a dummy parameter in the Azure portal when you create the webhook. This satisfies the API's validation check.
- Go to your Automation Account > Runbooks > Select your runbook.
- Click on Add webhook > Create new webhook.
- Provide the webhook name, expiration date, and enable it.
- Back on the Add Webhook page, click Configure parameters and run settings.
- For each parameter defined in your runbook, supply a default or fixed value so that none are left null.
- If your runbook accepts webhook payload data, make sure the parameter is declared as: param( [object] $WebhookData ) This allows the webhook payload to be correctly passed into the runbook.
- After filling in all parameter values, click OK.
- Then click Create to finish creating the webhook.
Ensure that the parameters object is no longer null in the API call, allowing the webhook to be created successfully.
Kindly check the below documentation for more details: https://free.blessedness.top/en-us/azure/automation/automation-webhooks
Hope this helps. and please feel free to reach out if you have any further questions.
-
Daniel Ispanovits 5 Reputation points
2025-09-17T07:01:09.35+00:00 FYI, it looks like a bug to me.
Apparently you need to provide a WebhookData parameter now which is otherwise an optional parameter.
Passing an empty string helped. -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 5%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGC%3C/text%3E%3C/svg%3E)
Gopalakrishnan Chinnasamy 0 Reputation points2025-09-22T09:33:32.6833333+00:00 It looks like bug. So far created 100s of run books never had this issue. Looks like something recently added and causing the issue
-
Bharath Y P 1,350 Reputation points Microsoft External Staff Moderator
2025-10-14T05:09:54.0466667+00:00 Hello Daniel Ispanovits, we have reached out to you in Private messages for additional details, could you please look into it and share us the details? Thanks
Sign in to comment
Sign in to answer