GitLab Extended icon

GitLab Extended

Extended GitLab node
Join our community

Actions66

Overview

The "GitLab Extended" node integrates with GitLab to perform various operations on GitLab resources. Specifically, the Branch - Get Many operation retrieves multiple branches from a specified GitLab project. This is useful for scenarios where you want to list all branches or filter branches by name within a project.

Common use cases include:

  • Automating branch management workflows.
  • Synchronizing branch information with other tools.
  • Auditing or reporting on repository branches.
  • Triggering actions based on branch existence or status.

For example, you could use this node to fetch all branches of a project and then trigger deployments or notifications based on branch names or patterns.

Properties

Name Meaning
Authentication Choose how to authenticate: either using saved credentials ("Credential") or providing custom fields such as server URL and access token ("Custom").
GitLab Server Base URL of your GitLab instance (e.g., https://gitlab.com). Only shown if "Custom" authentication is selected.
Access Token Personal access token with API permissions for GitLab. Only shown if "Custom" authentication is selected.
Project Owner Namespace or owner of the project. Ignored if "Project ID" is set. Only shown if "Custom" authentication is selected.
Project Name Project slug or name. Ignored if "Project ID" is set. Only shown if "Custom" authentication is selected.
Project ID Numeric project ID. Takes precedence over owner and name if provided. Only shown if "Custom" authentication is selected.
Branch Optional branch name filter, e.g., feature/login. If provided, the node will filter branches matching this name.
Return All Whether to return all results or limit the number of returned branches. Defaults to false (limited).
Limit Maximum number of branches to return when "Return All" is false. Default is 50.

Output

The node outputs an array of JSON objects representing branches retrieved from the GitLab project. Each object typically contains branch details such as:

  • Branch name
  • Commit information (SHA, message, author, etc.)
  • Protection status
  • Other metadata related to the branch

The output is structured as standard JSON data under the json field of each item. This allows further processing or routing in n8n workflows.

This node does not output binary data.

Dependencies

  • Requires access to a GitLab instance, either the public GitLab.com or a self-hosted GitLab server.
  • Requires an API access token with appropriate permissions to read project branches.
  • Supports two authentication modes:
    • Using saved credentials configured in n8n.
    • Providing custom connection details and access token directly in the node parameters.

No additional external dependencies are required beyond network access to the GitLab API.

Troubleshooting

  • Invalid or missing credentials: The node validates that project credentials are present and valid. Ensure your access token has sufficient permissions to read branches.
  • Project identification issues: If both Project ID and Project Owner/Name are provided, Project ID takes precedence. Make sure the project exists and the ID or namespace/name is correct.
  • API rate limits or connectivity errors: Network issues or GitLab API rate limiting may cause failures. Check your network and GitLab API usage.
  • Empty results: If no branches are returned, verify the project contains branches and the optional branch filter matches existing branch names.
  • JSON parsing errors: Not applicable for this operation but relevant for other operations that accept JSON input.

Links and References

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

Discussion