Source type
Heroku Source Configuration
Heroku sources receive app webhook events for releases, builds, formations, add-ons, domains, and app lifecycle changes.
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 TypeHEROKU
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsSigning Secret
{
"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.
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-sha256Base64 HMAC-SHA256 signature over the raw body.
Heroku setup
- Create a Heroku app webhook pointing at the FastHook Source URL.
- Use the Heroku signing secret in FastHook.
- Route release and build events to deployment automation destinations.