Actions66
- Branch Actions
- File Actions
- Group Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Project Actions
- Raw API Actions
- Release Actions
- Tag Actions
Overview
The "Download Artifacts" operation of the Pipeline resource in this GitLab Extended node allows users to download build artifacts generated by a specific pipeline in a GitLab project. This is useful for automating retrieval of compiled binaries, test reports, or other output files produced during continuous integration (CI) runs.
Typical use cases include:
- Automatically fetching build outputs after a successful pipeline run for deployment or further processing.
- Archiving artifacts from pipelines for audit or backup purposes.
- Integrating artifact downloads into larger automation workflows that depend on pipeline results.
For example, after triggering a pipeline on the main branch, you can use this operation to download the resulting artifacts without manually visiting the GitLab UI.
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. Default: 0 |
| Pipeline ID | Numeric ID of the pipeline whose artifacts you want to download. Must be a positive number. Default: 1 |
| Ref | Branch or tag that triggers the pipeline, such as 'main'. Optional, default is 'main'. |
Output
The node outputs the downloaded artifacts data in the json field of the output items. The exact structure depends on the artifacts returned by the GitLab API but typically includes metadata about the artifacts and their content.
If the artifacts are binary files, the node will handle them accordingly (e.g., providing binary data output), allowing subsequent nodes to process or save these files.
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 pipeline artifacts.
- Supports two authentication modes:
- Using saved credentials configured in n8n.
- Providing custom connection details including server URL and personal access token directly in the node.
Troubleshooting
- Invalid Pipeline ID: Ensure the pipeline ID is a positive integer and corresponds to an existing pipeline in the specified project.
- Authentication Errors: Verify that the access token has the necessary API scopes to read pipeline artifacts.
- Project Identification Issues: If using custom authentication, ensure that either the numeric project ID is provided or both project owner and project name are correctly specified.
- Artifact Not Found: The pipeline may not have generated artifacts or they might have expired. Confirm artifacts exist for the given pipeline.
- Network/Server Errors: Check connectivity to the GitLab server URL and confirm it is reachable from the n8n environment.
Common error messages usually relate to authorization failures, invalid parameters, or missing resources. Reviewing the node's input parameters and GitLab permissions typically resolves these issues.