Components

The Awee engine runs automation workflows. A workflow is a portable, declarative definition, an ordered list of steps where each step runs one component and every output flows to the steps that come after it through sintax template expressions. The same definition reads clearly to people and to language models, runs the same on any operating system, and is launched from a command-line app, a REST API, or the web app.

It is the engine behind Awee, the automation platform. The core runtime, control flow, and the file, HTTP, inference, and control components are built in. The App components connect a workflow straight to the Awee data platform.

Awee pairs a static, inspectable execution plan with model-powered steps, per-run cost accounting, and multi-currency reporting, so an automation stays auditable even when a model is in the loop.

How it works

1. Define a workflow. List the actions, pick a component for each, and wire outputs with sintax {{ step.field }} expressions.
2. Plan. The engine compiles the definition into an ExecutionPlan with no I/O and no side effects.
3. Execute. Steps run in order, and conditions, loops, retries, and cache hits all resolve at runtime.

A first workflow

id: search-and-summarise
name: Search and Summarise

actions:
  - name: page
    component: http
    vars:
      url: "https://example.com/{{ topic | slug }}"

  - name: summary
    component: inference
    vars:
      provider: anthropic
      model: claude-opus-4-20250514
      prompt: "Summarise in three bullet points: {{ page.body }}"
    cache:
      for: 1h

  - name: write
    component: file:write
    vars:
      path: "./out/{{ topic | slug }}.md"
      content: "{{ summary.content }}"

Every field accepts {{ }} expressions. A prior step's output is referenced by its name, so {{ page.body }} reads the page step's body. Modifier chains such as {{ topic | slug | lower }} transform values inline, and {{ value | default:'x' }} supplies a fallback.

Control flow

Any step can carry an if condition, a retry policy, or a cache duration, and looping is the each component wrapping its body under actions. Conditions choose between a step and its else branch, loops run their child steps once per item, and a cache hit skips the step and injects the stored value. The control flow guide covers all of it.

Components

Each component links to its own page with its full options and outputs.

App

Manage schemas, tables, fields, and records in the Awee app platform.

CSV

Parse, transform, and merge CSV files.

Dir

Read and write directories on the local filesystem.

Each

Iterate over a list and run sub-steps for every item.

Error

Raise an explicit error to stop the workflow.

Event

Emit events during workflow execution.

Exec

Execute shell commands.

File

Read, write, copy, find, and validate files on the local filesystem.

Group

Group related steps under a single named step.

HTTP

Make HTTP requests and handle responses.

Inference

Interact with AI language models.

Map

Transform a list by running sub-steps per item and collecting results.

Print

Print values to stdout for debugging.

Sleep

Pause workflow execution for a duration.

Template

Render a text template.

Var

Set or pass through a variable value.

XML

Parse and transform XML documents.