Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation retrieves a paginated list of team members belonging to a specific team within an organization. It is useful when you want to manage or analyze the members of a team, for example, to audit team composition, synchronize team members with another system, or display team member information in a dashboard.

Practical examples:

  • Fetching all members of a development team to send them notifications.
  • Listing team members to verify access permissions.
  • Integrating team membership data into HR or project management tools.

Properties

Name Meaning
Id The unique identifier (ID) of the team whose members you want to list.
Page The page number of results to return (1-based). Useful for paginating through large lists.
Limit The maximum number of results to return per page (page size).

Output

The output contains a JSON array of team member objects corresponding to the specified team. Each object typically includes details about a team member such as their user ID, username, and other relevant metadata provided by the API.

If the API supports it, pagination metadata may also be included implicitly via the request parameters but is not explicitly detailed here.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating requests to the Gitea API.
  • The base URL for the Gitea instance must be configured in the node credentials.
  • The node uses the Gitea REST API endpoint /api/v1 to fetch team members.

Troubleshooting

  • Invalid Team ID: If the provided team ID does not exist or is incorrect, the API will likely return an error or empty result. Verify the team ID before running the node.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and base URL are correctly set in the node credentials.
  • Pagination Issues: Providing invalid page or limit values (e.g., negative numbers) might cause errors or unexpected results. Use positive integers starting from 1 for page and sensible limits.
  • API Rate Limits: If the Gitea server enforces rate limits, frequent calls may be throttled. Implement retry logic or reduce request frequency if needed.

Links and References

Discussion