Send a Webhook POST
Web API
Availability
This workflow action is available on our Business and Enterprise for Incident Management pricing plans. Please contact our Sales Team to upgrade to an account with this action.
Description
Send a POST request with a customized body and headers.
PagerDuty Events API
POSTrequests to the PagerDuty Events API is currently blocked from Incident Workflows.
Instructions
- If you have not done so already, please follow our instructions to Create an Incident Workflow.
- When you are prompted to add actions , select this action.
- Enter the following Inputs and then click Save. Continue following instructions to Publish the Workflow. When the action runs, you will see the Outputs listed below.
Inputs
| Name | Description |
|---|---|
| URL | Enter the URL to send the webhook request to. Only HTTPS URLs are supported. |
| Authentication Headers | Select a Workflow Integration 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 or PostBin 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.
Updated 9 days ago