Triggers
Start workflows automatically based on events — new orders, incoming messages, scheduled times, form submissions, or manual clicks. Triggers are the starting point of every flow.
Flows
AI-first workflow automation.
Ottili ONE Flows gives you a visual way to build automated workflows — with triggers, conditions, actions, waits, approvals and complete logs. No code required, just connect the blocks that make sense for your business.
Building blocks
Six components that make any workflow possible.
Every workflow in Ottili ONE is built from these six core components. You can combine them in any order to create automation that fits your business logic.
Conditions
Add logic branches to your workflows. Check if an order amount exceeds a threshold, if a customer is VIP, if inventory is low, or any custom condition you define. Conditions let workflows make decisions.
Actions
Execute tasks in connected systems — send emails, create records in your CRM, update inventory, post to Slack, call APIs, or run AI steps. Actions are what your workflows actually do.
Waits
Pause workflows for a specific time or until an event occurs. Wait for customer response, delay before follow-up, hold for approval, or schedule recurring checks. Waits add timing control to automation.
Approvals
Pause any workflow for human review before critical actions. Approvals can be required for customer replies, purchase decisions, publishing content, or any step you designate. You stay in control.
Logs
Every workflow run is fully logged — trigger details, condition results, action outputs, wait times, approval decisions and error states. Logs give you complete visibility into what happened and why.
FlowSpec concept
Workflows as code, without writing code.
FlowSpec is the concept behind Ottili ONE Flows — workflows defined as structured specifications that are declarative, versioned, testable and observable.
Declarative
Describe what should happen, not how. FlowSpec defines the workflow structure — triggers, conditions, actions — and the system handles execution. You focus on business logic, not implementation details.
Versioned
Every workflow change is versioned. Roll back to previous versions, compare changes, and maintain a complete history of how your automations evolved. Version control applies to business logic, not just code.
Testable
Test workflows before they run in production. Validate triggers, check condition logic, simulate action outputs, and verify approval paths. Test flows reduce risk and increase confidence.
Observable
Full observability into workflow execution. See active runs, completed executions, pending approvals, failed steps and performance metrics. Observability helps you debug issues and optimize performance.
Real examples
Workflows that businesses actually use.
These examples show how the building blocks combine to solve real business problems.
E-commerce order fulfillment
Trigger: New order arrives. Condition: Check inventory level. Action: If stock available, create shipping label; if not, notify customer. Wait: Hold for 24 hours for response. Approval: Large orders require review. Log: Full audit trail.
Customer support triage
Trigger: New support ticket arrives. Condition: Classify by topic and urgency. Action: Route to appropriate team or auto-respond for common issues. Wait: Escalate if unresolved after 4 hours. Approval: Critical issues notify management. Log: Track resolution time.
Weekly business report
Trigger: Every Monday at 9 AM. Condition: Check if previous week data is available. Action: Collect KPIs from all systems, generate summary. Wait: Hold for review. Approval: Send to stakeholders. Log: Archive each report for history.
Natural-language creation
Describe the workflow. Flows builds it.
You do not start from a blank canvas. Describe a process in plain language — "when a high-value order arrives, draft a thank-you email and wait for my approval before sending" — and Flows turns it into a structured, validated FlowSpec. The AI proposes the triggers, conditions, actions, waits and approvals; you review and confirm before anything runs.
Describe in plain language
Write the workflow the way you would explain it to a colleague. No diagrams, no scripting, no hidden configuration to learn first.
Validated before it runs
Every natural-language draft is validated against the FlowSpec schema: required fields, reachable steps, and safe action boundaries. Invalid or ambiguous steps are flagged, not silently executed.
Refine with the AI
Ask the assistant to add a condition, change an approval gate or rewire a branch. Each change is reflected as a versioned FlowSpec you can read and accept.
Persistent execution
Runs that keep going, even when systems do not.
A Flow is not a script that dies when a server restarts. Execution state is persisted at every step, so a run resumes exactly where it stopped — a pending approval, a timed wait, a retried action — without losing progress or running a step twice.
Durable state
Each run's progress is stored as it moves through triggers, conditions, actions, waits, approvals and logs. A crash or restart picks the run back up from the last committed step.
Resume and retry safely
Waits and approvals persist across restarts. Failed actions are retried with backoff, and the engine guarantees a step is not repeated once it has been confirmed complete.
Auditable by design
Because state and every transition are persisted, each run leaves a complete, replayable record — what triggered it, what each step decided, and what it did — for review and compliance.
Approval-first design
Automation that never runs away from you.
Ottili ONE Flows is built on an approval-first philosophy. Any workflow step that affects customers, money, content or external systems can be gated for human review. You define which actions are automatic and which require approval. The default is conservative — critical steps wait for your sign-off. Automation handles the routine, you handle the decisions.
Implementation status
Core Flows capabilities available.
Ottili ONE Flows is in active development. The core building blocks — triggers, conditions, actions, waits, approvals and logs — are being implemented incrementally. FlowSpec provides the foundation for declarative, versioned workflows. Some features may be in beta or require configuration. We prioritize reliability, observability and real business utility over feature breadth. If you need specific workflow capabilities for your business, contact us to discuss implementation priorities.
Build your first flow.
Start with a simple trigger-action workflow and expand from there. Every flow is versioned, testable and fully observable.