Source type
GitLab Source Configuration
GitLab sources receive project and group webhook events. FastHook supports legacy secret tokens and GitLab's Svix-compatible signed webhooks.
GitLab configuration
Create a GitLab source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Signing or Secret Token values for provider signature. FastHook uses these settings to validate each GitLab delivery before it enters the routing workflow.
Source TypeGITLAB
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsSigning or Secret Token
{
"type": "GITLAB",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "GITLAB",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}GitLab request contract
FastHook uses Svix verification when webhook-signature is present; otherwise it compares x-gitlab-token with the configured token.
GitLab headers
Preserve x-gitlab-token, webhook-signature, webhook-id, webhook-timestamp when sending GitLab 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-gitlab-tokenLegacy secret token header.
webhook-signatureSvix-compatible signature header when present.
webhook-idSvix-compatible message id.
webhook-timestampSvix-compatible timestamp.
GitLab setup
- Create a GitLab project or group webhook and paste in the FastHook Source URL.
- Use the legacy secret token or the signed webhook secret depending on your GitLab configuration.
- Route by x-gitlab-event or project fields when several GitLab event types share one source.