Overview

This node operation allows users to accept a quest within a specified group in the Habitica application. It is useful for automating the process of joining quests in Habitica, especially for users managing multiple groups or quests programmatically. For example, a user can automate accepting a quest in a group to streamline task management and collaboration within Habitica.

Use Case Examples

1. Automatically accept a quest in a specific group when certain conditions are met in a workflow.
2. Batch accept quests across multiple groups to manage group activities efficiently.

Properties

Name	Meaning
Group	The group in which the quest is to be accepted. This is a required field and can be selected either from a list of groups or by entering a group ID manually.
Request Options	Additional options to customize the request behavior, including batching, SSL certificate validation, proxy settings, and request timeout.

Output

JSON

• questAccepted - Indicates whether the quest was successfully accepted.
• groupId - The ID of the group in which the quest was accepted.

Dependencies

• Habitica API with an API key credential for authentication

Troubleshooting

• Ensure the group ID is valid and correctly formatted as a UUID to avoid validation errors.
• If SSL certificate validation fails and the request is blocked, consider enabling the 'Ignore SSL Issues' option, but be aware of security risks.
• Check proxy settings if requests fail to connect to the Habitica API through a proxy.
• Adjust the timeout setting if the server response is slow to prevent premature request abortion.