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 retrieve multiple chat messages from a specified group. It is useful for scenarios where you want to fetch and process all chat messages within a particular Habitica group, such as monitoring group discussions, archiving conversations, or triggering workflows based on new messages.
For example, you could use this node to:
- Automatically gather all chat messages from a project group to analyze team communication.
- Trigger notifications or actions when certain keywords appear in group chats.
- Archive group chat history for record-keeping or compliance purposes.
Properties
| Name | Meaning |
|---|---|
| Group | Select the Habitica group from which to retrieve chat messages. You can either select from a list of groups or enter a specific group ID manually. The group ID must be a UUID string (e.g., "a1abf9df-d89d-4f5e-9e80-26dc3c481042"). |
Output
The node outputs an array of chat message objects in the json output field. Each object represents a single chat message retrieved from the specified group. The structure typically includes details such as message content, sender information, timestamps, and any associated metadata.
If the node supports binary data output (not evident from the provided code), it would represent attachments or media related to chat messages; however, no explicit binary output handling is indicated here.
Dependencies
- Requires an active connection to the Habitica API using a valid API authentication token configured in the node credentials.
- The base URL for API requests can be customized if using a self-hosted Habitica instance; otherwise, it defaults to the official Habitica API endpoint.
- No additional external services are required beyond Habitica's API.
Troubleshooting
- Invalid Group ID Format: If the group ID does not match the expected UUID format, the node will likely throw a validation error. Ensure the group ID is correctly formatted.
- Authentication Errors: Missing or invalid API credentials will prevent the node from accessing Habitica data. Verify that the API key credential is correctly set up.
- Empty Results: If no chat messages are returned, confirm that the specified group contains messages and that the user has permission to access them.
- API Rate Limits: Habitica may impose rate limits; excessive requests might result in temporary blocking. Implement retry logic or reduce request frequency if needed.