GitLab Extended icon

GitLab Extended

Extended GitLab node

Overview

This node, named "GitLab Extended," integrates with GitLab's API to perform various operations on GitLab resources. Specifically for the Project - Create operation, it allows users to create a new project within a GitLab instance. This is useful in automation workflows where new projects need to be programmatically created, such as setting up repositories for new teams, initializing projects from templates, or automating project provisioning during onboarding.

Practical examples include:

  • Automatically creating a new project when a new client signs up.
  • Creating multiple projects in bulk based on predefined configurations.
  • Integrating project creation into CI/CD pipelines or other DevOps workflows.

Properties

Name Meaning
Authentication Choose between using saved credentials ("Credential") or specifying custom connection details ("Custom").
GitLab Server Base URL of your GitLab instance (e.g., https://gitlab.com). Used only if "Custom" authentication is selected.
Access Token Personal access token with API permissions for authentication. Used only if "Custom" authentication is selected.
Project Owner Namespace or owner of the project. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected.
Project Name Name of the new project to create. Required.
Project Path URL path (slug) of the new project. Required.
Namespace ID Numeric ID of the namespace under which the project will be created. Optional; defaults to 0 (root namespace).

Output

The node outputs JSON data representing the newly created project as returned by the GitLab API. This typically includes fields such as project ID, name, path, description, visibility settings, URLs, and other metadata about the project.

No binary data output is produced by this operation.

Dependencies

  • Requires access to a GitLab instance, either the public GitLab server (https://gitlab.com) or a self-hosted GitLab server.
  • Requires an API access token with sufficient permissions to create projects.
  • The node supports two authentication modes: using stored credentials or providing custom connection details directly in the node parameters.
  • No additional external dependencies beyond the GitLab API and n8n environment are required.

Troubleshooting

  • Invalid or missing access token: If the personal access token is invalid or lacks necessary permissions, the API request to create a project will fail. Ensure the token has api scope or appropriate project creation rights.
  • Namespace ID issues: Providing an incorrect or unauthorized namespace ID may cause errors or unexpected project placement. Verify the namespace ID exists and the token has permission to create projects there.
  • Project name/path conflicts: Attempting to create a project with a name or path that already exists in the target namespace will result in an error. Use unique names/paths or handle errors gracefully.
  • API endpoint errors: Network issues or incorrect GitLab server URLs can cause failures. Confirm the server URL is reachable and correct.
  • JSON parsing errors: Although not typical for this operation, ensure any optional JSON inputs (not applicable here) are valid if used.

Common error messages usually come directly from the GitLab API and indicate issues like authentication failure, validation errors, or permission denials. Reviewing the error message details helps identify the root cause.

Links and References


If you need further details on other operations or resources, feel free to ask!

Discussion