smartordercapture documentation
Build automation visually on the web, run it locally on your Android phone. The docs here explain how the pieces fit together, what every node does, and how to debug what goes wrong.
New here? Start with the 5-minute quickstart. If you have the app installed and an account paired, jump straight to the triggers and actions references — they list every node, what it does, and the edge cases worth knowing.
Where to start
Install the app, pair your phone, and run your first workflow in five minutes.
Workflows, triggers, actions, runs, devices — the mental model in one page.
All 15 triggers, all 20 actions, the workflow DSL, and the on-device denylist.
Why a trigger didn't fire, why a tap missed, why an upgrade failed — fixes for the common ones.
Refunds, accounts, the Play Store, the companion device program, what we won’t automate.
The shape of the product
smartordercapture has three surfaces:
- The web app. Where you build workflows — drag triggers and actions onto a canvas, connect them, save, push to a device.
- The Android client. The engine that executes your workflows locally on your phone. Speaks to Android's Accessibility API to dispatch taps and read on-screen state.
- The cloud. Sync between web and device, billing, optional template marketplace. Workflow content executes on-device; the cloud never sees the apps you automate.
Updates
The docs are versioned alongside the DSL. The current DSL version is 1. When we ship a new node kind, you'll see a callout on the relevant reference page and a note in the changelog.