Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows editing a team within an organization on a Gitea server via its API. It is useful for managing team settings such as permissions, repository access, and descriptive information programmatically. Typical scenarios include automating team updates during organizational changes, syncing team configurations from external systems, or bulk updating team permissions.

For example, you can update a team's permission level to "admin", change its description, or modify which repositories the team has access to, all through this node.

Properties

Name Meaning
Id The unique identifier of the team to edit (required).
Can Create Org Repo Boolean flag indicating if the team can create repositories in the organization.
Description Text description of the team.
Includes All Repositories Boolean flag indicating if the team includes all repositories in the organization.
Name The name of the team (required).
Permission The permission level granted to the team. Options: Read, Write, Admin.
Units JSON array specifying repository units/features the team has access to, e.g., code, issues.
Units Map JSON object mapping each unit to a specific permission level, e.g., "repo.code": "read".

Output

The node outputs JSON data representing the updated team object returned by the Gitea API after the edit operation. This typically includes the team's id, name, description, permissions, repository access details, and other metadata reflecting the new state of the team.

No binary data output is involved.

Dependencies

  • Requires connection to a Gitea instance with appropriate API access.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the Gitea API must be set in the credentials.

Troubleshooting

  • Invalid Team ID: If the provided team id does not exist, the API will return an error. Verify the team id before running the node.
  • Insufficient Permissions: The API token used must have rights to edit teams; otherwise, permission errors occur.
  • Malformed JSON: The units and units_map properties expect valid JSON strings. Invalid JSON will cause parsing errors.
  • Network Issues: Ensure the Gitea server URL is reachable and correct in credentials.
  • Missing Required Fields: The id and name fields are mandatory; omitting them will cause validation errors.

Links and References

Discussion