Integrations
Systems that work together
We connect your website to accounting, CRM, payments and delivery so data flows on its own and managers don't recalculate or copy anything by hand.
Accounting, CRM, payments and delivery, connected
We connect the services a business can't run without. If a system has an API, we'll work with it too.
Accounting systems
Exchange of products, prices, stock and orders.
- 1C
- MoySklad
CRM
Leads and orders from the site go straight to managers.
- Bitrix24
- amoCRM
- RetailCRM
- Megaplan
- Notion
Online payments
Customers pay on the site the way they like.
- Kaspi Pay
- TipTopPay
- Bank acquiring
Delivery
Exact cost and timing right on the site.
- CDEK API
Marketplaces
Product export so you can sell there too.
- Kaspi store
Notifications
New orders and statuses go to a manager's messenger.
- Chatbots
Forms and leads
Every enquiry from the site is saved and never lost.
- CRM
POST /api/orders { "status": "paid", "sync": ["1c", "crm"] }
Any API
We connect the site to external services and your own systems.
- REST API
- Webhooks
Less manual work, faster client decisions
How integrations changed our clients' work.
- Open the website
- Call the company
- Wait for a manager
- Get a price
- Open the website
- Pick a route
- See the exact price
API keys never reach the browser
Requests to external services go through an intermediate server: the key is stored only there, even when the site is built on a website builder.
Tilda website
no key here
Our server
the key lives here
CDEK API
rates & pricing
A CDEK API delivery calculator
We built this calculator into the CDEK Business Tilda site in 3 days. Press “Calculate”.
CDEK BusinessFrom analysis to stable operation
An integration isn't just code: it's agreements with the services and monitoring after launch.
- First step
Systems analysis
Which data, from where, to where
- Before development
Exchange design
Schedule, formats, errors
- In parallel
Access and APIs
We handle it with the services
- From 3 days
Build and test
Server, exchange, checks
- Ongoing
Support
We watch the exchange and API changes
- First stepSystems analysisWhich data, from where, to where
- Before developmentExchange designSchedule, formats, errors
- In parallelAccess and APIsWe handle it with the services
- From 3 daysBuild and testServer, exchange, checks
- OngoingSupportWe watch the exchange and API changes
Integrations in our projects
Can you connect an API to a Tilda website?
Yes. For CDEK Business we added a CDEK API delivery calculator to a Tilda site, and it launched in 3 days.
Won't the API keys leak?
No: requests go through an intermediate server and the key is stored only there. It never reaches the visitor's browser.
How often is data from 1C updated?
On an agreed schedule. At Ecoshop the catalog syncs every two hours instead of once a day.
Which CRMs do you work with?
Bitrix24, amoCRM, RetailCRM, Megaplan and Notion: leads and orders from the site land there automatically.
Which payment methods do you connect?
Kaspi Pay, TipTopPay and bank card acquiring, and we can export products to a Kaspi store.
What if a service changes its API?
We stay on for support: we monitor the exchange and update the integration when the service changes.
Shall we connect your systems?
Tell us which services you use — we'll propose a data exchange design.