Actions

Why it matters

flowchart LR
    Need[Repeatable need] --> Action[Reusable action]
    Action --> Review[Reviewable execution]

Actions explain how TrialStack packages operational behavior into repeatable units instead of requiring teams to rebuild the same workflow logic each time.

How it works

flowchart LR
    Purpose[Purpose] --> Action[Action]
    Inputs[Inputs] --> Action
    Action --> Runs[Runs]

An action is a reusable capability with a defined purpose, input shape, and execution boundary. It creates consistency across repeated work and gives the team a stable thing to trigger, review, and improve over time.

When to use it

flowchart TD
    Repeat[Task repeats] --> Action[Use an action]
    OneOff[One-off task] --> Manual[Stay manual]

This concept matters when a task should be executed the same way across multiple records, teams, or workflow moments.

What to watch for

flowchart LR
    Action[Action] --> Run[Run]
    Run --> Review[Review]
    Review --> Trust[Trusted result]

An action is not just a button label. It is the reusable behavior behind the button, and it still depends on the surrounding run and review workflow to make the result trustworthy.