Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to edit a wiki page within a specific repository on a Gitea instance. It is useful for automating updates or corrections to documentation hosted in the repository's wiki, such as adding new information, fixing typos, or updating existing content programmatically.

Practical examples include:

  • Automatically updating project documentation after a deployment.
  • Syncing external documentation sources with the repository wiki.
  • Adding changelog entries or release notes directly into the wiki pages.

Properties

Name Meaning
Owner The username or organization name that owns the repository.
Repo The name of the repository where the wiki page exists.
Page Name The exact name of the wiki page to be edited.
Content Base 64 The new content for the wiki page, encoded in base64 format.
Message Optional commit message summarizing the changes made to the wiki page.
Title The title of the wiki page; leave empty if you want to keep the current title unchanged.

Output

The node outputs JSON data representing the response from the Gitea API after editing the wiki page. This typically includes details about the updated wiki page such as its name, content, and metadata confirming the successful update.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to a Gitea instance via an API key credential.
  • The node expects the base URL of the Gitea server and authentication credentials to be configured in n8n.
  • The API endpoint used is /api/v1 on the configured Gitea server.

Troubleshooting

  • Invalid Repository or Owner: If the owner or repository name is incorrect, the API will return an error indicating the resource was not found. Verify these values carefully.
  • Page Not Found: If the specified wiki page does not exist, the operation may fail. Ensure the page name matches exactly.
  • Content Encoding Issues: The content must be base64 encoded. Failure to encode properly will result in corrupted or unreadable wiki content.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Confirm that the API key is valid and has sufficient permissions.
  • Commit Message Optional: Omitting the commit message is allowed, but providing one helps track changes in the repository history.

Links and References

Discussion