Get Logbook
home_assistant.get_logbook
ActionBusiness appsconnection required
Calls the Home Assistant API with the connection's credentials.
Read logbook entries over a period, optionally for one entity.
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
3 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
start Start of the period, ISO-8601. Blank means 24 hours ago. | string | No | — | iso8601 format | 2026-09-08T00:00:00+00:00 |
end End of the period, ISO-8601. Blank means now. | string | No | — | iso8601 format | 2026-09-09T00:00:00+00:00 |
entity_id Keep only entries for this entity, as '<domain>.<object_id>'. | string | No | — | — | light.kitchen |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"end": "2026-09-09T00:00:00+00:00",
"entity_id": "light.kitchen",
"start": "2026-09-08T00:00:00+00:00"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The objects Home Assistant returned, in its own order. | array | — |
count How many objects are in `items`. | number | — |
{
"count": 0,
"items": []
}Related Home Assistant nodes
See Get Logbook 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.