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.

GITLABPOST, PUT, PATCH, DELETESigning or Secret TokenDeveloper tools
GitLab sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.GitLabProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLGITLABProvider 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.

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 Type

GITLAB

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Signing or Secret Token

GitLab source config
{
  "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.

POSTPUTPATCHDELETE

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-token

Legacy secret token header.

webhook-signature

Svix-compatible signature header when present.

webhook-id

Svix-compatible message id.

webhook-timestamp

Svix-compatible timestamp.

GitLab setup

  1. Create a GitLab project or group webhook and paste in the FastHook Source URL.
  2. Use the legacy secret token or the signed webhook secret depending on your GitLab configuration.
  3. Route by x-gitlab-event or project fields when several GitLab event types share one source.

Continue with GitLab