User Actions & the action button
A User Action is a saved, named webhook or MQTT action you can trigger on demand — not tied to a threshold.
- Under Rules → Actions, create an action of type webhook or mqtt with its config.
- On a dashboard, add an action-button widget and point it at that action.
- Clicking the button fires the action immediately (
POST /actions/:id/trigger).
Use these for manual operations — acknowledge, reset a counter, open a valve, ping an external workflow. They share the same config shape as rule webhook / rule MQTT actions, including custom headers and the same reserved header names.
HTTP method. A webhook User Action can use POST (the default), PUT, PATCH or GET. All of them are signed with X-Synacl-Signature when you set a secret. GET sends no body, so its signature is computed over an empty string — it proves the request holds your secret, not that a payload is intact. See verifying webhook signatures.
Plan limits apply. The action types available to you come from your plan, and are enforced when you create, edit and trigger an action. If a type isn't on your plan you'll see a clear message rather than a silent failure.
Who can use one. Firing an action — from the button, or through a rule or a macro step that calls it — needs Trigger actions, so a rule or macro that calls a saved action can only be saved or switched on by someone who holds it. A webhook action's secret and headers show only to people who can edit actions; a member who can only view sees that they're set, not what they are. The same goes for the secret and headers on a rule's webhook action and the broker login on an MQTT action.