Automation Workflows
Automations are durable workflow records with setup state, execution state, and run history. They are how Nexus turns conversational requests into repeatable, governed work.
Audience: Operators building repeatable processes and teams managing AI-assisted execution.
Current Version
1.0
Documentation aligned to the current operational build of Chat, Automations, Contacts, and workflow runtime.
Scope
1
A standalone documentation page with a stable URL you can share directly.
Quick Start
How the system is meant to be used
Step 1
Read the platform overview first so you understand how Chat, apps, and runtime work together.
Step 2
Start your first conversation in Chat with a real business outcome, not just a general prompt.
Step 3
Let Nexus turn that intent into a durable record, workflow, or next-step artifact.
Step 4
Connect the systems required for context, communication, and execution as setup requires.
Step 5
Move into the relevant app surface to review, manage, approve, and operate the resulting work.
Operating Principle
Chat compiles. Apps operate. Runtime executes.
Nexus is not a chatbot that happens to call tools. It is a structured operating system where conversational intent is translated into durable records, validated state, and auditable actions.
This docs site is the product-level reference for how that model works today and how the current 1.0 surfaces fit together.
Audience
Operators building repeatable processes and teams managing AI-assisted execution.
Automation Workflows
Automations are durable workflow records with setup state, execution state, and run history. They are how Nexus turns conversational requests into repeatable, governed work.
Philosophy
Automation in Nexus should be understandable, resumable, and operable by humans. AI may help author the workflow, but structured workflow state is what makes automation trustworthy.
Technically Managed By
- Workflow definitions are stored as durable records with setup state, runtime state, and execution history.
- Integrations, validation, approvals, and execution policies are attached to the automation rather than hidden in chat.
- The server compiles and versions workflow specifications before execution occurs.
How Users Should Use and Manage It
- 1Review new automation requests in the Automations surface before activating them.
- 2Resolve setup blockers such as integrations, required inputs, and validation rules.
- 3Use run history and workflow status to manage the automation after creation.
How It Fits in Nexus
- Automations are the execution layer of Nexus.
- They turn conversational requests and operating needs into repeatable, governed system behavior.
- They depend on Chat for intake, Integrations for connectivity, and Runtime and Safety for execution control.
What Matters
- Chat-authored workflows become managed records in the Automations app.
- Workflow specs are compiled and versioned before execution.
- Activation, pause, resume, and run-now are meant to be explicit and auditable.
Reference Notes
Next Step
Use the docs as the product contract.
As new apps and runtime behaviors ship, extend this documentation hub first so users and internal teams have one clear reference for how Nexus is supposed to work.