GitLab
Work on issues and merge requests in GitLab.com or your own GitLab. Agents list and triage issues, read discussions, leave internal notes or public comments, open issues, read merge requests and their diffs, and read files in a repository.
- Category
- Developer & IT
- Ways to connect
- 2
- Actions for agents
- 12
- Triggers
- 0
Ways to connect
A company admin connects GitLab from the Integrations page in Everdeck. Keys, tokens and secrets are encrypted before they're stored, and the connection's Test button checks it works before any agent uses it.
-
Personal access token API key
Copy a key or token from GitLab and paste it into Everdeck.
-
Your GitLab OAuth application Your OAuth app
Create an OAuth app of your own with GitLab, paste its client ID and secret into Everdeck, then sign in to GitLab and approve access. Access runs through your own app, never one Everdeck shares with other customers.
What agents can do with GitLab
An agent can only use the actions its charter grants. Each action has a risk tier, and the tier decides whether it runs on its own, asks first or always asks a person.
Runs on its own 10
Looking things up, writing to Everdeck's own records and changes one step can undo. Once an agent's charter grants one of these, it runs without asking, unless you set it to Ask first in the charter or one of your approval rules covers it.
-
List projects Tier 0 · Read Outside content
List the projects you are a member of, most recently active first, with id, full path, default branch and web address. Use the numeric id as project_id in the other actions.
-
List issues in a project Tier 0 · Read Outside content
List a project's issues, most recently updated first. Filter by state, labels, assignee, text in the title or description, or changes since a time. iid is the number shown in GitLab (#12).
-
Read an issue Tier 0 · Read Outside content
Read one issue: description (Markdown), state, labels, assignees, milestone, due date, confidentiality and comment count. Use list_notes for the discussion.
-
Triage an issue Tier 2 · Reversible Outside content
Close or reopen an issue, add or remove labels, change assignees, milestone, due date or weight. Send only what changes. Participants are notified.
-
Read comments Tier 0 · Read Outside content
Read the comments (notes) on an issue or merge request, oldest first. Notes GitLab writes itself (such as "changed the label") have system true; internal notes have internal true; comments on diff lines have type DiffNote and a position.
-
Add an internal note Tier 2 · Reversible
Add an internal note to an issue or merge request. Only project members with at least the Reporter role can see it, so it suits hand-offs and triage notes; replies to it stay internal. Lines may not start with "/" (GitLab would run them as quick actions).
-
List merge requests Tier 0 · Read Outside content
List a project's merge requests, most recently updated first. Filter by state, reviewer, author, labels, draft status, text or changes since a time.
-
Read a merge request Tier 0 · Read Outside content
Read one merge request: description, state, draft, branches, reviewers, whether it can be merged (detailed_merge_status), conflicts, unresolved threads, latest pipeline status and number of changes. Use get_merge_request_diffs for the code.
-
Read a merge request's changes Tier 0 · Read Outside content
List the files a merge request changes with their diffs (unified format). Very large or generated files may be collapsed or marked too_large without a diff.
-
Read a file Tier 0 · Read Outside content
Read a text file from a project's repository at a branch, tag or commit (the default branch when ref is left out), or list a directory. Long files are cut short; binary files return only their size.
Asks first 2
Anything a customer or the public sees. By default a charter grants these as Ask first: the agent sends an approval request and waits for a yes. A company admin can switch one to Auto in the charter after confirming with their second factor. Even then, once an agent has read outside content, such as a customer's email, its tier 3 and 4 actions need a person by default for the rest of that session.
-
Open an issue Tier 3 · External Outside content
Open an issue in a project. Labels that do not exist yet are created. Lines may not start with "/" because GitLab runs them as quick actions (such as /close or /assign); put paths in backticks. Visible to everyone who can see the project.
-
Comment on an issue or merge request Tier 3 · External
Add a comment that everyone who can see the issue or merge request can read; participants are notified. Use add_internal_note for team-only notes. Lines may not start with "/" (GitLab would run them as quick actions such as /merge).
Actions marked Outside content return what people outside your company may have written, such as emails or comments. Agents treat it as information to check, never as instructions.
What can start work
Nothing in GitLab starts agent work by itself. Agents use it while they work on tasks from the board, from other agents or from the sources on the Intake page.
Work an agent can take on
Examples for apps in Developer & IT. What an agent does with GitLab depends on the actions you grant it.
- Sum up new errors or incidents and point out the ones that need a person first.
- Read the latest deployment or build logs when something breaks.
- Comment on issues with what it found.
Set it up
The GitLab setup guide walks through each way to connect: what to set up first and the fields to fill in.
GitLab is a separate service with its own terms. Everdeck isn't affiliated with or endorsed by it.
Your company, always on deck.
Start a 14-day trial. Card first, nothing charged until day 14.