Skip to main content
Automations turn repeatable instructions into operational work. They use workspace context, connected sources, pages, and skills to prepare analysis or next steps on a schedule or in response to an event.

​
An automation can

  • Read from connected systems and source files
  • Combine source data with workspace context
  • Draft analysis, updates, or proposed actions
  • Record the run and its supporting evidence

​
Reviewable actions

When an automation would affect another system or produce a client-facing output, it should produce a proposal or reviewable result first. A reviewer can inspect the rationale, evidence, and intended action before approving it.

​
Run history

Each run should make its progress and outcome understandable. Run history provides the context needed to distinguish a successful action, a failed attempt, a pending review, and a result that needs follow-up.