Configure Webhooks for Gitlab

Overview

Webhooks enable real-time communication between GitLab repositories and the Cubyts platform. Once configured, Cubyts can automatically analyze merge requests, commits, and review activity to generate actionable insights.

Prerequisites

Before setting up the webhook, ensure you have:

• Admin (Maintainer/Owner) access to the target GitLab repository.

• Access to the Cubyts platform.

• Generated Payload URL and Secret from the Cubyts GitLab integration page.

Step-by-Step Setup

Navigate to Webhook Settings

1. Open your GitLab repository (project).

2. Go to Settings.

3. Click on Webhooks.

Or directly access:

https://gitlab.com/<your-group>/<your-project>/-/hooks

Configure Webhook Details

Fill in the following fields:

URL

• Paste the Payload URL generated from Cubyts

• Note: The payload URL will be available at the repository level in the Cubyts GitLab integration page

Secret Token

• Enter the Secret generated from Cubyts

• Note: The secret will be available at the repository level in the Cubyts GitLab integration page

Select Trigger

Enable the following triggers:

• Push events

• Merge request events

• Comments

SSL Verification

Ensure the following is enabled: enable_ssl_verification: true

Final Configuration

Ensure the following settings are correctly configured:

Click Add webhook to complete the setup.

Note: Please ensure that only one webhook is created for a repo (pointing to the Cubyts payload URL).

Notes & Best Practices

• A webhook must be configured per repository (project)

• Keep your Secret Token secure and do not expose it publicly

• If you regenerate the secret in Cubyts, update it in GitLab immediately

• Avoid duplicate webhooks for the same repository