Many operator arguments are template fields: before the task runs, Airflow renders {{ ... }} in them with Jinja, using the run's context. BashOperator.bash_command, PythonOperator.op_kwargs and SQLExecuteQueryOperator.sql are templated; arguments that are not in an operator's template_fields are passed as written.
The values you will use most: {{ ds }} (2026-11-09), {{ ds_nodash }} (20261109), {{ logical_date }}, {{ data_interval_start }} and {{ data_interval_end }}, {{ params.region }}, {{ var.value.marigold_bucket }}, {{ conn.marigold_warehouse.host }}, and macros such as {{ macros.ds_add(ds, -1) }} for the day before. Airflow 3 dropped shortcuts like yesterday_ds; use the macro.
A name that does not exist fails the task when it renders, not when the file is parsed. Open Rendered templates on a task instance, or run airflow tasks render, to see exactly what a task received.
This workspace supports {{ }} expressions and filters, plus if, elif, else, for and set blocks. You can use loop metadata and comments. Template inheritance, Jinja macros and extensions aren't simulated.