One-Click Actions on Records

A record detail page shouldn't just display information. It should let you act on it.

"Mark as paid." "Send to customer." "Approve and advance." "Escalate to manager." These are the things your team needs to do with records — and making them available as one-click actions is the difference between a platform people actually use and one they use reluctantly.

Configurable Action Buttons

Swifty lets you define action buttons for any object type. Each button has:

• A label that describes what it does
• An action that executes when clicked — a status transition, a field update, a workflow trigger
• Optional confirmation — a dialog that asks "Are you sure?" before executing irreversible actions

Buttons appear on the detail page, in the header or alongside workflow indicators. Exactly where your team expects to find them.

Actions That Do Real Things

Clicking a button in Swifty isn't cosmetic. Actions can:

• Move a record through a workflow — advance status, log the transition, trigger automated consequences
• Update field values — set a field to a calculated value, fill in a timestamp, mark a boolean
• Trigger downstream processes — send a notification, update a related record, kick off a background job

The platform executes the action immediately and reflects the result. Your team clicks once and the work is done — not "submitted" or "queued," but done.

Confirmation for Irreversible Actions

Some actions shouldn't be one-click — or at least should pause for confirmation. Deleting a record. Cancelling an order. Sending an email. For these, Swifty's confirmation dialog asks the user to acknowledge before proceeding.

This prevents accidental actions without creating unnecessary friction for routine ones.

The Consistency of Configured Actions

When actions are defined in configuration rather than embedded as ad-hoc buttons in custom templates, they're consistent. Every instance of an object type has the same actions available. New team members see the same interface as veterans. The expected behavior is predictable.

That predictability is part of what makes a platform trustworthy.