Hule Docs

Appearance

Automations ​

Automations (called Actions in Hule) let you define rules that trigger when tasks change. Currently, one effect is available: spawn a task from a template. More effects will follow.

How it works ​

An Action has three parts:

  1. Trigger — an event that starts the rule (e.g. a task is moved to Done).
  2. Condition — optional filter (e.g. only in a specific list).
  3. Effect — what happens (e.g. spawn a new task from a template).

When the trigger fires and the condition matches, the effect runs automatically.

Creating an automation ​

  1. Go to Settings → Automations.
  2. Click + New automation.
  3. Name it (e.g. "Spawn QA task when bug is fixed").
  4. Configure the trigger and conditions.
  5. Choose the effect and its parameters.
  6. Save.

Trigger: task status changes ​

The automation watches for task update events. You can filter by:

  • List — only trigger for tasks in a specific list.
  • Status transition — from one status/group to another (e.g. when a task moves from "In Progress" to "Done").

Effect: spawn task from template ​

The available effect creates a new task from an existing task template. You configure:

  • Template — which task template to copy.
  • Target list — where to place the new task.
  • Status — optionally override the spawned task's status (otherwise uses the list's first open status).
  • Assignee — optionally pre-assign the spawned task.

The spawned task is a full copy of the template: title, description, priority, tags, checklist, subtask structure.

Use case examples ​

Spawn a QA verification task when a bug is fixed:

  • Trigger: task moved to "In Review" status
  • Effect: spawn task from "QA Checklist" template into the "QA" list

Replenish a backlog:

  • Trigger: task moved to "Done" in the "Sprint" list
  • Effect: spawn a new task from "Backlog Item" template into the "Backlog" list

Create a follow-up:

  • Trigger: task status changes to "Waiting for Reply"
  • Effect: spawn a "Follow up in 3 days" template task assigned to yourself

Managing automations ​

  • Enable/disable — toggle an automation on or off without deleting it.
  • Edit — change trigger, condition, or effect at any time.
  • Delete — removes the automation permanently. Running instances are not affected.

Automations run in the background — they don't slow down your task operations. The timezone of the automation creator is used for any date-related calculations.