Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation checks whether a specified user is a public member of a given organization on Gitea, a self-hosted Git service. It is useful for workflows that need to verify membership status before performing actions such as granting access, sending notifications, or managing permissions based on organizational affiliation.

For example, you might use this node to:

  • Confirm if a user publicly belongs to an organization before allowing them to access certain resources.
  • Automate team management by verifying membership status in an organization.
  • Trigger alerts or workflows when a user's public membership status changes.

Properties

Name Meaning
Org The name of the organization to check membership against.
Username The username of the user whose public membership status is being checked.

Output

The node outputs JSON data indicating whether the specified user is a public member of the given organization. The exact structure depends on the API response but typically includes a boolean or membership details confirming the public membership status.

If the node supports binary data output (not evident from the provided code), it would relate to any associated files or media returned by the API, but this is unlikely for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in the credentials.
  • Depends on the Gitea REST API endpoint /orgs/{org}/public_members/{username} or equivalent to check public membership.

Troubleshooting

  • Common issues:

    • Invalid organization or username input leading to "Not Found" errors.
    • Authentication failures due to missing or incorrect API credentials.
    • Network connectivity problems preventing access to the Gitea server.
  • Error messages and resolutions:

    • 404 Not Found: Verify that the organization and username exist and are spelled correctly.
    • 401 Unauthorized: Check that the API key credential is valid and has sufficient permissions.
    • Network errors: Ensure the Gitea server URL is reachable and correct in the credentials.

Links and References

Discussion