Actions23
- Task Actions
- Chat Message Actions
- Skill (Spell) Actions
- User Actions
- Quest Actions
- Group Actions
- Content Actions
- Inbox Actions
Overview
This node interacts with the Habitica API to retrieve detailed information about a specific group within the Habitica platform. It is useful for scenarios where users want to fetch metadata or status about a group they belong to or manage, such as group name, members, description, or other group-related data.
Practical examples include:
- Displaying group details in a workflow after selecting a group.
- Automating reports or notifications based on group info.
- Integrating Habitica group data into other systems or dashboards.
Properties
| Name | Meaning |
|---|---|
| Group | The target group to get information for. Can be selected from a list of groups or specified by its unique ID (UUID format). |
The "Group" property supports two modes:
- List: Select from a searchable list of available groups.
- ID: Enter the group's UUID directly (must match the pattern
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
Output
The node outputs JSON data containing the full information of the requested group as returned by the Habitica API. This typically includes fields such as group ID, name, description, members, and other metadata relevant to the group.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Habitica API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- Uses the base URL either from the default Habitica API endpoint or a self-hosted instance if specified in credentials.
Troubleshooting
- Invalid Group ID Format: If the entered group ID does not match the UUID regex pattern, the node will reject it. Ensure the ID is correctly formatted.
- Group Not Found: If the group ID or selected group does not exist or the authenticated user lacks access, the API may return an error or empty result.
- Authentication Errors: Missing or invalid API credentials will cause request failures. Verify that the API key/token is correctly set up.
- Network Issues: Connectivity problems to the Habitica API endpoint can cause timeouts or errors.