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.

What works today

The family webhook and the Automation API are available with an active trial or a premium plan. A Home Assistant blueprint is ready too: one import gives you a working automation, with no custom component to install.

The Home Assistant add-on (HACS integration) is still in development. The entities and HA events described below belong to it and are not available yet. Until then, the blueprint is the recommended route.

Home Assistant blueprint

The blueprint uses Home Assistant's built-in webhook trigger, so it works on any Home Assistant install. You decide what happens on each DinkyTask event — turning a hallway lamp green when the day's plan is done, for instance.

  1. Import the blueprint into Home Assistant — or paste this link yourself: https://dinkytask.com/home-assistant/dinkytask-family-webhook-blueprint.yaml
  2. Choose a long, random webhook ID. Home Assistant turns it into a public URL: https://YOUR-HA-HOST/api/webhook/THAT-ID
  3. Set the actions for each event (plan started, completed, failed, expired; submission pending review, approved, rejected).
  4. Paste the same webhook URL into DinkyTask under Profile → Advanced settings.

The blueprint runs on the family webhook, so it follows the events and payloads described there.

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 blueprint: a working automation from a single import, built on Home Assistant's own webhook trigger. Available now.
  • Home Assistant add-on: will use the Automation API, create Home Assistant entities, and fire DinkyTask events on the HA event bus. In development.

Home Assistant entities

The entities below belong to the Home Assistant add-on, which is still in development and not available yet.

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.