Documentation
Easymatic automates a phone by wiring nodes together. A trigger says when something happens, an action does something about it, and values and transforms feed them the data they need. A foreground service runs the result in the background.
Start here
Section titled “Start here”- Install and first run — what to install and what to allow
- Your first macro — four nodes, from empty canvas to armed
- The editor — the canvas, the palette, the bottom bar
How it works
Section titled “How it works”The core concepts section is the part worth reading once, properly:
| Nodes, ports and wires | The four node kinds, the two wire kinds, and why identifiers are chosen |
| Types and conversion | Why a drop is refused, what autocast does, how dates behave |
| Values and transforms | The pull side — read on demand, never pulsed |
| Control flow | Branching, loops, lists, waiting, stopping |
| Variables | The graph’s only writable state |
| How a macro runs | Arming, and what a problem actually blocks |
| The console | What a run did |
Setting things up
Section titled “Setting things up”Anything shared by more than one macro is configured once on the Setup tab — overview here.
Connections: AI · Smart home · Home Assistant · MQTT · Mail
Libraries and permissions-only integrations: Messengers · Calendar · Places · NFC tags · Files · Photos
The phone: Permissions · Running in the background · Widgets and shortcuts
Extending it
Section titled “Extending it”- Scripting — JavaScript inside one node
- The process API — run a macro from another app or a shell
- Writing a plugin — add your own nodes to the palette
Node reference
Section titled “Node reference”Every one of the 175 nodes ships with a page listing its ports, its configuration and anything it needs from the phone. Those pages are generated from the node declarations themselves, so they cannot describe a port a node no longer has.
Pick the group you want in the sidebar, or search — the search box covers every node name and description.