How to reference input variables within jinja tempate?

Configuration
1

I have an automation that I’ve been using that I want to turn into a blueprint. It uses a response_variable in a for_each loop to process todo list items. It works fine with a hardcoded todo list entity, but I can’t figure out how to have it use an input variable for the the entity id, specifically in the jinja template of the for_each.

Here’s an example of what I’m trying. Appreciate any help with the correct syntax:

automation:
  - alias: Process To-Do List Items
    trigger:
      # Your trigger here (e.g., a button press, a specific time)
    action:
      - service: todo.get_items
        target:
          entity_id: !input todo_entity
        data:
          status: needs_action # Get only items needing action
        response_variable: daily_tasks # Name your response variable

      - repeat:
          for_each: "{{ daily_tasks[todo_entity]['items'] }}" # Reference the specific 'items' list
          sequence:
            - service: notify.mobile_app
              data:
                message: "Task summary: {{ repeat.item.summary }}" # Access properties of each item
            # Add more actions to perform for each item here
variables:
  todo_entity: !input todo_entity
2

I’ve never actually needed to do this but I guess something like:

  - service: todo.get_items
    target:
      entity_id: {{ states('input_text.myvariablehere') }}

Your mileage may vary, but if the name of the todo list is in the input_text, I don’t see why it wouldn’t work.

3

Single line templates should also be surrounded by double (or single when it makes sense) quotes…

    - service: todo.get_items
      target:
        entity_id: "{{ states('input_text.myvariablehere') }}"
4

The way you are setting and using the input and variable looks fine, but automations don’t allow the use of !input, so I’m not sure what you are expecting from what you have posted… Without an actual blueprint config, it’s hard to say for sure what the source of any issue is.

FWIW, I would suggest using merge_response(), that will allow you to use more than one todo entity at a time if desired, and has the side effect of eliminating the need for using the input.

Blueprint Sketch 
blueprint:
  domain: automation
  name: Example 
  description: Example 
  input:
    my_trigger_input:
      name: Triggers
      selector:
        trigger:
    todo_entity:
      name: ToDo Lists
      selector:
        entity:
          multiple: true
          filter:
            - integration: todo
    further_actions:
      name: Actions
      selector:
        action:
triggers:
  - triggers: !input my_trigger_input
actions:
  - action: todo.get_items
    target:
      entity_id: !input todo_entity
    data:
      status: needs_action 
    response_variable: daily_tasks
  - variables:
      tasks: "{{ merge_response(daily_tasks) }}"
  - repeat:
      for_each: "{{ tasks }}"
      sequence:
        - service: notify.mobile_app #MAKE SURE TO PUT A REAL NOTIFY ACTION HERE
          data:
            message: "Task summary: {{ repeat.item.summary }}"
        - sequence: !input further_actions

If you can clarify what your goals are for the blueprint we can probably provide a bit more guidance

5

Yeah, sorry for the confusion. I am working on a blueprint but hastily copied and pasted an automation that had similar code to illustrate the issue. I am able to use input variables to assign todo list entities everywhere except the jinja code below:

 for_each: "{{ mylist['todo.recurring']['items'] }}"

However, your suggestion to use the merge_response() did easily solve the problem - thank you.

For future reference I would still like to know how to replace a hard coded value - ‘todo.recurring’ with a variable if anyone knows. Thanks again.

6

Are you asking about doing it in an automation or a blueprint?

The way you had it should work, but you need to use a real value in the variable definition, not an input, because automations don’t use inputs:

automation:
  - alias: Process To-Do List Items
    triggers:
      # Your trigger here (e.g., a button press, a specific time)
    variables:
      todo_entity: "todo.recurring"
    actions:
      - action: todo.get_items
        target:
          entity_id: "{{ todo_entity }}"
        data:
          status: needs_action
        response_variable: daily_tasks
      - repeat:
          for_each: "{{ daily_tasks[todo_entity]['items'] }}"
          sequence:
            - action: notify.mobile_app
              data:
                message: "Task summary: {{ repeat.item.summary }}"
7

When I generate the automation from the blueprint, the input values populate into all of the places they should, except for that jinja string.

I’m fighting a hideous sinus infection right now which is making it hard for me to keep my eyes open for more than a few minutes, but when I’m feeling better I’ll post so more code to demonstrate.

8

Post the actual blueprint config.

9 
blueprint:
  name: Recurring Todo Blueprint Backup
  description: Sets the next due date of recurring todo list items based on date completed
  domain: automation
  input:
    todo_entity:
      name: Todo List
      description: Todo list that contains the recurring items
      selector:
        entity:
          filter:
            - domain: todo
    calendar_entity:
      name: calendar entity
      description: The calendar you want to update when items are completed
      selector:
        entity:
          filter:
            domain: calendar

triggers:
  - trigger: state
    entity_id:
      - !input todo_entity
  - trigger: time_pattern
    minutes: /15
conditions: []
actions:
  - action: todo.get_items
    data:
      status:
        - completed
    target:
      entity_id: !input todo_entity
    response_variable: mylist
  
  - repeat:
      sequence:
        - action: todo.update_item
          data:
            item: "{{repeat.item.summary}}"
            status: needs_action
            due_date: >-
              {{ (now() + timedelta(days=repeat.item.summary.split('[',
              1)[1].split(']')[0]|int)).strftime('%Y-%m-%d')}}
          target:
            entity_id: !input todo_entity
        - action: calendar.create_event
          target:
            entity_id: !input calendar_entity
          data:
            summary: ✔ {{repeat.item.summary.split('[', 1)[0]}}
            description: "{{repeat.item.description}}"
            start_date: "{{ now().strftime('%Y-%m-%d')}}"
            end_date: "{{ (now() + timedelta(days=1)).strftime('%Y-%m-%d')}}"
      for_each: "{{ mylist['todo.recur_test']['items'] }}"
mode: single

In the second to last line I have the todo entity hardcoded because I can’t figure out how to populate it from an input. Thanks didgeridrew.

10

Setting it up as follows is working for me…

blueprint:
  name: Recurring Todo Blueprint Backup
  description: Sets the next due date of recurring todo list items based on date completed
  domain: automation
  input:
    todo_entity:
      name: Todo List
      description: Todo list that contains the recurring items
      selector:
        entity:
          filter:
            - domain: todo
    calendar_entity:
      name: calendar entity
      description: The calendar you want to update when items are completed
      selector:
        entity:
          filter:
            domain: calendar
variables:
  todo_entity: !input todo_entity
triggers:
  - trigger: state
    entity_id:
      - !input todo_entity
  - trigger: time_pattern
    minutes: /15
conditions: []
actions:
  - action: todo.get_items
    data:
      status:
        - completed
    target:
      entity_id: !input todo_entity
    response_variable: mylist
  - variables:
      todo_items: "{{ mylist[todo_entity]['items'] }}"
  - repeat:
      for_each: "{{todo_items}}"
      sequence:
....
11

Thanks, that works. But, I realized that my original script was also working with a local variable declared and this…

for_each: "{{ mylist[todo_entity]['items'] }}"

The problem was my troubleshooting. I was generating the automation from the blueprint, taking control, and verifying that the input variable values were populating into the correct places. For some stupid reason I was expecting those values to appear in place of the local variable in the for_each. I blame it on the sinus infection and not utter stupidity :slight_smile: Thanks again for all of your help. The merge_response() function will come in handy for a few automations I need.