Interface automation for software with no API
Operates older software exactly the way a person would
You automate even the systems never designed to allow it
Interface automation is the second-best option. It is worth using only when the best one does not exist.
What you get
Legacy systems join in
Software from fifteen years ago, with no API and no support, can still be automated.
No migration project
You do not have to replace the system in order to escape the manual work inside it.
The same rights as an employee
It runs under a dedicated account with limited permissions. What an operator cannot do, nor can it.
It works at night
Large volumes of data entry can move outside working hours, where they block nobody.
How it works
1. The path
We record the exact steps an operator takes, including where they hesitate and why.
2. Anchors
Elements are found by text and structure, not screen position. A moved window breaks nothing.
- Playwright
3. Verification
After each important step it confirms the screen shows what it should. It does not type into nothing.
- Playwright
4. Exceptions
An unexpected screen stops the run and sends the capture to a person. It does not press buttons hopefully.
- Slack
Where it works well
- Software with no API but stable screens
- Repetitive entry with identical steps every time
- External portals where integration is not on offer
- Temporary bridges until a system is replaced
Where it does not
- Interfaces that change often need continuous upkeep — we say so upfront, not later
- Slower than an API: it works at the pace of screens, not of data
- We do not use it where an API exists — it would be a choice you regret
What we use
- n8n
- PostgreSQL
Where we use it
Frequently asked questions
- Does it break when the vendor updates the software?
- Sometimes, yes — which is why we prefer an API where one exists. Monitoring catches the break on the first failed run, not a week later.
- Is it legal to automate an external portal?
- It depends on their terms of use. We check first and tell you if it breaches them. We will not build something that could get your account closed.
- Does it need a machine left switched on?
- It runs on a server, not on somebody's desktop. Nobody has to leave a laptop open overnight.
- What happens with the passwords?
- A dedicated account, credentials in an encrypted vault, minimum rights. We never use any employee's personal account.
- How much upkeep does it need compared with an API?
- Realistically, several times more. That is why we recommend it as a bridge or a last resort, not a default choice.