# GitLab AI employee Viktor works in GitLab for you. Ask in Slack or Microsoft Teams. Viktor is an AI employee that connects to GitLab and helps you build, test, and deploy code through CI/CD pipelines, running 28 GitLab actions for you like Get Issue, Create Epic, and List Groups. Ask in plain English from your workspace; Viktor does the work in GitLab and reports back. Viktor connects in one click via OAuth. - Tool: GitLab - Category: AI & Machine Learning - Connection: One-click OAuth - Actions available: 28 - Currently available in: Slack, Microsoft Teams, and Discord - Page: https://viktor.com/integrations/gitlab ## What can your AI employee do in GitLab? Viktor connects to your GitLab account and completes work in it. He doesn't just answer questions about GitLab, he takes the actions on your behalf and delivers the finished result to your workspace. Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right GitLab actions, chains them with the other 9,800+ tools he connects to, and asks for approval before anything sensitive runs. ### About GitLab GitLab is the most comprehensive AI-powered DevSecOps Platform. ### How a run works 1. **You ask in your workspace** - Describe what you need in plain English 2. **Viktor picks the actions** - Selects from 28 GitLab actions, chains them together 3. **Runs in GitLab** - Helps you build, test, and deploy code through CI/CD pipelines - your real data. 4. **Reports back** - Delivers the finished result to your workspace ## Use GitLab from Slack and Microsoft Teams Message Viktor in a Slack channel, a Microsoft Teams chat or a direct message. He opens GitLab, does the work and posts the result in the same thread, so nobody has to switch tabs. He can also run GitLab work on a schedule, like a weekly GitLab summary posted to your team's channel. Anything sensitive waits for your approval before it runs. ## Security and permissions - One-click OAuth - Viktor never sees your password, and you can revoke access at any time. - Review-first approvals: sensitive GitLab actions wait for your sign-off before they run. - Isolated compute per team, encrypted in transit and at rest - and your data is never used to train models. - SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress. - Viktor is not affiliated with or endorsed by GitLab. ## What can you ask Viktor to do in GitLab? - "Check GitLab for the latest failed build and summarize the likely cause." - "Trigger a deploy in GitLab for the latest release and report when it's done." - "Watch GitLab for failed pipelines and post a summary here with the likely cause." - "Summarize what shipped through GitLab this week for the changelog." ## How does Viktor work with GitLab? 1. Open Viktor in a supported workspace. 2. Connect GitLab with one-click OAuth - Viktor handles authentication. 3. Ask in plain English. Viktor runs the GitLab actions, chains them with your other tools when needed, and reports back. Sensitive actions wait for your approval. ## What can Viktor do in GitLab? (28 actions) - **Approve Merge Request** - Approve a merge request as the authenticated user, or withdraw an earlier approval by setting Action to unapprove. Call Get Merge Request first to check the merge request is actually ready — its readiness rollup reports the pipeline status, conflicts and how many approvals are still required — and Get Merge Request Diffs to read the changes being approved. Two things commonly go wrong: GitLab refuses to let you approve your own merge request, and a project may require approval from a specific approval rule that the authenticated user does not satisfy; both surface as a 401. To approve as part of leaving review feedback in one step, use Create Merge Request Review with its Action set to approve instead. Optionally pass SHA to make the approval conditional on the merge request's head commit, so it fails rather than silently approving work that was pushed after you read the diff. - **Create Branch** - Create a new branch in the repository. - **Create Epic** - Creates a new epic. - **Create issue** - Creates a new issue. - **Create Merge Request Comment** - Post a comment on a merge request. It works in three modes, chosen by which props you set: leave File Path and Discussion ID blank for a plain comment on the merge request as a whole; set File Path plus a line number to open an inline thread anchored to that line of the diff; or set Discussion ID to reply inside an existing thread. Use Get Merge Request Diffs first to get valid file paths and line numbers, and List Merge Request Discussions to get a Discussion ID to reply to. Line numbers follow GitLab's diff rules: for a line the merge request adds or leaves unchanged, pass New Line; for a line it removes, pass Old Line; for an unchanged context line, pass both. Getting that wrong is the usual cause of a rejected inline comment. To post several review comments at once, and optionally approve in the same step, use Create Merge Request Review instead. - **Create Merge Request Review** - Submit a whole review on a merge request in one step: any number of inline comments anchored to lines of the diff, an overall summary comment, and optionally an approval. This is the tool for \"review this MR\" — call Get Merge Request and Get Merge Request Diffs first to read the changes, then send the findings back here. GitLab has no single submit-review API, so this action posts each inline comment as its own thread and then approves if asked; if an individual comment is rejected (usually a line that is not part of the diff) the rest are still posted and the failures are returned in failed, so check that array rather than assuming everything landed. Line numbers follow GitLab's diff rules: newline for a line the merge request adds, oldline for a line it removes, both for an unchanged context line. There is no REST equivalent of GitLab's Request changes state — to block a merge request, leave the findings as comments and do not approve. - **Create Merge Request** - Open a new merge request from one branch into another. Use this for \"open an MR\", \"raise a merge request\", \"submit my branch for review\". Both branches must already exist in the project — use List Repo Branches to check, or Create Branch to make one. Reviewers and assignees are given as usernames and resolved to IDs automatically; a username that is not a member of the project is rejected rather than silently dropped. Set Draft to true for work that is not ready for review — GitLab expresses this by prefixing the title with Draft:, which this action does for you and which blocks merging until removed. After creating, use Get Merge Request to check its pipeline and merge readiness. - **Get Issue** - Gets a single issue from repository. - **Get Merge Request Commits** - List the commits contained in a merge request, newest first. Use this to understand how a change was built up — whether it is one clean commit or a long history to squash, who wrote each part, and what the commit messages claim. For the actual code changes call Get Merge Request Diffs instead; for merge readiness call Get Merge Request. - **Get Merge Request Diffs** - List the file-level changes in a merge request — each changed file's path, whether it was added, deleted or renamed, and its unified diff. This is the tool to call before reviewing, approving or commenting on a merge request: the newpath values and the line numbers inside each diff hunk are what Create Merge Request Comment and Create Merge Request Review need to anchor an inline comment. Large merge requests can be trimmed with Paths (only files under the given prefixes) and Max Files. Watch for toolarge: true or collapsed: true on a file — GitLab omits or shortens those diffs, so do not conclude a file is unchanged. Use Get Merge Request for metadata and merge readiness, and Get Merge Request Commits for the commit history. - **Get Merge Request** - Get a single merge request together with a readiness rollup that answers \"can this be merged?\" in one call — state, draft flag, detailedmergestatus, conflict flag, whether blocking threads are resolved, head pipeline status, and the approval count with who has approved. Use this to open or inspect a merge request, and before approving or merging one. It does not return the code changes: call Get Merge Request Diffs for those, and List Merge Request Discussions for existing review comments. If you only know the merge request by title, resolve its iid with Search Merge Requests first. The response also carries diffrefs, the commit SHAs needed to anchor inline comments — no other tool needs to fetch them. - **Get Repo Branch** - Get a single project repository branch. - **List Commits** - List commits in a repository branch. - **List Group ID Options** - Retrieves available options for the Group ID field. - **List Group Path Options** - Retrieves available options for the Group Path field. - **List Groups** - List all groups. - **List Merge Request Discussions** - List the comment threads on a merge request — both general comments and inline threads anchored to lines of the diff. Use this to read existing review feedback before adding your own, to find what a reviewer objected to, or to get the id of a thread so you can reply to it with Create Merge Request Comment or close it with Resolve Merge Request Thread. Each thread's notes carry resolvable, resolved and, for inline threads, the position (file path and line) they are attached to. GitLab records label changes, assignments and other bookkeeping as system notes; those are filtered out by default because they are rarely what a reader wants — set Include System Notes to true to see them. Set Only Unresolved to true to get just the threads still needing attention. - **List Merge Requests** - List merge requests, filtered by project, group, state, author, assignee, reviewer, labels or target branch. Use this for any \"what merge requests are …\" question — open MRs in a project, MRs waiting on my review (set Scope to reviewsforme), MRs assigned to me, MRs targeting a release branch. Use Search Merge Requests instead when you have text to match against a title or description. Set Project to scope to one project, Group to scope to a whole group, or leave both blank to search across everything the authenticated user can see — note that with both blank GitLab defaults Scope to createdbyme, so pass all to widen it. Results are summarized by default; set Detail to full for the complete merge request objects. The returned iid is what every other merge request tool needs. - **List Project ID Options** - Retrieves available options for the Project ID field. - **List Project Labels** - List the labels defined in a project. Call this before applying labels with Create Merge Request: GitLab creates a label it does not recognize rather than rejecting it, so an invented or mis-cased name silently adds a new project label instead of applying the intended one. Each result's name is the value to pass back; the description is worth reading because label names are often abbreviations. Narrow a long list with Search. - **List Project Members** - List all members of a project. - **List Projects** - List or search GitLab projects, optionally filtering by search term, membership, or ownership. Use this to discover projects (and their IDs) before acting on them with other GitLab actions. Supports ordering by name, path, creation/update time, star count, last activity, or search similarity, plus pagination. The similarity order requires a Search term. - **List Repo Branches** - Get a list of repository branches from a project. - **Resolve Merge Request Thread** - Mark a merge request thread as resolved, or reopen a resolved one by setting Resolved to false. Use this after acting on a piece of review feedback — resolving threads is what clears a merge request's blockingdiscussionsresolved flag so it can merge. Get the Discussion ID from List Merge Request Discussions (set its Only Unresolved to true to see just the threads still open). Only threads that are resolvable can be resolved: plain comments on the merge request as a whole are not, and GitLab rejects the attempt. - **Search Issues** - Search for issues in a repository with a query. - **Search Merge Requests** - Find merge requests whose title or description matches a search term. Use this when the user refers to a merge request by what it is about (\"the MR about the Redis cache refactor\", \"the payments migration MR\") rather than by number - it is the fastest way to turn a description into the iid that every other merge request tool needs. ALWAYS set Project (or Group) when you know which one the user means: a project-scoped search returns in well under a second, whereas an unscoped search scans every project the account can access and, on accounts that belong to many projects, can take tens of seconds and time out (HTTP 408). Leave both blank only when the project is genuinely unknown. Use List Merge Requests instead when there is no text to match and you only want to filter by state, author, reviewer or branch. Matching is case-insensitive substring, not fuzzy - prefer one or two distinctive words over a whole sentence. - **Update Epic** - Updates an epic. - **Update Issue** - Updates an existing project issue. ## Viktor uses GitLab together with - [Slack](https://viktor.com/integrations/slack) - [Gmail](https://viktor.com/integrations/gmail) - [Google Sheets](https://viktor.com/integrations/google-sheets) - [HubSpot](https://viktor.com/integrations/hubspot) - [Notion](https://viktor.com/integrations/notion) - [Salesforce](https://viktor.com/integrations/salesforce) ## More AI & Machine Learning integrations - [Browser Use](https://viktor.com/integrations/browser-use) - [Symbl.ai](https://viktor.com/integrations/symbl-ai) - [Daytona](https://viktor.com/integrations/daytona) - [OpenAI (ChatGPT)](https://viktor.com/integrations/openai-chatgpt) - [Devin](https://viktor.com/integrations/devin) - [Ollama](https://viktor.com/integrations/ollama) - [302.AI](https://viktor.com/integrations/302-ai) - [Cursor](https://viktor.com/integrations/cursor) ## FAQ ### Does Viktor integrate with GitLab? Yes. GitLab is one of the 9,800+ tools Viktor connects to, in one click via OAuth. Once connected, anyone on your team can put Viktor to work in GitLab from their workspace - no workflow builder, no code. ### How do I connect GitLab to Viktor? Ask Viktor in your workspace to connect GitLab, then approve the one-click OAuth prompt. Viktor never sees your password, handles authentication itself, and starts working right away. Setup takes about two minutes, and you can revoke access at any time. ### What can Viktor do in GitLab? Viktor can run 28 GitLab actions, including Get Issue, Create Epic, and List Groups - and chain them with other tools in a single request. In practice that means Viktor helps you build, test, and deploy code through CI/CD pipelines. If a task spans several actions, Viktor plans the sequence itself and reports back when the work is done. ### Do I need to build workflows for GitLab? No. Viktor isn't a workflow builder - there are no triggers to map and nothing to maintain. You ask for the outcome in plain English in your workspace, and Viktor decides which GitLab actions to take, runs them, and reports back. ### Is my GitLab data secure with Viktor? Yes. Viktor connects to GitLab in one click via OAuth, runs in an isolated environment per team, and never trains models on your data. Sensitive actions wait for your approval, and you can revoke access at any time. Viktor is SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress. ### How much does the GitLab integration cost? Nothing extra - every integration, including GitLab, is available on every plan. You can start free with up to $100 in credits, no credit card required; the Team plan is $100 a month. ### Can Viktor use GitLab together with my other tools? Yes - that's the point. Viktor connects to 9,800+ tools and works across them in a single run: he can pull data from GitLab, cross-reference it with another tool - for example Slack or Gmail, and deliver the finished result in your workspace. ## Get started Viktor is free to start - up to $100 in credits, no credit card required. All 9,800+ integrations are included on every plan. Sign up at https://viktor.com or browse all integrations at https://viktor.com/integrations.