01
Marketplace sellers
Delivery slots are gone in minutes, and stock and orders are checked by hand. You need monitoring and automatic alerts.
Case: Telegram bot for Wildberries delivery slots →🔄
Automation and document processing
Less manual routine for your staff
We set up n8n: linking ERP, marketplaces and CRM into one chain. We sync stock, upload orders and catch warehouse delivery slots via the Wildberries and Ozon APIs. Tasks a person used to do by hand now run themselves.
Where ready-made integrations don't exist, we write our own: monitoring, ticketing systems, document processing — and embed them into the overall scheme.
Problems clients bring
Typical situations and what we do about them.
Leads are copied from a messenger into the CRM by hand
Requests arrive in a Telegram bot, and then someone copies them into the CRM and a spreadsheet. We build an n8n chain where the request is split into fields and lands in Bitrix24 and Google Sheets on its own.
You need to know about an event in another service right away
Around holidays, Wildberries delivery slots are taken within minutes, and a manager notices a deal status change only when they open the CRM. We poll the API or receive webhooks and send a Telegram message immediately.
Calculations and documents are done by hand
Spreadsheet formulas produce errors that surface only at the cutting stage, and documents get edited in several versions. We move the rules into code: a library calculates by formula, and documents are built from a source file with one command.
Who it is for
Types of clients we have already built this for.
02
Small businesses taking leads in a messenger
Leads from Telegram are copied into the CRM and a spreadsheet by hand. You need a pipeline where the data moves itself.
Case: Lead automation on n8n: Telegram, CRM and Google Sheets →03
Manufacturing companies
Calculations are done by hand from tables and standards. You need software that always calculates the same way and is covered by tests.
Case: FEFCO box die-line calculation in C++ →What we build
Types of work in this area. Each links to a case where it is already done.
Telegram bot requests into CRM and Google Sheets
An n8n scenario takes a message from the bot, splits it into fields, creates a record in Bitrix24 and appends a row to a spreadsheet. Every run is visible in the execution log. The result is a request with no manual copying.
Manager alerts and payment system webhooks
When a deal status changes, the CRM calls an n8n address by itself, and the scenario finds the responsible manager and messages them in Telegram. Payment system events arrive at the same node and are recorded without manual reconciliation.
Self-hosted n8n on the client's server
We install n8n on your server instead of a cloud plan: there is no cap on the number of runs, only the server's capacity. Scenarios are exported as JSON files, moved between servers and kept in git. Keys and tokens live inside n8n, not in the scenario file.
Wildberries delivery slot monitoring
A Telegram bot polls the Wildberries API every 30 seconds and sends free slots for the chosen warehouses, dates and acceptance coefficients. The message contains a direct booking link. The bot runs on a server around the clock.
Box blank and sheet layout calculation (FEFCO)
We move formulas out of spreadsheets into code: a C++17 library calculates a cardboard box blank for FEFCO styles, volumes and the layout of blanks on a corrugated sheet. Invalid input is rejected with a message, and the formulas are covered by tests. The library has no dependencies and embeds into production software.
LAN and CCTV survey with a document package
We describe the local network, video surveillance and remote access: every fact has a stated source, and anything unconfirmed goes into separate lists for on-site checking. The output is a report, internal memos and a commercial proposal with work stages.
Building Word documents from Markdown
The document source lives in Markdown in git, and a Python script builds the .docx for signing in the agreed layout: A4, Times New Roman 12. Edits go into the source, so the change history is preserved. Passwords and keys never reach the repository.
What you get
What stays with the client after handover.
- n8n scenarios as JSON files: they can be moved to another server and kept in git
- n8n on your own server rather than a cloud plan: no cap on the number of runs
- An execution log: for every run you can see whether the request went through
- A Telegram bot or alerts with filters tuned to your task
- Tests where the project includes calculations: formula and input validation checks
- Code and data stay with the client
- README written as a technical specification, and a CHANGELOG
- One month of free support after handover
How the work goes
From the first request to handover: at every step it is clear what happens next.
- 1
Request and free audit
We look at where staff copy data by hand and which systems are involved. Before any estimate, you get a list of what can be automated.
- 2
Integration check
We find out whether each system has an API or webhooks so it can join the chain. If there is no ready-made node, we plan a separate Python service.
- 3
Chain design
We describe what triggers the scenario, which steps follow and where the data ends up. You approve the design before we build.
- 4
Build and launch on the server
We build the scenarios in n8n or write a separate service and install it on the client's server. Keys and tokens are stored inside n8n.
- 5
Check against real data
We run the chain and verify the result in the execution log: the request arrived, the status changed, the row appeared in the spreadsheet.
- 6
Handover and support
We hand over the scenarios as files, a README written as a technical specification and a CHANGELOG. Support is free for a month after handover.
Stack for this area
- n8n →
- An automation builder: steps are assembled from ready-made blocks and triggered by an event, so no separate program is needed for each link.
- Webhooks →
- An address to which a system sends an event by itself: this is how the CRM reports a deal status change without waiting for someone to look.
- WB API →
- The Wildberries interface through which the bot gets delivery slots without opening the seller account.
- Python →
- The language for separate services where n8n has no ready node: the slot bot and document building.
- Google Sheets →
- A familiar tracking spreadsheet that also serves as a fallback record of requests if the CRM is unavailable.
- C++17 →
- A fast calculation library that embeds into production software with no external dependencies.
Pricing
Ballpark figures to understand the order of magnitude. Exact estimates come after the audit.
Service connections
from $80
per workflow
Webhooks and manager notifications, self-hosted n8n, document assembly from Markdown to Word.
- ✓Wildberries slot monitoring — from $160
- ✓Workflows are delivered as files and can live in git
- ✓Keys and tokens are stored in n8n, not in the file
Leads into CRM
from $400
per project
Bot or website → CRM → Google Sheets, no manual copying.
- ✓Every run is visible in the execution log
- ✓n8n on your server: no limits on runs
- ✓Scheme agreed before the build
Engineering calculations
from $500
per project
Calculation services for production: sheet layouts, nesting, calculators.
- ✓Result as a service or a spreadsheet
- ✓README as a technical specification and CHANGELOG
- ✓Free audit before the proposal
The audit and the proposal are free. No hourly billing: the price is fixed for the result, the exact figure comes in the proposal after the audit. Support after delivery starts at $100 a month, the first month is free. Timelines are individual and set once the specification is approved.
Cases in this area
4 projects — with the task, the solution and the numbers
CompletedNDA
Telegram bot for Wildberries delivery slots
for a Wildberries supplier: shipment slots without manual checking
In productionNDA
Lead automation on n8n: Telegram, CRM and Google Sheets
for a small business: a bot lead lands in Bitrix24 and a spreadsheet by itself
CompletedNDA
FEFCO box die-line calculation in C++
a library and calculator for a cardboard packaging manufacturer
In developmentNDA
Network and CCTV survey for a museum complex
for a museum complex in Moscow: a document set and a phased commercial proposal
Frequently asked questions
Can you set up n8n to integrate with Wildberries and Ozon?
Yes, we specialize in integrations with Russian marketplaces: automatic stock sync, order uploads and price updates through the WB and Ozon APIs, running reliably 24/7.
Why n8n instead of Zapier or Make?
n8n lives on your server: no operation limits, data doesn't leave for someone else's cloud, and the service won't switch off due to regional restrictions. Same scenarios — webhooks, schedules, branching — without a monthly fee for every step.
What if n8n has no integration we need?
We write our own node or a separate Python service and plug it into the chain. That's how the Wildberries warehouse slot monitor works — n8n isn't needed there, a custom bot polls the API every 30 seconds.
How do I pass a Telegram bot request into a CRM and a spreadsheet without manual work?
The bot hands the message to n8n. The scenario splits it into fields, creates a record in Bitrix24 and appends a row to Google Sheets. That is how the small-business request automation we built works: no manual copying.
How can a manager learn about a deal status change immediately?
When the status changes, the CRM calls an n8n address, which is called a webhook. The scenario finds the responsible manager and sends them a Telegram message, so they don't need to open the CRM.
Where are n8n scenarios stored and who owns them?
A scenario is exported to a JSON file that can be imported on another server and kept in git. n8n runs on the client's server, keys and tokens are stored in it rather than in the file. Code and data stay with the client.
How do I avoid missing free delivery slots on Wildberries?
The bot polls the API every 30 seconds and sends slots for the chosen warehouses, dates and acceptance coefficients. The message has a direct booking link: from the alert to booking takes about 10 seconds. A person makes the decision.
Can production calculations be automated, for example a cardboard box blank?
Yes. For a packaging manufacturer we built a C++17 library: from inner dimensions and board thickness it calculates the blank for FEFCO 0200, 0201 and 0203 and the layout on a sheet. The formulas are covered by tests. The scoring allowance should be checked against a specific plant's tooling.
Can document preparation for management be automated?
Yes. The source is kept in Markdown in git, and a script builds the .docx for signing in the agreed layout. That is how we built the survey package for a museum complex network: five internal memos and a commercial proposal. Edits go into the source, because a change made in Word is overwritten by the next build.
How much does automation cost and how fast is it done?
Linking two services, webhooks and notifications, self-hosted n8n start at $80 per workflow. Leads from a bot or website into CRM and Google Sheets start at $400. Marketplace slot monitoring starts at $160, engineering calculations for production at $500. The total depends on how many systems must be linked and whether they have an API. We name the price and timeline after a short free audit; there is no hourly billing.
Need something from “Automation and document processing”?
A short review is free: we'll look at the task and tell you what's worth doing and roughly for how much.