rocketkind
Developer Tools

GitLab

GitLab hosts repositories and the work around them — issues, merge requests and CI pipelines.

Authentication

  • API key
  • OAuth 2.0

Actions

Generic API request. Call any GitLab API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

  • Add issue notePost a note (comment) on a GitLab issue.
  • Add merge request notePost a note (comment) on a GitLab merge request's overview.
  • Create issueOpen a new issue in a GitLab project, optionally labelled and assigned.
  • Create merge requestOpen a merge request proposing that sourceBranch be merged into targetBranch within one project.
  • Create pipelineTrigger a CI pipeline run on a branch or tag, optionally passing pipeline variables as key/value pairs that the jobs read as environment variables.
  • Get application settingsRead a self-managed GitLab instance's application settings — among them emailconfirmationsetting, whether new users must confirm their email (off, soft or hard).
  • Get enterprise userRead one enterprise user of a top-level group on GitLab.com — an account whose email is in a domain the group verified — with their email, state, bot and external flags and confirmedat.
  • Get issueRead one GitLab issue by its project-scoped internal id (issueIid) — the number shown in the UI, not the global issue id.
  • Get projectRead one GitLab project by numeric id or by its URL-encoded namespace/project path — which is also how you convert a path you know into the numeric id the other actions accept.
  • Get project memberRead one user's membership of a GitLab project, counting membership inherited from parent groups and granted through invited groups — the effective role, not only direct membership.
  • Get userRead one GitLab user by numeric id.
  • List branchesList the branches in a project's repository.
  • List issuesList the issues in a GitLab project, optionally narrowed by state (opened, closed, all) and by a comma-separated set of labels.
  • List merge requestsList the merge requests on a GitLab project, optionally narrowed by state (opened, closed, merged, all) — the way to find what is awaiting review, or to get an iid before merging.
  • List pipelinesList the CI pipelines run for a GitLab project, most recent first, with each one's ref and status.
  • List projectsList the GitLab projects visible to the connection, optionally narrowed with a search term or restricted with membership to just those the caller belongs to.
  • Merge merge requestDestructiveMerge an open merge request, addressed by its project-scoped internal id (mrIid).
  • Update issueDestructiveUpdate a GitLab issue: retitle it, close or reopen it with stateEvent, or reset its labels.

Triggers

  • Issue and merge request commentsAnswers as an agent on a GitLab project's issues and merge requests: when someone mentions the connection's user in a comment — or, if you choose, assigns them an issue, requests their review, or opens any issue or merge request — the agent replies in its comments, and later comments there continue the conversation.
  • Issue openedStarts when a GitLab project's Issue Hook webhook reports that a new issue was opened, before any comment, label, or state change is applied.
  • Merge request openedStarts when a GitLab project's Merge Request Hook webhook reports that a new merge request was opened, before any review, note, or state change.
  • New or updated issueStarts when a GitLab issue is created or updated.
  • New or updated pipelineStarts when a pipeline in a chosen GitLab project is created or its status changes.
  • New or updated projectStarts when a project visible to the token is created or its metadata changes in GitLab.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.