Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to list organizations associated with a specific user. It is useful when you want to retrieve all organizations that a given user belongs to within a Gitea instance. Typical use cases include automating user management, auditing user memberships across organizations, or integrating organization data into other workflows.

For example, you might use this node to fetch all organizations for a developer's username to display their affiliations or to synchronize organization membership data with another system.

Properties

Name Meaning
Username The username of the user whose organizations you want to list.
Page The page number of results to return (1-based). Useful for paginating through results.
Limit The maximum number of results to return per page (page size).

Output

The node outputs JSON data containing the list of organizations associated with the specified user. Each item in the output array represents an organization object as returned by the Gitea API, typically including details such as organization ID, name, description, and other metadata.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Gitea API.
  • The node expects the base URL of the Gitea instance to be configured in the credentials.
  • No additional external dependencies are required beyond the Gitea API access.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing a non-existent username will result in empty results or errors from the API.
    • Pagination parameters (Page and Limit) set incorrectly (e.g., zero or negative values) may lead to unexpected results or API errors.
  • Error messages:

    • Authentication errors usually indicate invalid or expired API tokens; verify and update credentials.
    • "User not found" or similar errors suggest the username does not exist on the Gitea instance.
    • Rate limiting errors from the API may require adding delays or reducing request frequency.

Links and References

Discussion