Connect your GitLab project to Decuga in minutes. Branches, commits and MRs link to tasks automatically — no access token needed, just a webhook secret.
The GitHub integration shipped last week. This week, the same feature is live for GitLab. If your team runs GitLab — self-hosted or gitlab.com — you can now connect any project repository to Decuga and get automatic task transitions and review sub-tasks on every merge request, with zero configuration overhead.
GitLab sends a webhook event to Decuga on every push and merge request action. Decuga scans the branch name, commit messages, and MR title for task codes (e.g. PROJ-42) and links the artefact to the matching task. Push a branch → task moves to In Progress. Open an MR → a "Review MR" sub-task is created under the parent task, assigned to the MR assignee. Merge or close the MR → the link card updates.
Unlike many integrations, Decuga does not need a GitLab access token. All the data we need — branch name, commits, MR title, assignee login, project path — is delivered in the webhook payload itself. The only thing you configure is a webhook secret that authenticates incoming events. This keeps the setup simple and means you have one fewer credential to rotate.
| What Decuga needs | How it arrives |
|---|---|
| Repository name | payload → project.path_with_namespace |
| Branch name | payload → ref (push event) |
| Commit messages + SHAs | payload → commits[] |
| MR title, number, URL | payload → object_attributes |
| Assignee username | payload → assignee.username |
| Webhook authenticity | X-Gitlab-Token header (secret you choose) |
The entire setup takes under two minutes. There is nothing to install, no OAuth to complete, and no token to generate on GitLab.
Install in Decuga
Project Settings → Integrations → Connect GitLab. Enter a webhook secret (any random string). Copy the Webhook URL.
Add webhook on GitLab
Project → Settings → Webhooks. Paste the URL and the same secret token. Enable Push events and Merge request events.
Push a test branch
Include a task code (e.g. PROJ-1) in the branch name and watch the Development section appear on the task within seconds.
GitLab calls them Merge Requests; Decuga shows them labelled as "PR / MR" in the Development panel to make the UI consistent across providers. The review sub-task is titled "Review MR: …" instead of "Review PR: …". Everything else — state tracking (open → merged/closed), task code detection, deduplication — works identically to the GitHub integration.
Self-hosted GitLab
The integration works with self-hosted GitLab instances as long as your instance can reach the Decuga webhook endpoint (app.decuga.com). No additional configuration is needed.
Ready to try Decuga?
Start free — no account or credit card required. One month free trial of the Starter plan.
Start free trial