HOME ASSISTANT n8n INTEGRATION: AUTOMATE HOME ASSISTANT WITH N8N

This action allows you to create dynamic templates directly in Home Assistant through your n8n workflow. Templates in Home Assistant are powerful tools for computing values, formatting text, or creating conditional logic based on entity states—and now you can generate them programmatically.

Key parameters: Credential to connect with (required dropdown for authentication), Resource (set to "Template"), Operation (set to "Create"), and Template (text input for your Jinja2 template code).

Use cases: Generate personalized notification messages that include current sensor values, create computed values combining multiple entity states for use in downstream workflow nodes, or format dates, times, or numbers according to specific requirements before sending to external services.

This action retrieves multiple entity states from your Home Assistant instance in a single request. It's invaluable when you need a snapshot of your entire smart home status or want to monitor several devices simultaneously within your workflow.

Key parameters: Credential to connect with (required), Resource (set to "State"), Operation (set to "Get Many"), Return All toggle switch, and Limit (numerical input, default: 50) to control the number of states returned.

Use cases: Create a daily report of all sensor readings sent via email, monitor all security-related entities (doors, windows, motion sensors) and trigger alerts if any are in unexpected states, or build a dashboard data feed that collects temperature, humidity, and energy consumption from multiple rooms.

This action fetches detailed information about a specific entity in your Home Assistant setup. Use it when you need precise data about a single device, sensor, or any other entity for conditional logic or data processing in your workflow.

Key parameters: Credential to connect with (required), Resource (Entity), Operation (set to "Get"), and Entity Name or ID (text input for the unique identifier like sensor.outdoor_temperature or light.living_room).

Use cases: Check if a specific door is locked before sending a "goodnight" message, retrieve the current state of a thermostat to include in automated reports, or fetch battery levels of specific sensors for low-battery notification workflows.

This action allows you to programmatically set or modify the state of any entity in Home Assistant. It's particularly powerful for creating virtual sensors, updating helper entities, or maintaining state information that originates from external systems.

Key parameters: Credential to connect with (required), Resource (set to "State"), Operation (set to "Create or Update"), Entity Name or ID (required text input), State (text field for the state value), and State Attributes (optional key-value pairs for additional properties).

Use cases: Update a virtual sensor with data fetched from an external API (weather, stock prices, etc.), set occupancy states based on calendar events from Google Calendar or Outlook, or create input helpers that reflect the status of external systems integrated via n8n.

This action retrieves a list of available services in your Home Assistant instance. Services are the actions you can call to control devices—like turning lights on, adjusting thermostats, or triggering scripts. This action helps you discover what's available programmatically.

Key parameters: Credential to connect with (required), Resource (set to "Service"), Operation (set to "Get Many"), Return All toggle, and Limit (numerical input, default: 50) to constrain the number of services returned.

Use cases: Build a dynamic documentation of all available services in your Home Assistant setup, create a service discovery workflow that identifies new integrations and their capabilities, or generate a reference list of services for use in conditional workflow logic.

This is arguably the most powerful action in the integration. It allows you to call any service in Home Assistant, enabling you to control devices, trigger automations, run scripts, and much more—all from within your n8n workflow.

Key parameters: Credential to connect with (required), Resource (set to "Service"), Operation (set to "Call"), Domain Name or ID (text input for service domain like light, switch, script), Service Name or ID (dropdown for specific service), and Service Attributes (optional key-value pairs for parameters like entity_id, brightness, color_temp).

Use cases: Turn on lights when a calendar event starts (meeting room preparation), trigger a Home Assistant script when receiving a webhook from an external service, adjust thermostat settings based on weather forecast data fetched from an API, or send TTS announcements through speakers when specific conditions are met in your workflow.

This action retrieves entries from Home Assistant's logbook, giving you a chronological record of events and state changes. It's essential for auditing, troubleshooting, and creating historical reports about your smart home activity.

Key parameters: Credential to connect with (required), Resource (set to "Log"), Operation (set to "Get Logbook Entries"), and Additional Fields (optional section for filters like date ranges or specific entities).

Use cases: Generate daily or weekly activity reports sent via email, monitor specific entities for unexpected state changes and log them to external systems, or create audit trails for security-sensitive devices like locks and alarms.

This action specifically retrieves error logs from your Home Assistant instance. It's crucial for monitoring system health, catching integration issues early, and maintaining a reliable smart home setup.

Key parameters: Credential to connect with (required), Resource (set to "Log"), and Operation (set to "Get Error Logs" to fetch only error-level log entries).

Use cases: Set up automated alerts when error logs exceed a certain threshold, send daily error summaries to a monitoring channel in Slack or Discord, or create tickets in your issue tracker when specific error patterns are detected.

This action retrieves multiple event types available in your Home Assistant instance. Events are the backbone of Home Assistant's automation system—they represent everything from button presses to state changes.

Key parameters: Credential to connect with (required), Resource (set to "Event"), Operation (set to "Get Many"), Return All toggle to fetch all events when enabled, and Limit (numerical input, default: 50) to restrict results when Return All is disabled.

Use cases: Document all available event types in your Home Assistant setup, build conditional workflows that react differently based on event availability, or create monitoring systems that track which event types are firing most frequently.

This action allows you to fire custom events in Home Assistant from your n8n workflow. Custom events can trigger Home Assistant automations, making this a powerful bridge between external systems and your smart home logic.

Key parameters: Credential to connect with (required), Resource (set to "Event"), Operation (set to "Create"), Event Type (text input for event type name like n8n_workflow_completed or external_doorbell_pressed), and Event Attributes (optional key-value pairs for context data like timestamps, source identifiers, or relevant information).

Use cases: Trigger Home Assistant automations when an email is received (via n8n Gmail trigger), fire events when external sensors or APIs detect specific conditions, or create a unified event system that bridges multiple platforms through Home Assistant.