Source type
Buildkite Source Configuration
Buildkite sources receive pipeline, build, job, agent, and annotation webhooks with timestamped Buildkite signatures.
Buildkite configuration
Create a Buildkite source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Token values for provider signature. FastHook uses these settings to validate each Buildkite delivery before it enters the routing workflow.
Source TypeBUILDKITE
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsWebhook Token
{
"type": "BUILDKITE",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "BUILDKITE",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}Buildkite request contract
FastHook verifies x-buildkite-signature by signing timestamp + '.' + raw body with HMAC-SHA256.
Buildkite headers
Preserve x-buildkite-signature when sending Buildkite 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-buildkite-signatureContains timestamp and signature parameters.
Buildkite setup
- Create a Buildkite pipeline webhook using the FastHook Source URL.
- Paste the webhook token into FastHook.
- Route by event type or pipeline slug for CI automation.