Start In 5 Minutes
This is the shortest path from zero context to a working flow execution. It is designed for someone who wants to understand the system and ship fast.
5 Minute Start
Step 1
Open https://flow.iai.one.
Step 2
Create a new flow from the builder start screen.
Step 3
Add three basic nodes: Input, Logic, and Output.
Step 4
Run the flow and inspect the execution output or mail side-effects.
Current login state
The current access path is a temporary developer mailbox login. The full identity layer is planned as a dedicated future system.
Accounts
Current
- Session-based access
- Temporary developer mailbox login
- Builder and runtime testing for MVP use
Future
- Identity layer
- Role-aware access in app.iai.one
- Token-based API access
Core Concepts
| Term | Meaning | Why it matters |
|---|---|---|
Flow |
A workflow composed of nodes and edges. | It is the unit a user builds, saves, and executes. |
Node |
An action in the workflow. | Each node maps to runtime behavior. |
Execution |
A single run of a flow. | Executions create logs, outputs, and retry state. |
Output |
The result produced by the final step or side-effect. | Outputs can feed mail, alerts, or downstream systems. |
First Example
Even the smallest successful flow follows the same structural rules used by larger workflow graphs.
{
"nodes": [
{ "id": "input-1", "type": "input" },
{ "id": "logic-1", "type": "transform" },
{ "id": "output-1", "type": "output" }
],
"edges": [
{ "from": "input-1", "to": "logic-1" },
{ "from": "logic-1", "to": "output-1" }
]
}
What to verify
Your first success criteria should be simple: validate JSON, run once, store output, and confirm the execution log is visible.