GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node interacts with the GitLab API to create new applications via the POST /api/v4/applications endpoint. It is useful for automating the creation of OAuth applications or other app registrations within a GitLab instance. For example, it can be used in workflows that need to programmatically register new applications for integration or automation purposes.

Use Case Examples

  1. Creating a new OAuth application in GitLab automatically when a new project is set up.
  2. Automating the registration of applications for GitLab integrations in a CI/CD pipeline.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method to use for the API request, defaulting to GET but can be set to POST, PUT, DELETE, HEAD, or PATCH.
Parameter Schema Defines the schema for the parameters sent in the request body for the postApiV4Applications operation.
Request Body Schema Defines the schema for the request body content for the postApiV4Applications operation.
Request Path The API endpoint path for creating applications, set to /api/v4/applications.

Output

JSON

  • id - The unique identifier of the created application.
  • name - The name of the created application.
  • redirect_uri - The redirect URI registered for the application.
  • scopes - The scopes granted to the application.
  • created_at - Timestamp when the application was created.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the GitLab API key credential is correctly configured and has sufficient permissions to create applications.
  • Verify the baseUrl is correct and accessible from the environment where the node runs.
  • Check that the request body matches the expected schema for creating applications to avoid validation errors.
  • Common error messages include authentication failures (401 Unauthorized) and validation errors (400 Bad Request) which can be resolved by correcting credentials and request payload respectively.

Links

Discussion