Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node allows administrators to edit user accounts in a Gitea instance via its API. It is useful for managing user details and permissions programmatically within an automation workflow. Common scenarios include updating user profiles, changing access rights, enabling or disabling accounts, and modifying repository creation limits.

For example, an admin could automate the process of deactivating users who have left an organization or update user roles based on changes in team structure.

Properties

Name Meaning
Username The username of the user to edit (required).
Active Whether the user account is active (true/false).
Admin Whether the user has administrative privileges (true/false).
Allow Create Organization Permission to create organizations (true/false).
Allow Git Hook Permission to use Git hooks (true/false).
Allow Import Local Permission to import repositories locally (true/false).
Description A description or notes about the user.
Email The user's email address.
Full Name The full name of the user.
Location The user's location.
Login Name The login name for the user (required).
Max Repo Creation Maximum number of repositories the user can create (number).
Must Change Password Whether the user must change their password on next login (true/false).
Password The user's password.
Prohibit Login Whether the user is prohibited from logging in (true/false).
Restricted Whether the user is restricted (true/false).
Source Id The source ID for the user (required, number).
Visibility The visibility level of the user (string).
Website The user's website URL.

Output

The node outputs JSON data representing the updated user object as returned by the Gitea API. This typically includes all user properties such as username, email, permissions, and status after the edit operation.

No binary data output is involved.

Dependencies

  • Requires an API key credential with appropriate permissions to manage users in the Gitea instance.
  • The node uses the Gitea API endpoint configured via credentials, specifically targeting /api/v1 base URL.
  • Proper network access to the Gitea server is necessary.

Troubleshooting

  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions to edit users.
  • User not found: Verify that the username specified exists in the Gitea instance.
  • Invalid input values: Check that required fields like username, login_name, and source_id are provided and correctly formatted.
  • Permission denied: Confirm that the authenticated user has admin rights to perform user edits.
  • API connectivity issues: Validate the base URL and network connectivity to the Gitea server.

Links and References

Discussion