Data Sources

Overview

The Data Source area is the control plane for inbound integrations. A source can be:

a CRM source, such as Bitrix24
a direct telephony source, such as Streamtelecom
the public API — no vendor connection at all; you push call and chat data yourself with an API key

Data Source management lives in Settings -> Data Source.

Tabs

The section currently uses two tabs:

Connection

Use this tab to:

see the currently connected source
review connection metadata, such as vendor/domain/install date
change the source
disconnect the source

Changing or disconnecting a source uses confirmation dialogs because it affects ingest behavior.

Disconnecting a CRM app (Bitrix24, Uspacy) stops ingest and unsubscribes the portal from the call events it was sending. The app itself stays installed in your portal — remove it there if you also want it gone from the interface. Existing records and analyses are kept.

Records that arrived but had not finished processing when you disconnected end up as Not applicable: there is nothing left to analyse them from, and this is not treated as a failure.

A disconnected CRM app can be switched back on from the same tab: the Connection tab shows it as Disconnected with a Reconnect button, which re-subscribes the portal to call events. If the portal’s authorisation has expired in the meantime, reconnecting reports that the app has to be installed in the portal again.

Import

Use this tab to trigger an initial or catch-up import when the source supports it.

Notes:

Bitrix24 supports CRM-oriented import flows
Streamtelecom supports direct telephony import via CDR history
other telephony vendors may expose webhook ingest before they expose a full import client

An import spends your balance per record, so it is a two-step action: choose the scope and the date range, press Calculate cost, and Aelo reports how many records the range holds, how many billable minutes that is, and how much will be charged against your plan’s included minutes and your wallet. Start unlocks only after that — and changing the range asks for a fresh calculation, so the figure you approve is always the figure for the range you are importing. If the estimate exceeds your balance you can still proceed, but you have to type the amount to confirm it.

Telephony CDR imports cover at most 30 days per run — the provider’s own API limit. Import a longer history as consecutive runs.

CRM field mapping (delivering analysis results back to the CRM) is no longer a tab of this section — it’s configured separately, under Analysis Setup → CRM Updates, and is available only to Bitrix24 organizations. Smart Process controls are Bitrix24-specific.

Source Wizard

When no active source is connected, Aelo shows a multi-step source wizard:

Select source
Configure credentials/settings
Test connection
Import initial data (when supported)

The Public API card on the select-source step is a fourth path that skips steps 2-4 entirely: it takes you straight to Settings → API Keys to issue a key, instead of walking you through a vendor’s credentials. See Public API for the full reference. The card only appears when your organization can reach that section; on the free plan the section itself is still visible, but shows a plan-upgrade explanation instead of the key-creation form.

Current Support Model

Bitrix24

full CRM integration
embedded app support
webhook ingest
delivery configuration
Smart Process support

Unitalk

direct telephony source, cloud PBX / contact center
webhook ingest
test/setup through the Data Source flow
no bulk import: calls arrive by webhook from the moment you connect
no CRM write-back

Streamtelecom

direct telephony source
webhook ingest
test/setup through the Data Source flow
import/backfill from CDR history
no CRM write-back

Two data streams

Streamtelecom provides two independent streams:

Call history (CDR) — imported right after you connect with a login, password, and API key. Find the API key in the Stream Telecom console: Administration → Company Profile → API KEY.
Real-time calls — delivered via a webhook that only Stream Telecom support can activate (it cannot be self-served). On the wizard’s “Real-time call capture” step, copy your webhook URL and send the prepared email to support@streamtele.com — this subscribes you to Stream CALL API v3.0 events. Activation usually takes up to 24 hours. The same URL and instructions are always available under Settings → Data Sources → Connection.

Binotel

available in the source model
useful for registration and webhook-driven ingest
feature depth is currently narrower than Streamtelecom for direct import

Ringostat

cloud PBX, same category as Streamtelecom and Binotel — not a call-analytics tool
listed in the source catalog, but marked unverified: the webhook schema was guessed rather than confirmed against live Ringostat data, and call-history (CDR) import isn’t implemented
do not treat it as a working integration until it has been verified

Active Source Rules

only one active telephony source is allowed per organization
switching the active source deactivates the previous telephony source
connection state is read from the backend, not guessed locally by the UI

Typical Workflow

Open Settings -> Data Source
Start the wizard or open Change
Select the provider
Enter vendor-specific credentials/config
Run the connection test when available
Start initial import if the source supports it
For CRM sources, configure field mapping under Analysis Setup → CRM Updates

CRM Updates Notes

For CRM-capable sources, the Analysis Setup → CRM Updates step can include:

field mapping
transcript/summary/score delivery toggles
Smart Process setup or repair actions when applicable

For telephony-only sources, Aelo treats the integration as ingest-only, and the CRM Updates step is not available.

Troubleshooting

The wizard opens even though a source is connected

This usually means the UI could not resolve the active source query. Check API connectivity and re-open the Data Source section.

CRM Updates step is unavailable

That is expected for direct telephony sources — the Analysis Setup → CRM Updates step exists only for Bitrix24 organizations.

Smart Process controls are missing

Smart Process is Bitrix24-specific. If the active provider is not Bitrix24, those controls are intentionally hidden.