Block 1 - Extract from File
- Type / Role
- n8n-nodes-base.extractFromFile - extractFromFile
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
UPDATES: 2025 12 03 fix JS code in node E.ON W1000 → n8n → Home Assistant (Spook) “Integration” This workflow processes emails from the E.ON portal containing 15 minute (import/export) data and dai...
n8n-nodes-base.extractfromfile, n8n-nodes-base.renamekeys, n8n-nodes-base.gmail, n8n-nodes-base.aggregate, n8n-nodes-base.splitout, n8n-nodes-base.merge, n8n-nodes-base.code, n8n-nodes-base.homeassistant
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by András Farkas.
Original n8n.io sourcecalculate hourly sum nodeThis workflow processes emails from the E.ON portal containing 15-minute +A -A (import/export) data and daily 1.8.0 2.8.0 meter readings.
It extracts the required columns from the attached XLSX file, groups the 15-minute values by hour, then:
sensor.grid_energy_import and sensor.grid_energy_export, and input_number.grid_import_meter and input_number.grid_export_meter.> You may need to modify the workflow if there are changes in how E.ON sends scheduled exports. If the exported data format changes, please report it on Github!
+ new scheduled export setting button. Specify POD identifier(s): choose one of the PODs you want to query. Specify meter variables: select the following:+A Active Power Consumption-A Active Power Feed-InDP_1-1:1.8.0*0 Active Power Consumption Daily ReadingDP_1-1:2.8.0*0 Active Power Feed-In Daily ReadingExport sending frequency: daily Days of historical data to include: recommended 7 days to backfill missed data. Email subject: by default, use [EON-W1000]. If processing multiple PODs with the workflow, give each a unique identifier.input_number entities in configuration.yaml or via Helpers:input_number:
grid_import_meter:
name: grid_import_meter
mode: box
initial: 0
min: 0
max: 9999999999
step: 0.001
unit_of_measurement: kWh
grid_export_meter:
name: grid_export_meter
mode: box
initial: 0
min: 0
max: 9999999999
step: 0.001
unit_of_measurement: kWh
> If you name the entities differently, make sure to reflect these changes in the workflow.
template_sensor entities in configuration.yaml or via Helpers:input_number:
grid_import_meter:
name: grid_import_meter
mode: box
initial: 0
min: 0
max: 9999999999
step: 0.001
unit_of_measurement: kWh
grid_export_meter:
name: grid_export_meter
mode: box
initial: 0
min: 0
max: 9999999999
step: 0.001
unit_of_measurement: kWh
>If you name the entities differently, make sure to reflect these changes in the workflow.
template_sensor entities in config.yaml or via Helpers:template:
- sensor:
- name: "grid_energy_import"
state: "{{ states('input_number.grid_import_meter') | float(0) }}"
unit_of_measurement: "kWh"
device_class: energy
state_class: total_increasing
- name: "grid_energy_export"
state: "{{ states('input_number.grid_export_meter') | float(0) }}"
unit_of_measurement: "kWh"
device_class: energy
state_class: total_increasing
> If you name the entities differently, make sure to reflect these changes in the workflow.
importing the workflow
Set up n8n Credentials The credentials must be configured in the Home Assistant and Gmail nodes. The setup process is described in the Requirements section.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 46 workflow blocks. Download the JSON for the full node graph.
| Workflow | Import E.ON W1000 energy meter data to Home Assistant with Spook integration |
|---|---|
| Complexity | advanced |
| Nodes | 46 |
| Categories | File Management |
| Author | András Farkas |
| Published | 27 Sept 2025 |
Use the JSON export at /data/workflows/9010/9010.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
UPDATES: 2025 12 03 fix JS code in node E.ON W1000 → n8n → Home Assistant (Spook) “Integration” This workflow processes emails from the E.ON portal containing 15 minute (import/export) data and dai...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your File Management use case.