GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation allows users to create a new wiki page in a specific GitLab project by sending a POST request to the GitLab API endpoint `/api/v4/projects/{id}/wikis`. It is useful for automating the management of project documentation within GitLab, such as adding or updating wiki pages programmatically.

Use Case Examples

  1. Automatically create or update project wiki pages as part of a CI/CD pipeline.
  2. Integrate with other tools to maintain project documentation in GitLab wikis without manual intervention.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip using 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, defaulting to https://gitlab.com.
Method The HTTP method to use for the API request, defaulting to POST for this operation.
Path Parameters Parameters included in the API request path, specifically the project ID (`id`) identifying the GitLab project where the wiki page will be created.

Output

JSON

  • id - The unique identifier of the created wiki page.
  • title - The title of the created wiki page.
  • content - The content/body of the created wiki page.
  • format - The format of the wiki page content (e.g., markdown).
  • slug - The URL-friendly slug of the wiki page.
  • created_at - Timestamp when the wiki page was created.
  • updated_at - Timestamp when the wiki page was last updated.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID (`id`) path parameter is correctly set and corresponds to an existing GitLab project.
  • Verify that the authentication credentials (GitLab API key) are valid and have sufficient permissions to create wiki pages in the target project.
  • Check the request body schema to ensure all required fields for creating a wiki page are included and correctly formatted.
  • Common error messages include 401 Unauthorized (invalid or missing authentication), 404 Not Found (project ID does not exist), and 400 Bad Request (invalid request body). Resolving these involves correcting credentials, verifying project existence, and validating request data respectively.

Links

Discussion