Update a reward

Use this action to update a specific custom reward for the selected Habitica character.

Using this action from the user interface

If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.

To update a reward from an automation or a script:

  1. Go to Settings > Automations & scenes.
  2. Open an existing automation or script, or select Create automation > Create new automation.
  3. If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
  4. In the Then do section, select Add action.
  5. From the search box, search for and select Habitica: Update a reward.
  6. Select the Config entry of the character and the Task name of the reward to update. Then set the values you want to change.
  7. Select Save.

This action does not support targets. In the UI, you are not prompted to choose an area, device, entity, or label.

Options in the UI

Select character (Required)

The Habitica character that owns the reward.

Task name (Required)

The reward to update by name, task ID, or alias.

Rename (Optional)

The new title for the reward.

Notes (Optional)

The new notes for the reward.

Cost (Optional)

The cost of the reward in gold.

Add tags (Optional)

Add tags to the reward. If a tag does not exist yet, it is created.

Remove tags (Optional)

Remove tags from the reward.

Task alias (Optional)

An alias to use instead of the name or task ID. Only dashes, underscores, and alphanumeric characters are supported. The alias must be unique among all your tasks.

Using this action in YAML

If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required.

In YAML, refer to this action as habitica.update_reward:

ActionActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called *sequence*. [Learn more]
action: habitica.update_reward
data:
  config_entry: 6b4be47a1fa7c3764f14cf756dc9899d
  task: "Watch a movie"
  cost: 75

Options in YAML

config_entry string Required

The Habitica character that owns the reward.

task string Required

The reward to update by name, task ID, or alias.

rename string

The new title for the reward.

notes string

The new notes for the reward.

cost float

The cost of the reward in gold.

tag string | list

Add tags to the reward. If a tag does not exist yet, it is created.

remove_tag string | list

Remove tags from the reward.

alias string

An alias to use instead of the name or task ID. Only dashes, underscores, and alphanumeric characters are supported. The alias must be unique among all your tasks.

Try it yourself

Ready to test this? Open Developer tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] without writing a line of YAML.

Still stuck?

The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.

Tip

AI assistants like ChatGPT or Claude can also explain actions or suggest the right one when you describe what you want in plain language.