Action (workflow step)
A step in a workflow that performs an operation, such as sending a message, updating a record, or calling an API, as distinct from the trigger that starts the run.
In more detail
If the trigger is what starts a workflow, actions are what it does. Each action is a discrete operation: create or update a record, send a message, call an API, run a query, or transform data. A workflow is largely a sequence of actions, sometimes with branches and approvals between them.
Actions divide into reads and writes, and the distinction matters for safety. A read gathers information and is generally harmless to repeat; a write changes something in a real system and can be consequential or irreversible. Treating write actions with more care, through validation and approval, is a core part of designing a trustworthy workflow.
Where this shows up at Ceven
In Ceven, actions run across 1,000+ connected tools, and the consequential ones, the writes that change a real system, can be placed behind human-approval gates. Every action is recorded in the audit trail, so there is always a clear record of what the workflow did, to which system, and whether a person approved it.