Automation
Remove the manual copying between email, spreadsheets, and records
Automation is not there for the sake of “going digital”. It is for the place where a person copies the same fields every day. I connect services, and I build bots, documents, and regular reports, so a failure is visible and is not lost in silence.
What it takes on
- 01
Connect the systems
The site, email, the CRM, a spreadsheet, payment, and the records stop requiring copy and paste.
- 02
Build a bot
A messenger accepts a request, returns a status, or calls a person when the rule has run out.
- 03
Put documents in order
Repeated files and letters are assembled from data, not from the previous attachment.
- 04
Make the report live
The summary arrives on its own and matches the source, not the last manual export.
Who it is for
Operations teams
The day goes to moving statuses between windows.
Departments that already have a CRM
The core does not need to change, but the site, email, and the warehouse live apart.
Small companies
A full ERP is too early, and the manual routine already costs a salary.
If people have not yet agreed the rules of the process, a bot will not invent them. First we fix what counts as a request, a payment, and an error.
What can be built
Processes
Statuses, branches, and the handoff of responsibility between steps.
API
Exchange with external services, not a file kept “just in case”.
Integrations
Email, payment, messengers, spreadsheets, and accounting systems.
Telegram bots
Intake, notifications, and handing a conversation to a person.
Documents
Repeated letters, files, and packets of data.
Reports
A regular summary from the source, not from memory.
How it looks in practice
- 01
A request from the site lives apart from the CRM
The form writes to email. A manager creates the card by hand, and sometimes forgets. The link creates the card and leaves the letter only as an archive.
- 02
A client asks for the status in Telegram
The bot answers by order number and calls a person if the status is unusual. The employee does not have to find a row in order to answer “on the way”.
- 03
The report is assembled on Mondays
The same exports are stacked into one spreadsheet. The scenario does this at night, and it shows you when a source did not answer.
How development goes
- 01
Where the time is lost
The specific fields that get copied, and the cost of a mistake.
- 02
The rule
What the automation does itself, and where it stops and calls a person.
- 03
Sources
Which systems are primary, and which only receive a copy.
- 04
The scenario and the errors
A retry, a log, and a clear message if a service is unavailable.
- 05
A walkthrough
The normal path, and two or three failures, on test data.
- 06
Handover
How to switch it off, where to read the log, and who changes the keys.
Technologies
- Node.js
- Python
- REST API
- Webhook
- Telegram Bot API
- PostgreSQL
You receive a working scenario, error handling, a description of the fields, and access to the code or the scenario, so it can be changed.
Demonstrations on this topic
How to commission it
A separate scope
We take one mechanic, one link between systems, or one set of screens that can be finished and checked.
Inside a larger product
The interface, the game, or the automation sits inside a larger project. It does not live apart from the data.
Support
After handover there is a queue: fixes, new scenarios, and someone watching the system.
Questions
Is this instead of a CRM?
Not always. Automation connects what you already have. If there is nowhere for the request to live, a bot only hides the problem. Then a records system is needed first.
What happens if an external service is down?
The scenario must not lose data in silence. A retry, a log, and a message to a person are built in from the start. “It will get there somehow” is a poor handover.
Can this be done without programming, on a no-code tool?
Sometimes, yes. If the link is simple and a third-party builder suits you, I will say so. Code is needed when there are exceptions, your own rules, and no wish to put the process in a black box.
Do you work with 1C and with payments?
Yes, as external systems: an exchange of documents, statuses, and payments. The boundary between systems, and the set of fields, are fixed before development, not along the way with “we will look at the API”.
How safe is this?
Keys do not land in the frontend or in the repository. Access is granted for specific actions. What the system may change, and what it may only read, is written down in the open.