Handle Intent
home_assistant.handle_intent
ActionBusiness appsconnection required
Calls the Home Assistant API with the connection's credentials.
Send a named intent with its slots to Home Assistant's intent handler.
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.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
name The intent to handle, for example 'HassTurnOn'. | string | Yes | — | — | HassTurnOn |
data The intent's slots as a JSON object, for example {"name": "kitchen"}. | object | No | — | — | {"name":"kitchen"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"data": {
"name": "kitchen"
},
"name": "HassTurnOn"
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}Notes
- Needs 'intent:' in the instance's configuration.yaml; without it Home Assistant answers 405 and the step fails with that status.
Related Home Assistant nodes
See Handle Intent 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.