Resources and references
AilaFlow uses a one-character prefix to make every resource reference easy to recognize.
| Resource | Prefix | Example | Scope |
|---|---|---|---|
| Process | / |
/request_approval |
Administrator-defined workflow |
| Table | # |
#customers |
Persistent workspace data |
| Sandbox | + |
+default |
Isolated script environment |
| User | @ |
@robert |
Workspace user or administrator |
| Variable | $ |
$request |
One process execution |
Processes: /
A process coordinates steps, users, AI, and data. Processes can call other permitted processes.
Examples: /employee_onboarding, /request_approval.
Tables: #
Tables store persistent JSON-compatible data under string primary keys. Their data remains available across process executions.
Example: #customers.
Sandboxes: +
Sandboxes provide isolated Linux environments for scripts and integrations. Docker is the default engine.
Example: +default.
Each sandbox can define dependencies and secrets. Only /data persists when its container is replaced.
Users: @
Reference one user by name:
@robert
Select users by properties:
@{.team = "finance" and .access_level = "c3"}
Use and between conditions inside @{...}. Use or between alternative users or groups:
@robert or @{.team = "finance" and .access_level = "c3"}
Variables: $
Variables carry JSON data through one process execution. Their values must match their JSON Schemas.
Examples: $request, $status, $result.
Variable state is deleted when execution finishes. Use a table when data must persist.