Habitica Trigger icon

Habitica Trigger

Handle Habitica events via webhooks

Overview

The Habitica Trigger node listens for various Habitica events via webhooks and triggers workflows based on those events. It supports events such as task scoring, task creation, task updates, task deletion, group chat messages, quest activities, and user activities. This node is useful for automating actions in response to Habitica events, such as updating external systems when a task is scored or sending notifications when a group chat message is received.

Use Case Examples

  1. Trigger a workflow when a specific task is scored to update a project management tool.
  2. Start a workflow when a group chat message is received to send alerts to a communication channel.
  3. Automate user level-up notifications by triggering workflows on the 'Leveled Up' event.

Properties

Name Meaning
Event The specific Habitica event to listen for, such as taskScored, taskCreated, groupChatMessageReceived, etc.
All Tasks Whether to receive webhooks for all tasks or only for the specified task ID. Only applicable for taskUpdated, taskDeleted, and taskScored events.
Task The specific task ID to filter webhooks for. Only used if 'All Tasks' is false and the event is taskUpdated, taskDeleted, or taskScored.
Group The specific group ID to filter webhooks for. Only used when the event is groupChatMessageReceived.

Output

JSON

  • body - The JSON payload received from the Habitica webhook, containing event-specific data such as task details, group chat message content, quest information, or user activity data.

Dependencies

  • Requires an API key credential for Habitica API authentication to manage webhooks and receive event data.

Troubleshooting

  • If the webhook event is not supported, the node will log an error and not trigger the workflow. Ensure the selected event is valid.
  • For task-related events, if 'All Tasks' is set to false and the task ID does not match the incoming webhook's task ID, the webhook will be ignored. Verify the task ID is correct and matches the webhook payload.
  • Webhook creation and deletion rely on the Habitica API; network issues or invalid credentials can cause failures. Check API credentials and network connectivity if webhook management fails.

Discussion