GitLab API

GitlabTool

Actions1000

Overview

This node operation retrieves bulk import data from the GitLab API (version 4). It is useful for scenarios where users need to fetch information about bulk import jobs, such as their status, sorting order, and pagination details. For example, a user can get a list of bulk imports filtered by status or sorted by creation date.

Use Case Examples

  1. Fetch the first page of bulk imports with 20 items per page, sorted by creation date in descending order.
  2. Retrieve bulk imports filtered by status 'finished' to monitor completed import jobs.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
baseUrl The base URL of the GitLab instance to send the request to.
Method HTTP method to use for the request (GET, POST, PUT, DELETE, HEAD, PATCH).
Query Parameters Parameters to filter and paginate the bulk imports data.

Output

JSON

  • id - Unique identifier of the bulk import.
  • status - Current status of the bulk import.
  • created_at - Timestamp when the bulk import was created.
  • updated_at - Timestamp when the bulk import was last updated.
  • user_id - Identifier of the user who initiated the bulk import.
  • entity_type - Type of entity being imported.
  • source_type - Source type of the import.
  • configuration - Configuration details of the bulk import.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the baseUrl is correctly set to the GitLab instance URL.
  • Verify that the authentication token is valid and has sufficient permissions to access bulk imports.
  • Check query parameters for correct data types and valid values, especially for 'status' and 'sort'.
  • Common error messages include authentication failures (401 Unauthorized) and invalid parameter errors (400 Bad Request). Resolving these involves correcting credentials and query parameters respectively.

Links

Discussion