Render Template

home_assistant.render_template
ActionBusiness appsconnection required

Calls the Home Assistant API with the connection's credentials.

Render a Home Assistant Jinja2 template against the live state machine.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
Home Assistant
Secret shape
the long-lived access token, or {"access_token": "…"}
Config it needs
base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
template
The Home Assistant template to render, for example {{ states('sensor.outside_temperature') }}.
stringYes———
variables
Values the template can read, as a JSON object. Use this to pass data from earlier steps.
objectNo——{"threshold":20}

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "variables": {
    "threshold": 20
  }
}

Output

One shape.

result

FieldTypeExample
template
The template that was sent.
string—
rendered
The render, as text — Home Assistant answers in plain text, never JSON.
string—
truncated
True when the render reached the 2000-character response cap.
boolean—
{
  "rendered": "",
  "template": "",
  "truncated": false
}

Notes

  • Home Assistant templates use the same {{ … }} braces Mantle renders in node config, so this field is left unrendered — write plain Home Assistant syntax and pass step data through `variables`.
  • Home Assistant requires an admin token for this call; a non-admin long-lived token fails with 401 even though the connection tests green.

See Render Template run in a workflow.

In a technical demo we add the Home Assistant connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.