Actions66
- Branch Actions
- File Actions
- Group Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Project Actions
- Raw API Actions
- Release Actions
- Tag Actions
Overview
This node interacts with GitLab's API to manage projects and other related resources. Specifically, the Project - Get operation fetches detailed information about a single GitLab project by its numeric ID. This is useful when you want to retrieve metadata or configuration details of a specific project hosted on GitLab.
Common scenarios include:
- Automating workflows that require project details such as visibility, description, or repository URLs.
- Integrating GitLab project data into dashboards or reporting tools.
- Triggering downstream actions based on project attributes.
Example: You might use this node to get the project info for project ID 12345 to check its current settings before creating a new pipeline or merge request programmatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved credentials ("Credential") or entering custom connection details ("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 authentication. 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 ID of the project to fetch. Required for the "Get" operation under the "Project" resource. Default is 1. |
Output
The output is a JSON object representing the full details of the requested GitLab project. This includes all standard project fields returned by the GitLab API, such as:
- Project ID
- Name and path
- Description
- Visibility level
- Web URL
- SSH and HTTP clone URLs
- Creation date
- Last activity date
- Default branch
- And many other metadata fields provided by GitLab
The node outputs this data in the json field of the item, allowing further processing or routing within n8n workflows.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential or personal access token with appropriate permissions to read project information from GitLab.
- If using custom authentication, the user must provide the GitLab server URL and a valid access token.
- The node depends on internal helper functions to build the API request URL and handle authentication.
- No additional external dependencies beyond the GitLab API and n8n environment are required.
Troubleshooting
- Invalid Project ID: If the project ID is missing, zero, or invalid, the node will throw an error. Ensure the project ID is a positive integer.
- Authentication Errors: If the access token is invalid or lacks sufficient permissions, the API call will fail. Verify the token scopes and validity.
- Network Issues: Connection problems to the GitLab server URL can cause failures. Confirm the server URL is reachable and correct.
- API Rate Limits: Excessive requests may trigger rate limiting by GitLab. Implement retry logic or reduce request frequency.
- Unexpected Resource or Operation: The node expects the resource to be "project" and operation to be "get" for this summary. Using unsupported combinations will result in errors.