Actions
Named operations you define once and run from a button, the Actions list, or an automation — all eight kinds.
An action is a named operation you define once and then run from several
places. It has a typed kind, a configuration, and every run is recorded so you
can see what happened.
Actions are the unit of “do something” in Snoze. A button — on a page, on a dashboard, or as a field on a record — does not contain logic. It points at an action.
Running one
- From a button — a button block or a Button field on a record
- From the Actions surface — in the rail, run it directly
- From ⌘K — actions available for what you have open appear in the palette
- From an automation — an Action node runs it as one step
Each run produces an action run with status and result, so a failure is inspectable rather than silent. Runs can carry runtime input — that’s how one “Archive this” action works on whichever record you clicked it from.
Running an action doesn’t require an editing seat. Operators run the actions shared with them without being able to edit or build anything, and they’re free on every plan — see Invite teammates and roles.
The eight kinds
| Kind | What it does | Configure |
|---|---|---|
| Create database record | Adds a record | Target database, and template values for its fields |
| Update database record | Changes a record | Target database, the fields to set. Omit the record and it comes from runtime input |
| Refresh data source | Re-pulls an external source | Which data source |
| Run actions | Runs several other actions in order | The list of actions |
| HTTP request | Calls any URL | Method (GET/POST/PUT/PATCH/DELETE), headers, query, body, optional connection, timeout |
| Connector operation | Runs a typed operation on a connected app | Connector, operation, connection. See Integrations |
| Provider operation | Runs an operation on a configured provider | Provider and operation |
| Code | Runs a code step | The code |
Buttons
Add a Button block to a page or dashboard, or a Button field to a database. Configure:
- the action it runs
- a label
- a variant (
primaryand friends)
A Button field puts one button on every record, and the record it sits on becomes the action’s input — which is how “Send the welcome email” or “Mark reviewed” becomes a single click per row.
Actions vs. automations
- An action is one operation, run when something asks it to.
- An automation is a graph — triggers, branches, loops, waits — and it can call actions as steps.
Start with an action. Reach for an automation when you need it to happen on its own, or to involve more than one step.