All topics

Flow actions and credentials

Actions send messages or operate integrations/resources. They require suitable configuration.

Available options depend on your version, permissions and hardware. For missing actions, see Security and Diagnostics.

Step by step

  1. Choose the action and destination, message or command.
  2. Store required secrets in Credentials and reference them from nodes.
  3. Wire available success/error/timeout outputs, simulate and check logs.

Options explained

MQTT/webhook
need reachable broker/endpoint, correct topic/payload and response.
Email/push/SMS/Slack/Discord
need provider, destination and credentials; many require Internet.
Home Assistant/SmartThings/Kasa
require linked integration and compatible equipment.
Fan
needs supported host hardware, not inverter cooling.
Shared resources
inspect conflicts/manual overrides before targeting the same resource from two flows.

Troubleshooting

Check integration and secrets privately for failed deliveries. Simulation does not prove a provider accepts a real action.

Common problems
Flow actions and credentials | HelioPulse | HelioPulse