Habitica

Overview

This node integrates with the Habitica API to retrieve various content objects related to the Habitica game environment. Specifically, the "Get All Objects" operation under the "Content" resource fetches multiple types of game data such as achievements, quests, items, pets, mounts, and more. This is useful for workflows that need to access or synchronize Habitica's game content data, for example, to display user progress, generate reports, or customize game-related automations.

Practical examples include:

• Fetching all available quests and their details to create a custom dashboard.
• Retrieving achievement data to track user milestones.
• Accessing item lists or pets information for inventory management or notifications.

Properties

Name	Meaning
Language	The language in which to return the content. Options include many language codes like "en", "de", "fr", "zh_TW", etc. Default is "en".
Return All Keys	Boolean flag indicating whether to return all keys (all content categories) or only selected ones.
Keys	When "Return All Keys" is false, this multi-select property specifies which content keys to return. Options include: achievements, quests, gear, spells, pets, mounts, events, classes, food, backgrounds, faq, and many others representing different content categories in Habitica.

Output

The output JSON contains the requested content objects keyed by their category names. For example, if "quests" and "achievements" are requested, the output will have those keys with corresponding data structures describing each content type.

The structure is essentially a dictionary where each key corresponds to a content category, and its value is the detailed data object for that category as provided by the Habitica API.

No binary data output is indicated for this operation.

Dependencies

• Requires an API key credential for authenticating with the Habitica API.
• The node uses the official Habitica API base URL by default but supports self-hosted API endpoints via configuration.
• No other external services are required.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials will cause authentication errors.
  • Requesting keys not supported or misspelled may result in empty or error responses.
  • Network connectivity issues can prevent successful API calls.

• Error messages:

  • Authentication failures typically indicate invalid or expired API tokens; verify and update credentials.
  • If the API returns errors about unsupported keys, ensure the selected keys are valid and spelled correctly.
  • Timeout or connection errors suggest checking network settings or API availability.

Links and References

• Habitica Official API Documentation
• Habitica Website