User Actions & the action button

Updated

A User Action is a saved, named webhook or MQTT action you can trigger on demand — not tied to a threshold.

  1. Under Rules → Actions, create an action of type webhook or mqtt with its config.
  2. On a dashboard, add an action-button widget and point it at that action.
  3. 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.

More in Rules & alerts
Create an alerting rule
Trigger in-app, email, webhook, or MQTT actions when a threshold is crossed.
Operators & thresholds
The comparison operators a rule can use and how scope works.
Severity & cooldown
Label urgency and prevent alert storms with a cooldown.
Rule action: email
Send an email to one or more recipients when a rule fires.
Rule action: webhook (with signature)
POST a signed JSON payload to your endpoint when a rule fires.
Rule action: MQTT publish
Publish to any MQTT broker when a rule fires.