Actions11
Overview
This node provides extended integration with GitLab, allowing users to interact with various GitLab resources such as branches, files, issues, pipelines, and also supports making raw API requests. The "Raw API" resource with the "Request" operation enables users to perform arbitrary HTTP requests directly against the GitLab API endpoints, offering maximum flexibility for advanced use cases not covered by predefined operations.
Typical scenarios include:
- Performing custom GitLab API calls that are not yet supported by the node's built-in operations.
- Accessing experimental or less common GitLab API endpoints.
- Automating workflows requiring specific API interactions tailored to unique project needs.
For example, a user might want to trigger a custom GitLab webhook, update project settings, or query detailed repository statistics by specifying the exact HTTP method, endpoint, and parameters.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with GitLab: either using an Access Token or OAuth2 authentication. |
| Project Owner | The username or group name owning the GitLab project (URL-encoded internally). |
| Project Name | The name of the GitLab repository/project. |
| HTTP Method | The HTTP method to use for the request. Options: DELETE, GET, PATCH, POST, PUT. |
| Endpoint | The API endpoint path relative to the project, starting with /. For example: /issues. |
| Body Parameters | JSON object representing the body content sent with POST, PUT, or PATCH requests. |
| Query Parameters | JSON object representing URL query parameters appended to the request URL. |
Output
The node outputs an array of JSON objects corresponding to the response data from the GitLab API call(s). Each item in the output contains the parsed JSON response under the json property.
If multiple items are processed, the output aggregates all responses into a single array.
The node does not explicitly handle binary data output for this resource-operation combination.
Dependencies
- Requires a valid GitLab API authentication credential, either an access token or OAuth2 token.
- The node depends on internal helper functions to make HTTP requests to GitLab's REST API.
- No additional external services beyond GitLab are required.
- Proper configuration of the GitLab credentials within n8n is necessary.
Troubleshooting
Common Issues:
- Incorrect or missing authentication credentials will cause authorization errors.
- Malformed JSON in "Body Parameters" or "Query Parameters" can lead to request failures.
- Invalid endpoint paths or unsupported HTTP methods may result in API errors.
- URL encoding issues if the project owner or repository names contain special characters; the node encodes slashes but other characters should be verified.
Error Messages:
"Unknown resource"error indicates the selected resource is not recognized by the node.- HTTP 4xx or 5xx errors returned from GitLab indicate client or server-side issues; check the request details and permissions.
Resolution Tips:
- Verify the correctness of the project owner and repository names.
- Ensure the authentication token has sufficient permissions for the requested API action.
- Validate JSON syntax in input fields.
- Use GitLab API documentation to confirm endpoint paths and required parameters.