Source type
CircleCI Source Configuration
CircleCI sources receive workflow and job webhooks and verify CircleCI's outbound webhook signature.
CircleCI configuration
Create a CircleCI 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 CircleCI delivery before it enters the routing workflow.
Source TypeCIRCLECI
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsWebhook Signing Secret
{
"type": "CIRCLECI",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "CIRCLECI",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}CircleCI request contract
FastHook computes HMAC-SHA256 hex over the raw body and compares it with the v1 value in circleci-signature.
CircleCI headers
Preserve circleci-signature when sending CircleCI 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.
circleci-signaturev1 HMAC-SHA256 signature or plain signature value.
CircleCI setup
- Create a CircleCI outbound webhook using the FastHook Source URL.
- Paste the webhook signing secret into FastHook.
- Use pipeline, workflow, and project fields to route CI notifications.