Every team has them: the fifteen minutes after each supplier mail, spent copying order lines into a spreadsheet. The weekly folder clean-up. The summary someone writes every Friday. None of it is hard — it is just endless.
Classic automation tools answer with flow designers: boxes, arrows, connectors — and an afternoon of configuration for a rule you could say out loud in ten seconds. So the long tail of small automations never gets built.
In worX, the sentence is the automation.
From one file to every file
An automation in worX attaches to a folder or a stream. Described once, it runs on every file that lands in the folder, every mail that reaches the mailbox, every item that enters the stream — around the clock if you want, or on a schedule you set.
Powered by agents, kept honest by logs
Behind the sentence, an agent does the work — reading attachments, extracting values, writing files. Every run streams its steps into a log you can open: what was read, what was produced, what was skipped and why. If a run touches something sensitive, it pauses for your approval first.
That is the difference between automation you set up and automation you trust: you can always answer the question "what exactly did it do?"
Where teams start
About the author
Jens Meyer-Beeck is CEO of NEA X, the company behind worX, and writes about intelligent processes, AI agents that act with your permissions, and work that stays on your machine.