# Send a Webhook POST

Sends a one-way, fire-and-forget HTTPS POST with a custom body and headers to a webhook URL, without capturing a response body.


> **Availability:** See the [Incident Workflow Actions Overview table](/workflow-actions) for the plans this workflow is available on.

## Description

Send a POST request with a customized body and headers.

> **PagerDuty Events API:** `POST` requests to the [PagerDuty Events API](/developer/events-api-v2-overview) is currently blocked from Incident Workflows.

## Instructions

1. If you have not done so, follow the instructions to [Create an Incident Workflow](/ai-automation/automation/incident-workflows#create-an-incident-workflow).
2. When the instructions prompt you to [add actions](/ai-automation/automation/incident-workflows#add-actions), select **this action**.
3. Enter the following **Inputs** and click **Save**.
4. Continue following instructions to **Publish** the Workflow.
5. When the action runs, you will see the **Outputs** listed below.

## Inputs

> **Field References:** Fields with the **\{+\}** icon accept [Field References](/ai-automation/automation/incident-workflows#field-references), which can be useful for referencing incident data or outputs created in prior workflow steps. To add Field References, click **\{+\}**, or enter `{{`, and select relevant fields. Refer to the [Field References](/ai-automation/automation/incident-workflows#field-references) article for more information.

| Name                   | Description                                                                                                                                                                                                     |
| :--------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| URL                    | Enter the URL to send the webhook request to. Only HTTPS URLs are supported.                                                                                                                                    |
| Authentication Headers | Select a [Workflow Integration](/ai-automation/automation/incident-workflows/workflow-integrations) or click **New Web API Connection** to establish a new one.                                                                                   |
| Headers                | Enter a list of headers to include on the request, one per line. DO NOT INCLUDE SENSITIVE HEADERS, create a new Web API Credentials Connection above and use that instead. Ex: `Content-Type: application/json` |
| Body                   | The body to attach to the request. This field is blank by default. You will need to create and format the appropriate payload (e.g., JSON) for the tool or endpoint you are sending the webhook request to.     |

> **Recommendation:** We recommend using an online tool such as [Webhook.site](https://webhook.site/) or [PostBin](https://www.postb.in/)  to test and review the body you created for the request.

## Outputs

| Name                            | Description                                                                         |
| :------------------------------ | :---------------------------------------------------------------------------------- |
| Response Status Code            | The status code of the response.                                                    |
| Successful Status Code Response | Whether or not the response status code indicates success (`2XX`).                  |
| Response Headers                | The HTTP headers set in the response.                                               |
| Response Time in Milliseconds   | The time in milliseconds taken for a response to be sent to the request.            |
| Result                          | Value that shows if the action was successful or not. Either "Success" or "Failed." |
| Result Summary                  | Brief description of what the action did or if it failed.                           |
| Error                           | Brief description that is populated if the action failed.                           |

> **Webhook IP Addresses:** Incident Workflows does not use a static list of IP addresses for webhook actions. We recommend using **Authentication Headers**, rather than source IP address, to validate requests.