GitLab
GitLab issues and merge requests (self-hosted supported via base_url).
OCNORA ships 4 typed GitLab operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://gitlab.com/api/v4 through the HTTP node with the same credential.
Before you connect GitLab
- Authentication
- API key
- Credential
- {"token": "glpat-…"} — a personal or project access tokenthe GitLab access tokenthe GitLab personal/project access token
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
- Prerequisites
- The token's user needs the Maintainer or Owner role on the project; GitLab answers 404 (not 403) for a project whose hooks it may not administer, so a 'project not found' at publish usually means the role, not the path. The connection's base_url is the instance — set it for self-hosted GitLab; blank means gitlab.com. Publishing also needs MANTLE_APP_PUBLIC_BASE_URL set to a URL the instance can reach, which for a private instance means reachable from inside its network.
Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.
What you can do with GitLab
Operations, grouped by what they do to your data, plus 1 trigger that start a run.
Create and send 2
Read and search 2
A sample GitLab workflow
- 1Eventtrigger.gitlab_eventStart a run when a GitLab project event arrives (push, merge request, issue, comment, pipeline…).
- 2Download Archivegitlab.download_archiveDownload a project repository snapshot (zip / tar.gz) as a file blob.
- 3Create Issuegitlab.create_issueOpen an issue in a GitLab project.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 4
- Create IssueOpen an issue in a GitLab project.gitlab.create_issue
- Create Merge RequestOpen a merge request in a GitLab project.gitlab.create_merge_request
- Download ArchiveDownload a project repository snapshot (zip / tar.gz) as a file blob.gitlab.download_archive
- List IssuesList issues in a GitLab project.gitlab.list_issues
Where GitLab fits
GitLab questions
- How does OCNORA authenticate with GitLab?
- With a stored API key credential, shaped {"token": "glpat-…"} — a personal or project access token or the GitLab access token or the GitLab personal/project access token. A connection test can check it when you add it.
- What can I automate with GitLab?
- 4 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
- What if the GitLab operation I need is not listed?
- Call https://gitlab.com/api/v4 from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use GitLab?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are GitLab calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Business apps
See your first GitLab workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.