GitLab
Developer ToolsManage GitLab projects, issues, merge requests, repository content, CI/CD pipelines, and releases from your flows over the GitLab REST API v4. Works with GitLab SaaS and self-managed instances.
What This Integration Enables
FlowRunner agents use GitLab to keep engineering work flowing between systems without a person shuttling data by hand. An agent can turn tickets, form submissions, and monitoring alerts into labeled issues, open and update merge requests, commit generated files or configuration into a branch, and trigger, retry, or cancel CI/CD pipelines. When a release ships, it can publish the release and notify stakeholders. It works against gitlab.com or a self-managed instance without changing the flow. What it does not do on its own is merge to production or fire a production pipeline. Those stay with the engineer who owns the release.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Alerts into deduplicated issues
A monitoring alert lands in a flow. The agent maps it to the right project, calls List Issues to confirm the same alert has not already filed an issue, and then calls Create Issue with the alert details, the correct labels, and a link back to the source. It adds a note with the first-seen timestamp and posts the issue link to the engineering channel. Engineers open a tracker that is already deduplicated and labeled, instead of a pile of repeats.
Release tagging after a merge
A release workflow reaches the point where a reviewed merge request is ready. After an engineer approves and the agent calls Merge Merge Request, it calls Create Release to tag the version, then emails stakeholders the release notes. The version is tagged and announced without anyone assembling notes by hand.
Production merge gate
A merge request passes CI and is ready to merge into the default branch. The agent does not merge it. It posts the merge request, its pipeline status, and its diff summary to the release channel and asks the reviewing engineer to approve. Only after the engineer approves does the agent call Merge Merge Request. Code reaches production behind a decision a person made and a record shows they made it.
Human-in-Loop Highlight
The human-in-loop moment in GitLab is the production merge and pipeline gate. Reading issues, filing them, committing to a feature branch, and running CI on a branch are all reversible or low-stakes, so the agent runs them by rule. Merging into the default branch and triggering a production pipeline are not, so the agent stops. When a merge request is green and ready, the agent posts it to the release channel with its pipeline status and asks: "MR !482 is green and ready to merge into main. Approve the production merge?" A named engineer approves. Only then does the agent call Merge Merge Request, and, where the flow ships from a pipeline, Trigger Pipeline. The agent keeps the tracker and the branches moving. A person owns the moment the change goes live.
Agent Capabilities
27 actionsProjects
2- List Projects List the projects the authenticated token can access. Used to resolve a project before other actions.
- Get Project Retrieve a single project by numeric ID or namespaced path.
Issues
5- Create Issue File a new issue in a project. Used to turn a support ticket or monitoring alert into a tracked bug.
- Get Issue Retrieve a single issue by its project-scoped internal ID.
- List Issues List the issues in a project. Used to check for duplicates before filing.
- Update Issue Change an issue's state, labels, assignees, or fields.
- Create Issue Note Add a note (comment) to an issue.
Merge Requests
6- Create Merge Request Open a merge request from a source branch into a target branch.
- Get Merge Request Retrieve a single merge request by its internal ID.
- List Merge Requests List the merge requests in a project.
- Update Merge Request Update a merge request's title, description, labels, or reviewers.
- Merge Merge Request Merge a merge request into its target branch. Run it behind a human approval on production merges.
- Add Merge Request Note Add a note (comment) to a merge request. Used to post automated review notes.
Repository
7- List Branches List the branches in a project repository.
- Create Branch Create a branch from a ref.
- Delete Branch Delete a branch.
- Get File Read a file's contents at a path and ref.
- Create or Update File Commit a new or changed file to a branch.
- List Commits List the commits on a branch or across the repository.
- Create Commit Create a commit with one or more file actions in a single request.
Pipelines
5- List Pipelines List the CI/CD pipelines for a project.
- Get Pipeline Retrieve a single pipeline and its status.
- Trigger Pipeline Start a pipeline on a branch or tag. Run it behind a human gate when it targets production.
- Retry Pipeline Retry the failed jobs in a pipeline.
- Cancel Pipeline Cancel a running pipeline.
Releases
2- List Releases List the releases for a project.
- Create Release Publish a release tied to a tag. Used to ship a version and notify stakeholders.
Start building with GitLab
$100 in credits. No card required. Connect in minutes.