Source type
PagerDuty Source Configuration
PagerDuty sources receive incident, service, escalation, and responder lifecycle webhooks with PagerDuty webhook v3 signatures.
PagerDuty configuration
Create a PagerDuty source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Signing Secret values for provider signature. FastHook uses these settings to validate each PagerDuty delivery before it enters the routing workflow.
Source TypePAGERDUTY
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsWebhook Signing Secret
{
"type": "PAGERDUTY",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "PAGERDUTY",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}PagerDuty request contract
FastHook parses x-pagerduty-signature, extracts v1 values, and accepts any HMAC-SHA256 hex digest that matches the raw body.
PagerDuty headers
Preserve x-pagerduty-signature when sending PagerDuty test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.
x-pagerduty-signatureComma-separated v1 HMAC-SHA256 signatures over the raw body.
PagerDuty setup
- Create a PagerDuty webhook subscription with the generated FastHook Source URL.
- Copy the PagerDuty webhook signing secret into FastHook.
- Route by event_type, service id, or incident urgency for alerting workflows.