DocumentationWorkflowsHTTP and developer tools
GitLab node
Creates issues in a GitLab project, lists them with an optional status filter, and adds comments (notes) to existing issues. Uses the official gitlab.com API. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
8 min readUpdated
What this node does
Creates issues in a GitLab project, lists them with an optional status filter, and adds comments (notes) to existing issues. Uses the official gitlab.com API.
Use GitLab as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add GitLab from the node catalog.
- 02Complete the required fields and map values from previous steps.
- 03Run the node with a small test record and inspect its output.
- 04Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Choose the required function in Action. The panel then shows the relevant settings.
- Create issue
- List issues
- Add comment
Settings
| Field | Meaning | Area |
|---|---|---|
| GitLab access token | Pick the workflow secret holding your GitLab personal or project access token, or create a new one right here. The token is NEVER stored in the workflow, only the secret name. Sent as a PRIVATE-TOKEN header. | Protected |
| Action | Choices: Create issue, List issues, Add comment | Standard |
| Project ID | Numeric project ID or raw project path, for example group/project. The workflow handles URL encoding safely. | Standard |
| Title | Configure this value in the node panel. | Standard |
| Description | Configure this value in the node panel. | Standard |
| Status filter | Choices: Open, Closed, All | Standard |
| Issue IID | The project-local issue number (IID), not the global issue ID. | Standard |
| Comment text | Configure this value in the node panel. | Standard |
| Run once per item | Off (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry. | Standard |
| If one item fails | "Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file. | Standard |
| Pause between items (milliseconds) | Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes). | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
This node can process lists item by item. Error handling and the delay between items are available in advanced settings.
Example and test run
Create a bug report from chat: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"project_id": "12345678",
"title": "Login schlägt fehl nach Passwort-Reset",
"description": "Ein Kunde meldet, dass der Login nach einem Passwort-Reset mit Fehler 500 fehlschlägt."
}Access and security
Before activation, review which data enters this step and what its output contains.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.
- List processed once: enable per-item execution in advanced settings.