Source type

Heroku Source Configuration

Heroku sources receive app webhook events for releases, builds, formations, add-ons, domains, and app lifecycle changes.

HEROKUPOST, PUT, PATCH, DELETESigning SecretDeveloper tools
Heroku sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.HerokuProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLHEROKUProvider 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.

Heroku configuration

Create a Heroku source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Signing Secret values for provider signature. FastHook uses these settings to validate each Heroku delivery before it enters the routing workflow.

Source Type

HEROKU

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Signing Secret

Heroku source config
{
  "type": "HEROKU",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "HEROKU",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Heroku request contract

FastHook computes base64 HMAC-SHA256 over the raw body and compares it with heroku-webhook-hmac-sha256.

POSTPUTPATCHDELETE

Heroku headers

Preserve heroku-webhook-hmac-sha256 when sending Heroku 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.

heroku-webhook-hmac-sha256

Base64 HMAC-SHA256 signature over the raw body.

Heroku setup

  1. Create a Heroku app webhook pointing at the FastHook Source URL.
  2. Use the Heroku signing secret in FastHook.
  3. Route release and build events to deployment automation destinations.

Continue with Heroku