How it works

smartordercapture has five concepts. Once you have them down, the rest of the product is navigation.

Workflow

A directed graph of one trigger and one or more actions, expressed as a versioned JSON document. You build it in the visual editor, which serializes it to the workflow DSL and syncs it to your phone.

Saving a change creates a new version; older versions are kept so you can roll back without rebuilding from scratch.

Trigger

The node that starts a workflow. Every workflow has exactly one. Time-based, SMS, NFC tap, homescreen shortcut, cloud push and others — see the triggers reference.

Action

The node that does something: tap a button, swipe, type, wait, open an app, make an HTTP call, log to a sheet, send an SMS. Two action types are special — branch (conditional) and loop (repetition). Actions form the body of the workflow and execute in the order you connect them.

Run

One execution of a workflow. Each run records its status (queued, running, success, failed, cancelled), timestamps, any error message, and a trace showing what happened step by step.

Device

An Android phone paired with your account. Workflows are device-specific, and each device carries a label, an installation source, and a heartbeat.

The execution loop, end to end

1. You save a workflow in the web builder.
2. The API versions it and marks the paired devices as needing sync.
3. The Android client pulls the new version and stores it locally.
4. The trigger fires on-device — no cloud round-trip.
5. Actions execute in order through the Accessibility service.
6. The run result is queued locally and uploaded when the network allows.

Local-first vs. cloud-first

The cloud is the source of truth for which workflows belong to you. Execution is fully local.