Join the LadVen OS testing programRequest a demo
Skip to main content

Integrations hub

The integrations hub is the single place where the business connects external channels and systems so they work together with CRM: messengers, website forms, telephony, document exchange, and your own applications. A connected channel stops living on its own: incoming messages, leads, and calls become inquiries with an owner, a pipeline, and a history.

The hub is in the CRM → Integrations section (route /crm/integrations). The form builder opens right next to it, at /crm/integrations/forms.

A single connection workflow​

Every connector is connected the same way, in working terms:

  1. Add. Pick a connector type from the catalog and go through the step-by-step wizard. You can often choose a ready-made business scenario so you don't have to configure everything by hand.
  2. Configure. Fill in the main fields; advanced transport and authorization parameters stay hidden until you need them. You can save the configuration as a draft and come back later.
  3. Test the connection. Run a check — it shows whether the connection is healthy and gives a clear reason if something is wrong.
  4. Enable. Save the connection with the active toggle. For the web widget and forms, this step also generates the code to embed on your website.
  5. Status and health. Every connection card has a state: active and healthy, warning, error, draft, archived, or disabled. It tells you at a glance which channels need attention.
  6. Work flow. Each type has its own working screen: lead counters for forms, a request log for the REST integration, sync jobs for document exchange, and delivery health and a retry queue for messengers.

Who sets it up​

The integrations hub is an administrator-level setup, not a daily employee action. Viewing the catalog is available with read permission for communications; creating, changing, testing, and deleting connections requires write permission (the portal administrator has full access). Without write permission the hub opens in read-only mode: you can see the connectors, but the wizard, the connection test, and the toggles are unavailable, and attempting them shows a message about insufficient permissions.

Connector catalog​

The catalog lists the types of external connections. All connectors below are implemented and available.

  • External REST integration (API key) — programmatic two-way communication: an external system creates and updates tasks and deals over the API with an access key, acting as a dedicated service account with minimal permissions. See the External REST integration page for details.
  • Telegram bot and MAX bot — two-way conversational channels: incoming messages from the messenger are attached to CRM inquiries and chats, and replies go back out through the connector.
  • Chat widget — an embeddable chat window for your website: a visitor writes from the site, and the inquiry appears in the shared CRM flow. The embed code is generated at the save step.
  • Website form — one-way intake of leads from an external form via webhook: leads turn into inquiries by the chosen scenario — straight into CRM, screened first, or local only.
  • Website forms (built-in module) — the portal's own forms, which you build and publish without a developer. They have no separate setup in the hub: the "Open forms" button leads to the form builder, and the card in the hub shows lead and CRM error counters. See also Forms.
  • Telephony — connecting an external phone provider: incoming calls are answered and routed to employees and queues by CRM rules, and the call itself is linked to a deal. The call log is available as a separate page.
  • Document exchange (SBIS) — integration with the SBIS electronic document management operator: outgoing drafts are prepared from the document card, statuses and signed copies are pulled in, and incoming documents are matched to a client. This is a regional connector for Russia.

AI is configured separately: connecting external language models and assistants — see AI and scenarios.

Good practices​

  • Give each connection a clear name and run the connection test right away, instead of enabling it "blind."
  • For each channel, assign a pipeline, a starting stage, and an owner, so a lead doesn't sit there without anyone responsible for it.
  • Check statuses regularly: a channel with a warning or error means lost leads and messages.
  • Don't show real tokens, keys, passwords, and embed code in screenshots, and don't forward them.