Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to create or update a wiki page in a specified repository on a Gitea instance. It is useful for automating documentation updates, adding new wiki content, or maintaining project notes directly from your workflows without manually accessing the repository interface.

Practical examples include:

  • Automatically generating and committing release notes or changelogs as wiki pages after deployment.
  • Creating or updating project documentation pages based on external data sources.
  • Managing collaborative wiki content programmatically within CI/CD pipelines.

Properties

Name Meaning
Owner The username or organization name that owns the repository where the wiki page resides.
Repo The name of the repository to which the wiki page belongs.
Content Base 64 The content of the wiki page, encoded in base64 format.
Message An optional commit message summarizing the change made to the wiki page.
Title The title of the wiki page. Leave empty to keep the existing title unchanged.

Output

The node outputs JSON data representing the response from the Gitea API after creating or updating the wiki page. This typically includes details about the committed wiki page such as its URL, commit SHA, and metadata confirming the successful operation.

No binary data output is produced by this node operation.

Dependencies

  • Requires an active connection to a Gitea instance with appropriate API access.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The node uses the Gitea REST API endpoint /api/v1 as the base URL, which must be correctly set in the credentials.

Troubleshooting

  • Authentication errors: Ensure the API token credential is valid and has sufficient permissions to write to the repository's wiki.
  • Invalid base64 content: The Content Base 64 property must be properly base64 encoded; otherwise, the API will reject the request.
  • Repository not found: Verify that the Owner and Repo names are correct and that the authenticated user has access rights.
  • Empty title issues: If updating an existing page, leaving the Title empty keeps it unchanged; however, when creating a new page, a title is required.
  • Commit message missing: While optional, providing a meaningful commit message helps track changes better and avoid ambiguous commits.

Links and References

Discussion