Actions23
- Task Actions
- Chat Message Actions
- Skill (Spell) Actions
- User Actions
- Quest Actions
- Group Actions
- Content Actions
- Inbox Actions
Overview
This node integrates with the Habitica API to manage chat messages within groups. Specifically, the "Delete Message" operation under the "Chat Message" resource allows users to delete a specific message from a selected group in Habitica. This is useful for automating moderation tasks, cleaning up outdated or inappropriate messages, or managing group communications programmatically.
Practical examples include:
- Automatically removing system-generated messages after a certain period.
- Deleting user messages flagged by moderation bots.
- Cleaning chat history during scheduled maintenance or updates.
Properties
| Name | Meaning |
|---|---|
| Group | Select the target group where the message exists. You can choose from a list of groups or enter a group ID manually. The group ID must be a UUID string (e.g., "a1abf9df-d89d-4f5e-9e80-26dc3c481042"). |
| Message ID | The unique identifier of the message to delete within the selected group. This is a required string input. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
If the node supports binary data output, it would relate to any attachments or media associated with the chat message, but based on the provided code and properties, the primary output is JSON confirming the deletion status.
Dependencies
- Requires an active connection to the Habitica API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for the API can be either the default Habitica API endpoint or a self-hosted instance, configurable via credentials.
Troubleshooting
- Invalid Group ID Format: If the group ID does not match the UUID format, the node will reject the input. Ensure the group ID is correctly formatted as a UUID.
- Message Not Found: Attempting to delete a message that does not exist or has already been deleted may result in an error. Verify the message ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Confirm that the API key/token is correctly set up in n8n credentials.
- Permission Issues: The authenticated user must have permission to delete messages in the specified group. Lack of permissions will lead to errors.
- Network or API Downtime: Connectivity issues or Habitica API downtime can cause request failures. Check network connectivity and Habitica service status.