GitLab troubleshooting hub: webhooks, access tokens, CI/CD, and MR notifications

Use this guide as the starting point when Axolo does not behave as expected with GitLab.

It links the most common GitLab issues: missing merge request channels, webhook errors, access token problems, self-hosted setup, and CI/CD notifications.

Start here: what is broken?

Axolo does not create Slack channels for merge requests

Start with:

Axolo is not opening channels

Common causes:

the GitLab group/project is not connected to Axolo,
the repository/project is inactive in Axolo,
the MR author is not onboarded in Axolo,
the MR was opened by a bot while bots are disabled,
Axolo did not receive the GitLab event,
the MR was explicitly excluded with _noslackchannel.

GitLab messages are not sent to Slack

Read:

GitHub or GitLab messages are not sent in Slack

Slack messages are not sent back to GitLab

Read:

Slack messages are not sent to GitHub/GitLab

Pipeline or CI/CD notifications are missing

Read:

Pipeline and CI/CD GitLab notifications troubleshooting

GitLab Cloud installation

For GitLab Cloud, Axolo installation is similar to GitHub but less granular.

After installing the application, you select the GitLab group you want to integrate with Axolo. Axolo then saves your organization members and project information.

Required GitLab scopes are:

api,
openid,
profile,
email.

GitLab self-hosted installation

For self-hosted GitLab, Axolo needs a GitLab application created in your GitLab instance.

The Axolo GitLab app should use these redirect URIs:

Required scopes are:

api,
read_user,
openid,
profile,
email.

The GitLab application must be confidential.

If your self-hosted instance is behind a VPN or firewall, contact us so we can share the Axolo server IPs to allowlist.

Read:

GitLab self-hosted installation

GitLab webhooks

Axolo needs GitLab events to receive merge request, comment, and pipeline activity.

If webhooks are failing, read:

Troubleshooting: GitLab Webhook Issues

If GitLab shows a webhook error, include the error when contacting support.

GitLab access tokens

If your GitLab token is missing, expired, revoked, or lacks permission, Axolo may fail to update webhooks or synchronize data.

Read:

Enable Access Tokens for GitLab

GitLab CODEOWNERS and auto reviewer assignment

Axolo has a GitLab auto reviewer assignment feature that can use your GitLab CODEOWNERS file to select reviewers for merge requests.

Read:

Auto Reviewer Assignment for GitLab by Axolo

Common GitLab symptoms

New MRs do not appear in Slack

Check:

The MR belongs to the GitLab group/project connected to Axolo.
The repository/project is active in Axolo.
The MR author is onboarded in Axolo.
The MR was not opened by a disabled bot or service account.
The MR does not include _noslackchannel in the body or label.
Axolo receives GitLab events for this group/project.

Pipeline notifications do not appear

Check:

The MR channel exists.
GitLab sends pipeline events to Axolo.
The pipeline is linked to the merge request.
Pipeline/CI-CD notifications are enabled for your setup.

Then read:

Pipeline and CI/CD GitLab notifications troubleshooting

What to send support

For GitLab troubleshooting, send:

GitLab group or project path,
example MR link,
whether the issue affects all projects or one project,
whether your GitLab is cloud or self-hosted,
screenshot or text of webhook errors,
whether the MR was created by a human, bot, or service account,
whether the repository/project is active in Axolo.

Updated on: 11/05/2026

Was this article helpful?

Thank you!