GitLab Webhook Integration

Learn how our GitLab integration works and what data we collect through webhooks.

Overview

Our service integrates with GitLab through webhooks to provide real-time notifications in your Slack channels. When you configure a webhook in your GitLab project, GitLab will automatically send event data to our service whenever certain actions occur.

Events We Process

Merge Requests

When merge requests are opened, updated, merged, or closed. Includes comments and approvals.

Issues

Issue creation, updates, assignments, and state changes (open, closed, reopened).

Comments

Comments on merge requests, issues, and code snippets.

Push Events

Code pushes to repositories, including branch and tag creation/deletion.

Data We Store

What We Keep

Event timestamps and activity tracking
Merge request URLs and basic metadata
Issue identifiers and states
Project and repository names

What We Don't Store

Full webhook payloads
Code content or diffs
Personal access tokens
Full comment or description text

How It Works

1

Webhook Configuration

You configure a webhook in your GitLab project pointing to our service with a unique URL and secret token.

2

Event Processing

When events occur in GitLab, the webhook sends a HTTP POST request to our endpoint with event details.

3

Slack Notification

Our service processes the event and sends formatted notifications to your configured Slack channels.

Security & Privacy

Webhook Validation

All incoming webhooks are validated using the shared secret token to ensure authenticity.

HTTPS Only

All webhook endpoints require HTTPS encryption for data transmission.

Minimal Data Storage

We store only the minimum data required for functionality and never retain sensitive information.

Getting Started

Ready to set up GitLab webhooks for your project?

For existing users: Visit your dashboard to find your webhook URL and secret token.

New to our service? Sign up and follow our setup wizard to get started in minutes.