Skip to content
Esc
↑↓navigate↵open⌘Jpreview
On this page

GitLab

Sync merge requests and issues, and let the agent act on them

The GitLab integration connects your GitLab projects to Modem. It captures merge request, issue, and comment activity from the projects you choose, and it gives the Modem Agent the ability to search, create, update, and comment on merge requests and issues directly from chat.

Prerequisites

  • Admin access in the Modem organization where you want to connect GitLab
  • A GitLab account with at least Maintainer access on the projects you want to monitor (required to install project webhooks)

Setup

Start the connection

Go to Settings → Integrations → GitLab in your Modem dashboard and click Connect GitLab.

Authorize Modem

You’ll be redirected to GitLab to authorize Modem. Review the requested access (api and read_user) and approve. Modem connects as the GitLab account you authorize with.

Enable projects

Back in Modem, you’ll see the projects your account can access. Toggle on the ones you want Modem to monitor. See Enabling Projects below for what happens when you do.

Enabling Projects

GitLab ingestion is opt-in per project. Nothing is captured until you enable a project from the project list in Settings → Integrations → GitLab.

Enabling a project installs a webhook on that project for merge request, issue, and comment events, so new activity flows into Modem in real time. It also starts a one-time import of every merge request and issue on that project updated in the last 90 days (with up to 100 comments per item).

Toggle a project off at any time to remove its webhook and stop ingestion. You can filter the project list by visibility (public, internal, private) to find what you’re looking for.

What Gets Captured

For each enabled project, Modem captures:

Merge requests

Merge request titles, descriptions, source and target branches, author, labels, and state. Modem tracks the full lifecycle: opened, updated, merged, and closed-without-merge.

Issues

Issue titles, descriptions, author, labels, and state (open or closed), captured as they’re created and updated.

Comments

Comments (GitLab calls them notes) on both merge requests and issues, with their author and body.

What the Agent Can Do

With GitLab connected, you can ask the Modem Agent to work with your merge requests and issues. Read operations run on demand; write operations require your approval before they execute.

  • Search and list merge requests and issues the connected GitLab account can access
  • Read full details of a merge request or issue, including its recent comments
  • Update issues: title, description, labels, open/close (requires approval)
  • Comment on a merge request or issue (requires approval)
  • Create issues from feedback conversations (requires approval)

The agent talks to GitLab’s GraphQL API, not only the operations above. Reads run as written. Writes must be parameterized GraphQL mutations (no inline arguments) and still require your approval. Enabling a project in Modem controls ingestion into topics; it does not limit what the agent can query in GitLab.

Example Prompts

These work from the dashboard, Slack DMs, or by mentioning @modem in a channel.

Simple:

PromptWhat merge requests merged in the api project this week?
PromptShow me issue #42 in web/storefront and summarize the discussion
PromptCreate a GitLab issue for the login timeout complaints in the backend project

Advanced:

PromptFind the open issues in our GitLab projects with the most related user complaints and rank them by feedback volume
PromptSummarize all Slack and Discord feedback about search performance and add it as a comment on the relevant GitLab issue

Automations

GitLab merge request and issue events can trigger automations in Modem. After GitLab is connected, you can create trigger automations for:

Trigger Fires when
GitLab MR Created A new merge request is synced
GitLab MR Merged A merge request is merged
GitLab MR Closed A merge request is closed without being merged
Pull Request Activity A merge request is opened, marked ready for review, merged, closed, or reopened
Issue Activity An issue is opened, closed, reopened, or commented on

These are useful for posting shipping updates to Slack, summarizing merged work, or connecting merged changes back to the feedback that prompted them.

Self-Managed GitLab

The connect flow always authorizes against GitLab.com, so you can’t point a connection at your own instance from the dashboard. If you run self-managed GitLab, contact support@modem.ai.

Troubleshooting

A project isn't appearing in the list

The project list reflects what your connected GitLab account can access at Maintainer level or above. If a project is missing, verify your access in GitLab, then reload the GitLab settings page in Modem.

Merge requests, issues, or comments aren't showing up

Work through these in order:

  • Confirm the project is toggled on in Settings → Integrations → GitLab
  • Allow a few minutes for webhook delivery and processing
  • In GitLab, check the project’s Settings → Webhooks and look at the recent delivery log for the Modem hook
  • Note that GitLab system notes (automated label/assignment entries) are intentionally skipped
Connection shows an error

Open Settings → Integrations → GitLab to see the error detail. If the access has expired or permissions changed, reconnect from the same page. If the error persists, contact support@modem.ai.

The agent can't find or act on a merge request or issue

Work through these in order:

  • Verify GitLab is connected. For data that should already be in Modem (topics, captured comments), also confirm the project is toggled on. The agent can still query GitLab live for projects the connected account can access, even if they aren’t enabled for ingest.
  • Be specific with the project path and the merge request or issue number
  • Remember that creating issues, updating issues, and adding comments require approval, so check for a pending approval prompt

Disconnecting

To disconnect GitLab:

  1. Go to Settings → Integrations → GitLab
  2. Click Disconnect

This removes the webhooks from your enabled projects, so new activity is no longer synced and the agent can no longer act on GitLab. Historical data remains in Modem after disconnecting.

Was this page helpful?