Services / Integrations
Integrations and Business Process Automation
When people copy data by hand between a CRM, a marketplace, a spreadsheet and a messenger, mistakes are a matter of time. Closeflow turns such processes into services that run on a schedule or on an event, retry on failure and show exactly what went wrong.
02What we connect
Systems we link together
The task usually reads as “data from system A has to reach system B without anyone opening a spreadsheet”.
CRM and accounting systems
Deals, contacts, orders and statuses between the CRM, the website and internal tools, with no manual copying.
Marketplaces
Wildberries and Ozon: tariffs, stock, orders, reports. Built around API limits and errors on the platform side.
Payments and acquiring
Payment intake, payment statuses, refunds and reconciliation against provider data.
Messengers
Notifications and commands through Telegram and other channels: requests, alerts, confirmations.
Google Sheets
A spreadsheet as the interface for a team that already works in it. The service writes the data there instead of forcing everyone to switch tools.
Webhooks and custom APIs
Sending and receiving events with signature checks, delivery acknowledgement and protection against duplicates.
03Reliability
What makes it a service rather than a script
A script that “usually works” soon becomes a source of silent losses. For an integration, behaviour on bad days is what matters.
Retries with backoff
A temporary error from an external API must not lose data. The request is retried with backoff, and a permanent error lands in a visible queue for review.
Idempotency
A repeated webhook or a rerun does not create a second order or write a row twice.
Reconciliation
We periodically compare our data with the external system and find discrepancies before a customer does.
Visibility
Logs, metrics and error notifications, so a failed integration is an event and not a surprise a week later.
Limits and instability
We account for rate limits and response formats that external platforms change without notice.
04Example
wildberries-tariff-sync: a manual process turned into a service
An open example from our repositories is wildberries-tariff-sync. It is a TypeScript service that pulls Wildberries tariffs and syncs them into PostgreSQL and Google Sheets. It replaces a process that is otherwise done by hand: log in, export, paste into a sheet, compare with yesterday.
The example shows the approach itself: a data source, a reliable store and the spreadsheet the team is used to. It is a demonstration project, not a finished product for every shop, but it shows how we write this kind of thing.
The code is public: github.com/Husqvarnalox/wildberries-tariff-sync.
05Where we start
How the work runs
Review of the current process
We find out who does what by hand today, where mistakes happen and what counts as the correct result.
Contracts and data model
We fix what data comes from where, how it is stored and what counts as a duplicate.
One end-to-end scenario
We launch one working path from source to result and show it on real data.
Failures, retries, reconciliation
We add error handling, retries and discrepancy checks, then notifications.
Handoff
Deployment, documentation and a clear picture of who owns what after delivery.
06Boundaries
What we do not do
We do not configure no-code scenario builders and we do not roll out a CRM as a product. We write the code that links systems when ready-made connectors are not enough or break under load and failures.
A process that is done by hand?
Describe the systems that need to be connected and where data gets lost today. We will answer plainly and say whether we take it on.
Discuss an integration08Contact
Tell us what
has to work.
Describe the problem, your current system and its constraints. If it’s a good fit, we’ll suggest a next step — usually a short call about data, integrations and timelines.
- Telegram@missuk2003
- Emailceo@closeflow.ru
- GitHubHusqvarnalox