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 enables searching for projects within a GitLab instance. It is useful when you want to find projects by name or other searchable terms programmatically, such as automating project discovery or filtering projects based on keywords.
Typical use cases include:
- Automating the retrieval of project details matching specific search criteria.
- Integrating GitLab project search into workflows that require dynamic project selection.
- Filtering projects before performing further operations like cloning, updating, or reporting.
For example, you can input a search term like "frontend" to get all projects related to frontend development in your GitLab instance.
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. 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 | Project slug or name. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected. |
| Project ID | Numeric project ID. Takes precedence over owner and name if provided. Used only if "Custom" authentication is selected. |
| Search Term | (Required) The term to search for among projects. |
Output
The node outputs an array of JSON objects representing the projects found by the search query. Each object contains project details as returned by the GitLab API's project search endpoint, such as project ID, name, description, visibility, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires access to a GitLab instance, either the public
https://gitlab.comor a self-hosted GitLab server. - Requires an API access token with sufficient permissions to read project information.
- Supports two authentication modes: using stored credentials or custom authentication parameters.
- No additional external dependencies beyond standard HTTP requests to the GitLab API.
Troubleshooting
- Empty results: Ensure the search term is correctly specified and matches existing projects. Also verify that the access token has permission to view the projects.
- Authentication errors: Check that the access token is valid and has the necessary API scopes. If using custom authentication, verify the GitLab server URL and token are correct.
- Invalid project ID or parameters: When using custom authentication, ensure numeric project IDs and other parameters are positive integers where required.
- API rate limits: If many requests are made in a short time, GitLab may throttle API calls. Consider adding delays or reducing request frequency.
Common error messages:
- "Unknown resource: project" — This indicates a misconfiguration in the resource parameter; ensure it is set to "project".
- "tagName must not be empty" — Not applicable here but seen in other operations; ensure required fields are filled.
- Network or permission errors typically indicate issues with the access token or server URL.