GiteaInstall

Overview

This node operation marks a notification thread as read or changes its status. It is useful in scenarios where you want to programmatically update the status of notifications, for example, marking all messages in a notification thread as read after processing them or acknowledging them in an automated workflow.

Practical examples include:

• Automatically marking notification threads as read once they have been processed by another system.
• Changing the status of notification threads to track which ones have been acknowledged or require further action.

Properties

Output

The node outputs JSON data representing the result of the status update operation on the notification thread. This typically includes confirmation that the thread's status was changed and may contain updated details of the notification thread.

No binary data output is indicated.

Dependencies

• Requires an API key credential to authenticate with the Gitea API.
• The base URL for the API must be configured in the credentials.
• The node uses the Gitea API endpoint /api/v1 to perform operations.

Troubleshooting

• Missing or invalid Id: If the Id property is not provided or incorrect, the API call will fail. Ensure the correct notification thread ID is supplied.
• Authentication errors: If the API key or credentials are missing or invalid, the node will not be able to connect to the Gitea API. Verify the API key and base URL configuration.
• Unsupported status values: If an unsupported value is given for To Status, the API might reject the request. Use valid status strings recognized by the Gitea notification system.
• Network issues: Connectivity problems to the Gitea server will cause failures. Check network access and server availability.

Links and References

• Gitea API Documentation (for reference on notification endpoints)
• n8n documentation on creating custom nodes