Nodes2Cloud
Nodes2CloudDocs
Integrations

GitLab

Automate GitLab issues and repository management

GitLab Integration

The GitLab integration allows you to automate issue tracking and repository operations within your GitLab projects.

How to get credentials

To use the GitLab node, you need a Personal Access Token (PAT).

  1. Go to your GitLab account Preferences (or Settings).
  2. Navigate to Access Tokens.
  3. Click Add new token.
  4. Give your token a name and an expiration date.
  5. Select the required scopes. You will need api scope for full access, or read_api / read_repository if you only need to read data.
  6. Click Create personal access token and copy the resulting string.
  7. In Nodes2Cloud, create a new GitLab credential and paste this token.

(Note: If you are using a self-hosted GitLab instance, ensure your network allows the Nodes2Cloud worker to reach your instance).


1. Issue Operations

What they do

Create, update, read, and manage issues and issue comments on a GitLab project.

Available Actions

  • Issue: Create: Creates a new issue in a project.
  • Issue: Get: Retrieves a single issue by its internal IID.
  • Issue: Update: Modifies an existing issue.
  • Issue: Add Comment: Posts a new comment (note) to an existing issue.

Common Fields

  • Credential: Your GitLab Personal Access Token.
  • Project ID: The ID or URL-encoded path of the project (e.g., 12345 or username%2Fproject-name).
  • Issue IID: The internal ID of the specific issue (the number you see in the issue URL, not the global database ID).
  • Title / Description: (For Create/Update) The text contents of the issue.

2. Repository Operations

Available Actions

  • Repository: List Commits: Retrieves a list of recent commits on a repository.

Options / Fields

  • Project ID: The ID or URL-encoded path of the project.
  • Branch: (Optional) The specific branch to list commits for.

Common Troubleshooting

  • 404 Not Found / Project Not Found: This usually means your Personal Access Token does not have access to the project, or the Project ID is incorrect. If using the project path (e.g., group/repo), ensure it is URL-encoded (e.g., group%2Frepo).
  • Cannot update issue state: When using Issue: Update, you change the state of an issue by passing a state event (e.g., close or reopen), rather than directly editing a status field.

On this page