Events, Automations and Workflows

Workflows connect typed steps and conditions into a bounded process. Validation and execution history help you inspect how data and actions move through it.

A successful step does not prove that every later step succeeded. Check partial results and external effects before rerunning the process.

Automations initiate work from a configured schedule or event. They begin as disabled drafts so you can inspect the conditions before activation.

Run now is a real execution, not a preview. It uses the same permissions and policy checks. Inspect execution history before repeating a failed external action.

Work is the execution inbox for tasks that are waiting, running, need attention, completed or failed. It helps distinguish an active run from a finished result.

A completed run still needs output review. An approval should identify the action, target and effect; reject an unexpected or overly broad request.

Authorized integrations use versioned Yasnora APIs and SDKs. Pass identity and policy context and request logical capabilities rather than hard-coding a physical provider.

For streaming, distinguish partial data from the final result and handle finish, cancel, errors and usage. Do not treat a dropped stream as successful completion or retry a write blindly.