Source type

PagerDuty Source Configuration

PagerDuty sources receive incident, service, escalation, and responder lifecycle webhooks with PagerDuty webhook v3 signatures.

PAGERDUTYPOST, PUT, PATCH, DELETEWebhook Signing SecretObservability
PagerDuty sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.PagerDutyProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLPAGERDUTYProvider credentialsignatureVerify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.

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 Type

PAGERDUTY

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Webhook Signing Secret

PagerDuty source config
{
  "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.

POSTPUTPATCHDELETE

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-signature

Comma-separated v1 HMAC-SHA256 signatures over the raw body.

PagerDuty setup

  1. Create a PagerDuty webhook subscription with the generated FastHook Source URL.
  2. Copy the PagerDuty webhook signing secret into FastHook.
  3. Route by event_type, service id, or incident urgency for alerting workflows.

Continue with PagerDuty