GiteaInstall

Overview

This node interacts with the Gitea API to delete a reaction from a specific issue in a repository. It is useful when you want to programmatically remove a reaction (such as an emoji) that was previously added to an issue, for example, to manage or moderate feedback on issues automatically.

Practical examples include:

• Removing inappropriate or outdated reactions from issues.
• Automating cleanup of reactions based on certain conditions or workflows.
• Managing community engagement by controlling visible reactions on issues.

Properties

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the reaction was successfully removed or provide error details if the deletion failed.

No binary data output is expected from this node.

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 being accessible and the user having permission to delete reactions on issues.

Troubleshooting

• Common Issues:

  • Incorrect repository owner or repo name can cause "not found" errors.
  • Using an invalid or unauthorized API key will result in authentication errors.
  • Specifying an issue index that does not exist will cause failure.
  • Providing an unsupported or incorrect reaction content type may lead to errors.

• Error Messages:

  • 404 Not Found: Check that the owner, repo, and issue index are correct.
  • 401 Unauthorized: Verify that the API key credential is valid and has sufficient permissions.
  • 400 Bad Request: Ensure the reaction content value is valid and supported by Gitea.

Resolving these typically involves verifying input parameters and ensuring proper API credentials.

Links and References

• Gitea API Documentation - Issue Reactions
• Gitea Official Website
• n8n Documentation on Creating Custom Nodes