Integration · Developer
AI agents for GitLab
Open and comment on issues, and start CI/CD pipelines, in the GitLab.com projects an access token can reach.
- Actions
- 4
- Read
- 1
- Write
- 3
Actions
What your agents can do in GitLab
Open and comment on issues, and start CI/CD pipelines, in the GitLab.com projects an access token can reach. Self-managed GitLab servers are not supported, because their hosts cannot be allow-listed ahead of time.
Read 1
Look things up. Nothing changes.
Get an issue
Reads one issue by its project-level number (iid): title, description, state, labels, assignees and web address.
Write 3
Create, change or send.
Create an issue
Opens an issue in a GitLab project, with an optional description in Markdown, labels, a due date and a confidential flag.
Comment on an issue
Adds a comment (a note, in GitLab's words) in Markdown to an issue, by its project-level number (iid).
Run a pipeline
Starts a CI/CD pipeline for a branch or tag, with optional CI/CD variables and pipeline inputs.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your GitLab account.
What you enter
- Personal access token
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your GitLab data
Ask a question in plain words. The agent can get an issue in GitLab, then answers with what it found.
- 02
Let an agent update GitLab
Have the agent create an issue or comment on an issue in GitLab as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent GitLab and Slack: it can get an issue in GitLab and post a summary to a Slack channel in the same run.
Works well with
More Developer tools
- GitHub4 actionsOpen and comment on issues, and start GitHub Actions workflows, in the repositories a personal access token can reach.
- Bitbucket3 actionsComment on and read pull requests, and start Bitbucket Pipelines, in the Bitbucket Cloud repositories your Atlassian API token can reach.
- Sentry3 actionsList, read, resolve and ignore error issues in a sentry.io organization, in its US or EU (Germany) data region.
- Datadog2 actionsPost events to the Datadog Event Explorer and send custom metric points, on any Datadog site, with an API key.
- PagerDuty4 actionsOpen, acknowledge and resolve PagerDuty incidents, add notes to them, and see who is on call for a schedule.
- App Store Connect8 actionsLook after iPhone, iPad and Mac apps on Apple's App Store.
FAQ
GitLab and MyDeepAgents
Can MyDeepAgents connect to GitLab?
Yes. The GitLab connector has 4 actions: 1 reads and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect GitLab?
Paste an API key from your GitLab account. You'll need: Personal access token. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in GitLab without asking?
Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs.
Can I use GitLab in workflows as well as agents?
Yes. Every GitLab action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put GitLab to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.