Home Assistant n8n integrationAutomate Home Assistant with n8n.

Grabs the current image from a camera entity and hands it to the workflow as a file, not as text. Downstream nodes can attach it to a message or drop it in storage.

• Camera Entity Name or ID: the camera to photograph, picked from the list n8n loads from your instance, or set with an expression such as {{ $json.entity_id }} when an earlier node decides which one.
• Put Output File in Field: the name of the output binary field the image lands in, which is what you reference when sending it on.

Returns the configuration of the Home Assistant instance as the API reports it. Nothing to fill in: the operation takes no parameter, it just answers.

Asks Home Assistant to validate its own configuration and returns the verdict. No parameter either, which makes it cheap to run often.

Fires a custom event on the Home Assistant event bus, so automations inside Home Assistant can listen for something that happened in n8n.

• Event Type: the entity ID for which the event will be created, typed as text or built from an expression.
• Event Attributes: optional payload added one pair at a time with Add Attribute, for the data the listening automation needs.

Lists the events the instance knows about, in one call, with no filter to configure.

• Return All: on, n8n walks the pages of the API until every event is back; off, it stops at Limit.
• Limit: the maximum number of events returned when Return All stays off.

Pulls the error log of the instance as Home Assistant records it. There is no field to fill, the operation returns what is there.

Returns logbook entries, the human readable history of what changed and when. Left alone it answers for the recent period; the optional fields narrow it down.

• Start Time: the beginning of the period, as a date and time value.
• End Time: the end of that period.
• Entity ID: restricts the logbook to a single entity instead of the whole house.

This is how a workflow acts on the house. The node picks a service domain, then a service inside it, and Home Assistant does the rest: turning a light on, setting a temperature, running a script.

• Domain Name or ID: the service family, chosen from the list or given by an expression such as {{ $json.domain }}.
• Service Name or ID: the service inside that domain, same list or same expression logic.
• Service Attributes: the values the service expects, added one pair at a time with Add Attribute.

Returns the services available on the instance, grouped by the domain they belong to.

• Return All: on, every service comes back across as many API pages as needed; off, the result stops at Limit.
• Limit: the maximum number of services returned.

Writes a value into the state machine. If the entity already has a state, it is replaced; if not, the entity appears with the value you sent.

• Entity Name or ID: the entity the state belongs to, from the list or from an expression.
• State: the value itself, as text.
• State Attributes: extra pairs attached to the state, added with Add Attribute.

Reads the current state of one entity, with its attributes. Nothing is modified, which makes it safe to place in front of any decision in a workflow.

• Entity Name or ID: the entity to read, picked from the list n8n loads from your instance, or supplied by an expression when an earlier node chose it.

Returns the state of every entity at once, which is the fastest way to see the whole house in a single execution.

• Return All: on, n8n pages through the API until the full state machine is back; off, the run stops at Limit.
• Limit: the maximum number of states returned.

Renders a Home Assistant template and returns the result, so the logic stays in Home Assistant syntax instead of being rebuilt in n8n nodes.

• Template: the template to render, written as text; the Home Assistant template documentation covers the syntax.