Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Admin resource of a Gitea instance to retrieve all email addresses registered in the system. It is useful for administrators who need to manage or audit user emails, perform bulk operations, or export email lists for communication purposes.

A practical example would be an admin wanting to fetch all user emails paginated by page number and limit per page, to integrate with an external mailing system or for compliance reporting.

Properties

Name Meaning
Page The page number of results to return (1-based). Used for pagination.
Limit The number of results to return per page (page size). Controls how many emails are fetched per request.

Output

The node outputs JSON data containing the list of emails retrieved from the Gitea Admin API. The structure typically includes an array of email objects or strings representing user emails. There is no indication that binary data is output by this node.

Dependencies

  • Requires connection to a Gitea instance via its API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL of the Gitea server must be provided in the credentials configuration.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid page or limit values (e.g., negative numbers) may result in errors or empty responses.
    • Network connectivity problems to the Gitea server can cause request timeouts or failures.
  • Error messages:

    • Authentication errors usually indicate invalid or expired API tokens; verify and update credentials.
    • HTTP 400 or 422 errors may indicate invalid query parameters; ensure page and limit are positive integers.
    • HTTP 500 errors suggest server-side issues; check Gitea server health and logs.

Links and References

Discussion