
The most expensive work in a business is what a person does between two programs: retype, forward, recalculate. We connect systems directly and decide in advance what happens when an outside service stops answering.
What’s included
- API integrations
- Banks, delivery services, auctions, registries. For example, the National Bank exchange rate and VIN decoding through the official US registry.
- Data sync
- One source of truth: the ART AUTO site re-reads tariffs from the client’s bot every 30 minutes.
- Automatic documents
- Invoices, bills and contracts as PDF, generated from the deal data with no copying by hand.
- Notification queues
- Telegram messages to the team and clients, retried if a service is briefly unavailable.
- Desktop apps
- Electron apps for Windows and macOS, like the ART AUTO trading terminal with bid limits and an activity log.
- Safety margin
- Timeouts on outside requests, last saved data, and a plain explanation for the owner when something goes wrong.
Where it already runs
-

Trading terminal
The auction in a protected window, one-time launch links valid for 30 seconds.
-

Terminal access
The owner grants and revokes access; the window closes within 30 seconds.
-

Bidding bridges
The channels that carry bids to auctions, with a “Stop all” button.
-

Request path
Steps from quote to car handover that the client sees in the portal.
How we automate
First, where the time goes. We sit with the team and count the minutes spent on every forward and recalculation.
Then, the shortest chain. We automate what repeats most often and leave the rare cases to people, with a hint.
Next, a safety margin. What happens when a service is down, data looks odd or a person makes a mistake is written down and covered by tests.
After launch, monitoring. Logs and notifications show the automation is working and where it is worth extending.
Technologies
TypeScript · Node.js · Cloudflare Workers · Electron · Telegram Bot API · REST · WebSocket
Questions
Where should automation start?
With the process that repeats every day and breaks most often: requests, payments or documents. The first result should be visible in a week or two, not in six months.
What if an outside service goes down?
The system will not wait forever: a timeout, the last saved data and a message to the owner with the reason. That is how the ART AUTO calculator behaves when the bot or the bank is not answering.
Everything we have is in Excel. Is that a problem?
No, it is a normal starting point. The spreadsheet can stay the data source and the system will read it, or we move the data into a database.
Can you automate without replacing our current software?
Often yes: we connect to what you already have through APIs, webhooks or imports, and add only the missing link.