An integration is a link between two programs: data moves from one to the other by itself, without manual copying. A native integration is a direct connector inside the AI-CRM with two-way sync: a Payme payment changes the deal status by itself, and an enquiry from Telegram becomes a customer record at once. A universal connector, or iPaaS, is a separate go-between service that passes an event along an “if this, then that” scenario, usually one way and with per-operation billing. For a CRM built on Uzbekistan’s payments and channels, native is more reliable: according to the Central Bank, 74.6 million bank cards were in circulation on 1 July 2026, and global iPaaS platforms usually do not support Payme, Click, Uzcard or Humo. In Zukko.AI ready-made connectors are on every plan, data is stored in Uzbekistan, and a missing service you connect yourself through the open API and webhooks from the Business plan, or we build your own integration on the Enterprise plan by quote.
What an integration is and how a native connector differs from iPaaS
An integration is a configured exchange of data between two systems: a request from Instagram becomes a deal in the CRM by itself, and a payment changes the order status by itself. A connector is the ready-made adapter that performs this exchange: it knows how both systems are built and passes data on a schedule or when an event happens. One question remains — who built that connector and where it runs.
A universal (no-code) connector, or iPaaS, is a separate go-between service. It catches an event in one application and passes it to another by an “if — then” scenario. It is quick for simple chains, but the data travels through a third party, and the depth of the sync is limited to whatever the external API exposes.
A native integration is a connector inside the AI-CRM itself. It connects to the service directly, with two-way sync: a change on either side shows up on the other with no link in between. How the whole integration layer is built is covered in the AI-CRM integration guide.
Native or iPaaS: comparison
| Criterion | Zukko native connector | Universal (no-code) connector / iPaaS |
|---|---|---|
| Sync | Two-way, out of the box | More often one-way, scenario-based |
| Intermediate layer | None — a direct connection | Yes — data goes through a go-between |
| Local payments | Payme, Click, Uzcard, Humo | Usually not supported |
| Cost | Included in every plan | Billed per task or operation, grows with volume |
| Reliability | A stable connector | Fragile when an API changes, scenarios that stop running |
| Data | Stored in Uzbekistan (Law ZRU-547) | Passes through the provider’s infrastructure |
| If there is no connector | You connect it yourself through the open API and webhooks from the Business plan; your own integration on the Enterprise plan, by quote | Limited to the provider’s catalogue |
When iPaaS fits and when a native connector does
- iPaaS fits a rare one-off link between two third-party services, where deep sync is not needed and no sensitive data passes through.
- A native connector is needed when the CRM is the working sales system: inbound messages from channels, payments, calls and deals have to live in one customer record with nothing lost.
Scenario automation inside the platform itself is covered by AI automation — with no external go-between.
What if the connector you need does not exist
This is a common argument for iPaaS: “it has everything”. But in Zukko you connect your own service yourself through the open API and webhooks from the Business plan, and on the Enterprise plan we build your own integration by quote. There is also no vendor lock-in: your data stays yours and export is available at any time. The full list is on the Integrations page.
Why this matters for Uzbekistan
The main local wedge is the payment rails: Payme, Click, Uzcard, Humo. The scale shows in the statistics of the Central Bank of Uzbekistan: 74.6 million bank cards were in circulation in the country as of 1 July 2026. Global iPaaS platforms and CRMs built abroad usually do not support these rails, so the link has to be pieced together by hand and watched so that it does not fall apart. A native connector covers local payments and channels (Telegram, Instagram) at once, and the data stays in Uzbekistan.
What the business gets
- Fewer breakdowns — no fragile intermediate layer that fails when an API changes.
- Local payments out of the box — Payme, Click, Uzcard, Humo, which global iPaaS platforms lack.
- Data under control — stored in Uzbekistan, export at any time, no vendor lock-in.
- Predictable cost — ready-made connectors are included in every plan.
Frequently asked questions
What is an integration in plain words
An integration is a link between two programs: data moves from one to the other by itself, without manual copying. For example, a customer writes in Telegram and a deal appears in the CRM; the customer pays through Payme and the order status changes to “paid”. Without it, a manager copies the same data by hand, late and with mistakes.
What is a connector
A connector is a ready-made module that links a CRM to one specific service: a messenger, a payment system, telephony or accounting software. It knows the data format on both sides and passes data on when an event happens. A native connector is built into the platform itself; a universal one works through a separate go-between service.
Is Zukko an alternative to universal no-code connectors
For scenarios around the CRM, yes. Native connectors and [AI automation](/platform/ai-automation) replace links built through iPaaS: requests from channels, payments and calls land in one customer record with two-way sync and no go-between. For linking two third-party services that have nothing to do with the CRM, a universal connector is still the more convenient tool.
Can a universal connector be used alongside Zukko
Yes. A universal connector suits rare one-off chains where deep sync is not needed and no sensitive data passes through. For working sales — channels, payments, calls, deals — native connectors are more reliable: they connect directly and do not depend on an intermediate service that can stop when an external API changes.
Do universal iPaaS connectors support Uzbekistan’s local payments
Usually not. Payme, Click, Uzcard and Humo are Uzbekistan’s payment infrastructure, and the catalogues of global iPaaS platforms generally do not include these connections. The link has to be assembled by hand and then watched. In [Zukko](/platform/sales-ai) the payment link is generated right in the chat, and the payment confirmation returns to the conversation and to the customer record.
What if the connector we need is not in the catalogue
From the Business plan you connect the service yourself through the open API and webhooks, and on the Enterprise plan we build your own integration by quote. Events are passed on in real time: a new lead, a payment, a deal status. There is no vendor lock-in: the data stays yours and export is available at any time.
Where is the data stored
In Uzbekistan, in line with Law ZRU-547 on personal data. With a native integration the data travels directly between the service and the CRM and does not pass through a third-party go-between’s infrastructure, as it does with universal connectors. Export is available at any time, so no dependence on the vendor arises.