GitLab API

GitlabTool

Actions905

Overview

This node interacts with the GitLab API to follow a user by their user ID. It is useful in automation workflows where you want to programmatically follow a GitLab user, for example, to keep track of their activities or projects.

Use Case Examples

  1. Automatically follow a GitLab user when a new project is created.
  2. Follow a user based on a trigger event in your workflow to stay updated on their contributions.

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 authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request, default is POST to follow a user.
Path Parameters Parameters included in the API request path, specifically the user ID to follow.

Output

JSON

  • id - The ID of the user being followed.
  • username - The username of the user being followed.
  • name - The full name of the user being followed.
  • state - The state of the user account (e.g., active).
  • avatar_url - URL to the user's avatar image.
  • web_url - URL to the user's GitLab profile.

Dependencies

  • GitLab API authentication token

Troubleshooting

  • Ensure the user ID provided in the path parameters is valid and exists in GitLab.
  • Check that the GitLab API authentication token is correctly configured and has the necessary permissions to follow users.
  • Verify the base URL is correct for your GitLab instance, especially if using a self-hosted GitLab server.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid user ID), and 403 Forbidden (insufficient permissions).

Links

Discussion