Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node enables creating a new organization in a Gitea instance via its API. It is useful for automating the management of organizations within Gitea, such as setting up new teams or groups programmatically without manual intervention through the web interface.

Practical examples include:

  • Automatically creating an organization when onboarding a new project or client.
  • Integrating with other systems to sync organizational data into Gitea.
  • Bulk creation of organizations based on external data sources.

Properties

Name Meaning
Description A textual description of the organization.
Email Contact email address for the organization.
Full Name The full display name of the organization.
Location Physical or geographical location of the organization.
Repo Admin Change Team Access Boolean flag indicating if repository admins can change team access (true/false).
Username (Required) The unique username identifier for the organization.
Visibility Organization visibility level; options are: public, limited, or private.
Website URL of the organization's website.

Output

The node outputs JSON data representing the newly created organization object returned by the Gitea API. This typically includes fields such as the organization's ID, username, full name, description, email, location, visibility status, and other metadata.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in the credentials.
  • The node uses the Gitea REST API v1 endpoint /api/v1 to perform operations.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or missing API credentials.
    • Validation errors if required fields like username are missing or invalid.
    • Permission errors if the API user does not have rights to create organizations.
    • Network connectivity problems to the Gitea server.
  • Error messages and resolutions:

    • 401 Unauthorized: Check that the API key credential is correct and has sufficient permissions.
    • 400 Bad Request: Verify all required properties are provided and valid, especially username.
    • 403 Forbidden: Ensure the authenticated user has organization creation privileges.
    • Network errors: Confirm the Gitea server URL is reachable and correct.

Links and References

Discussion