MultiOn

MultiOn drives real websites with no API, which is its strength and its fragility — when the target site ships a redesign, brittle instructions break.

Instruct by intent, not by coordinates

Don't tell it to click a specific button or path. Describe the goal in semantic terms:

Find the CSV export control in the billing table and download the current month.

MultiOn reads the DOM semantically, so an instruction phrased around what the element does survives a visual redesign that would break a selector-based script.

Build in resilience

• Add a verification step: "confirm the downloaded file has more than one row" catches a silent failure before it propagates.
• Expect latency on heavy pages — set generous timeouts rather than tight ones, and split long workflows into checkpoints you can resume from.
• For a site you automate daily, re-run the task manually once a week; you want to discover a breakage, not have a scheduled job discover it.

The rule

Semantic intent is the durable interface. If your instruction would still make sense read aloud to a person looking at the page, it will probably outlast the next redesign.