Skip to content

Commit c0be8a0

Browse files
Merge pull request #261770 from SnehaSudhirG/21Dec-Git113577
updated the request header property
2 parents 9a4af37 + 6cd77cf commit c0be8a0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/automation/automation-webhooks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Start an Azure Automation runbook from a webhook
33
description: This article tells how to use a webhook to start a runbook in Azure Automation from an HTTP call.
44
services: automation
55
ms.subservice: process-automation
6-
ms.date: 12/18/2023
6+
ms.date: 12/21/2023
77
ms.topic: conceptual
88
ms.custom: devx-track-azurepowershell, devx-track-arm-template
99
---
@@ -40,7 +40,7 @@ The `WebhookData` parameter has the following properties:
4040
| Property | Description |
4141
|:--- |:--- |
4242
| WebhookName | Name of the webhook. |
43-
| RequestHeader | Hashtable containing the headers of the incoming POST request. |
43+
| RequestHeader | PSCustomObject containing the headers of the incoming POST request. |
4444
| RequestBody | Body of the incoming POST request. This body keeps any data formatting, such as string, JSON, XML, or form-encoded. The runbook must be written to work with the data format that is expected. |
4545

4646
There's no configuration of the webhook required to support the `WebhookData` parameter, and the runbook isn't required to accept it. If the runbook doesn't define the parameter, any details of the request sent from the client are ignored.

0 commit comments

Comments
 (0)