Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea instance to retrieve the revision history of a specific wiki page within a repository. It is useful for users who want to track changes, audit edits, or display historical versions of documentation maintained in a repository's wiki.

Practical examples include:

  • Displaying all past revisions of a wiki page to understand how content evolved.
  • Auditing contributions by different users on a wiki page.
  • Integrating wiki revision data into other workflows or dashboards.

Properties

Name Meaning
Owner The username or organization name that owns the repository.
Repo The name of the repository containing the wiki page.
Page Name The exact name of the wiki page whose revisions you want to retrieve.
Page The page number of results to return (for pagination), starting at 1. Defaults to 0 (no pagination).

Output

The node outputs JSON data representing the list of revisions for the specified wiki page. Each revision typically includes metadata such as revision ID, author, timestamp, and possibly a commit message or summary of changes.

If the node supports binary data output (not indicated here), it would likely relate to attachments or snapshots of the wiki page content at each revision, but this is not evident from the provided code.

Dependencies

  • Requires access to a Gitea instance with API enabled.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL of the Gitea server must be set in the credentials.
  • Uses the Gitea REST API endpoint for wiki page revisions.

Troubleshooting

  • Common issues:

    • Incorrect owner or repo names will result in "Not Found" errors.
    • Missing or invalid API credentials will cause authentication failures.
    • Requesting a non-existent wiki page name will return an error or empty results.
    • Pagination parameters out of range may yield empty responses.
  • Error messages:

    • 401 Unauthorized: Check that the API token is valid and has sufficient permissions.
    • 404 Not Found: Verify the owner, repo, and page name are correct.
    • 400 Bad Request: Ensure the page number parameter is a positive integer if used.

Links and References

Discussion