Automation integrations

DinkyTask automation connections are available through family webhooks, the Automation API, and the Home Assistant integration. DinkyTask remains the source of truth, and automations react to DinkyTask state and events.

Connection options

  • Family webhook: each family can configure one target URL, and DinkyTask sends supported plan and submission events to that endpoint.
  • Automation API: token-based API available with an active trial or premium subscription. It returns the current family/child/plan status and an event feed.
  • Home Assistant integration: uses the Automation API, creates Home Assistant entities, and fires DinkyTask events on the HA event bus.

Home Assistant entities

The Home Assistant integration creates stable family and per-child entities.

  • sensor.dinkytask_family — family connection and snapshot status.
  • sensor.dinkytask_pending_reviews — number of submissions waiting for parent review.
  • binary_sensor.dinkytask_review_needed — turns on when at least one submission needs review.
  • sensor.dinkytask_<child>_today — per-child daily summary.

Per-child daily attributes

The child today sensor contains current-day plan status and the automation_key values used for automation routing.

  • plan_count, plans_active, plans_completed, plans_pending_review
  • progress, required_completed, required_total, pending_review_count
  • current_automation_key, active_automation_key, completed_automation_key, pending_review_automation_key
  • automation_keys, active_automation_keys, completed_automation_keys, pending_review_automation_keys
  • current_plan and plans with compact plan metadata.

Home Assistant events

The integration turns Automation API events into Home Assistant events. DinkyTask dots are replaced with underscores, and the event name receives a dinkytask_ prefix.

  • plan.completed → dinkytask_plan_completed
  • submission.pending_review → dinkytask_submission_pending_review
  • The payload can include fields such as child_name, plan_title, and automation_key.

The exact webhook behavior and payload structure are documented on the Webhooks page.