GiteaInstall

Overview

This node updates a secret associated with an organization in Gitea, a self-hosted Git service. It is useful when you need to programmatically change or rotate secrets (such as tokens, passwords, or keys) stored at the organization level for automation, security, or configuration purposes.

Practical examples include:

• Automatically updating deployment keys or tokens used by CI/CD pipelines.
• Rotating sensitive credentials stored as organization secrets without manual intervention.
• Synchronizing secret values across multiple environments or projects.

Properties

Output

The node outputs JSON data representing the response from the Gitea API after updating the organization secret. This typically includes confirmation details about the updated secret or any relevant metadata returned by the API.

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.
• Depends on the Gitea REST API endpoint /api/v1 for organization secret management.

Troubleshooting

• Common issues:

  • Invalid organization name or secret name will cause the update to fail.
  • Insufficient permissions or invalid API token may result in authorization errors.
  • Network connectivity problems to the Gitea server can cause request failures.

• Error messages and resolutions:

  • 401 Unauthorized: Check that the API key credential is valid and has sufficient permissions.
  • 404 Not Found: Verify that the organization and secret names are correct and exist.
  • 400 Bad Request: Ensure the data format for the secret is valid and properly encoded.
  • Network errors: Confirm the Gitea server URL is reachable and correctly set in credentials.

Links and References

• Gitea API Documentation – Official API docs for managing organizations and secrets.
• n8n Documentation – General guidance on using credentials and HTTP request nodes.