Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to list blocks associated with a specific organization. It is useful when you want to retrieve paginated data about blocks within an organization in Gitea, such as for auditing, monitoring, or integration purposes.

A practical example would be automating the retrieval of organizational block data to feed into dashboards or reports, or to trigger workflows based on the presence or absence of certain blocks.

Properties

Name Meaning
Org The name of the organization whose blocks you want to list.
Page The page number of results to return (1-based). Used for pagination.
Limit The number of results per page (page size). Controls how many blocks are returned each request.

Output

The node outputs JSON data representing the list of blocks for the specified organization. The structure corresponds to the API response from Gitea's endpoint for listing organization blocks, typically including details about each block.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in credentials.
  • Relies on the Gitea REST API v1 endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Incorrect organization name may result in empty results or not found errors.
    • Pagination parameters (page and limit) set incorrectly (e.g., zero or negative values) might lead to unexpected responses or errors.
  • Error messages:

    • Authentication failures: Check that the API key and base URL are correctly configured.
    • Not found errors: Verify the organization name exists and is spelled correctly.
    • Rate limiting or API quota exceeded: Ensure your API usage complies with Gitea limits.

Links and References

Discussion