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 creating new issues in a GitLab project. It is useful for automating issue tracking workflows, such as automatically opening bug reports or feature requests based on external triggers or events. For example, you could use this node to create an issue when a monitoring system detects an error or when a customer submits feedback through a form.
The node supports both using saved credentials and custom authentication fields, allowing flexibility depending on your GitLab setup (cloud or self-hosted).
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved API credentials ("Credential") or specifying custom connection details ("Custom"). |
| GitLab Server | Base URL of the GitLab instance, e.g., https://gitlab.com. Used only if "Custom" authentication is selected. |
| Access Token | Personal access token with API permissions for authenticating requests. 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 | Slug or name of the project. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected. |
| Project ID | Numeric ID of the project. Takes precedence over owner and name if provided. Used only if "Custom" authentication is selected. |
| Title | The title of the issue to create. Required. Example: "Fix login bug". |
| Description | Detailed description of the issue. Optional. Example: "Steps to reproduce the bug...". |
| Labels | Comma-separated list of labels to assign to the issue. Optional. Example: "bug,urgent". |
Output
The node outputs JSON data representing the created issue as returned by the GitLab API. This includes all standard issue fields such as:
id: Internal GitLab issue ID.iid: Issue number within the project.title: Issue title.description: Issue description.state: Current state (e.g., opened).labels: Array of assigned labels.web_url: URL to view the issue in GitLab.
No binary data output is produced by this operation.
Dependencies
- Requires a valid GitLab personal access token with appropriate API permissions to create issues.
- Supports either:
- Using saved credentials configured in n8n.
- Providing custom connection details including server URL, access token, and project identification.
- No additional external dependencies beyond GitLab API access.
Troubleshooting
- Invalid or missing authentication: Ensure that the access token has sufficient permissions to create issues and that the correct authentication method is selected.
- Project identification errors: If both project ID and owner/name are empty or incorrect, the API call will fail. Provide a valid numeric project ID or both owner and project name.
- Invalid labels format: Labels must be comma-separated strings without extra spaces or invalid characters.
- API rate limits or network issues: May cause request failures; check connectivity and GitLab API status.
- Error messages from GitLab API: Usually include HTTP status codes and messages indicating the problem (e.g., 401 Unauthorized, 404 Not Found). Verify credentials and project existence accordingly.