Overview

This node operation allows users to force start a quest for a specified group in Habitica. It is useful in scenarios where a quest needs to be initiated immediately for a group, such as in gaming communities or team productivity setups using Habitica quests.

Use Case Examples

1. Starting a quest for a specific group to encourage team collaboration.
2. Forcing the start of a quest when a scheduled start is delayed or needs to be overridden.

Properties

Name	Meaning
Group	The group to start the quest for, identified either by selecting from a list or by entering a group ID.
Request Options	Additional options to customize the request behavior, including batching, SSL certificate handling, proxy settings, and timeout duration.

Output

JSON

• status - The status of the quest start operation, indicating success or failure.
• message - Additional information or message returned from the quest start request.

Dependencies

• Requires an API key credential for Habitica API authentication.

Troubleshooting

• Ensure the group ID is correctly formatted as a UUID to avoid validation errors.
• If SSL certificate validation fails, consider enabling the 'Ignore SSL Issues' option, but be aware of security risks.
• Check proxy settings if requests fail to reach the Habitica API server.
• Adjust the timeout setting if the server response is slow or times out.