Skip to content

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 (Starter and above, or during the Pro trial of a free organization) — 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 and its connection status
  • 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.

Uspacy is different: disconnecting pauses its call processing, so Reconnect cannot bring it back. The card then says Processing not authorized and offers Give consent, which opens Settings → Consent Management. Consent given there switches the connection back on. Removing the app from the portal does not withdraw processing: it stops intake and deletes Aelo’s access to the portal. Until the app is installed again, the card says App removed from the portal. Install it in the portal again and processing resumes as it was before the removal, with no new consent, together with the reports and deal-state comments sent to Uspacy as you had them set. Processing you paused or withdrew yourself stays paused or withdrawn after a reinstall: give consent for it as above. If Aelo had moved the reports to the organization’s other CRM while this one was not delivering, they go back to it once it works again. What Aelo may do with the portal’s data is set out in the Data Processing Agreement, section 2.1: the separate Uspacy organization processing instruction is part of it.

The Deal state comment switch for a connected Bitrix24 or Uspacy source is not on this tab: it is under Analysis settings → CRM updates, in the What else to do in the CRM list — on by default, available on Pro and higher plans and in the Pro trial of a free organization, changed by the Owner and the Admin, and saved with the whole step by Save changes. After each analysed conversation of a deal or lead, Aelo adds a separate comment with the deal state to the CRM timeline — only in the organization’s active CRM (the one that receives call reports) and only for conversations up to 7 days old. The switch does not depend on the Report as a comment and Report as a note rows. See Deals.

Import Records

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

Notes:

  • Bitrix24 supports CRM-oriented import flows
  • Streamtelecom and Binotel support 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.

A Streamtelecom import covers at most 30 days per run — the limit of Streamtelecom’s own CDR API. Import a longer history as consecutive runs. Binotel has no such limit. Its cost estimate, though, currently stops counting at the first day without calls and after 40 days, so for such a range it can come out lower than the debit: before you start a long Binotel import, compare the record count in the estimate with the call log in Binotel.

Choosing CRM fields for analysis results (delivering them back to the CRM) is no longer a tab of this section — it is a separate step, Analysis Setup → CRM Updates. The step is shown to every Bitrix24 and Uspacy organization. For Bitrix24 it holds the delivery destination (CRM card or Smart Process), the field table for analysis results, the What else to do in the CRM list and the save panel; Smart Process controls are Bitrix24-specific. For Uspacy the same step, with the same save panel, holds the Report as a comment and Report as a note rows (both on after connecting; they can now be turned off) and, on plans that include the deal state (Pro and higher), Deal state comment. The connection status is not in the step — it is on the Connection tab of this section, and the Sync CRM Users button has moved to Settings → Team → Org structure (see Team).

Source Wizard

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

  1. Connect data source — pick the provider.
  2. Configure — enter the provider’s credentials.
  3. Testing connection — Aelo checks the credentials by itself; if the check fails, Try different key takes you back to step 2.
  4. Real-time call capture — the webhook address (and secret). Ringostat and Unitalk take it in their own settings; for Stream Telecom and Binotel only the provider’s support can register it, and the step prepares the email to send.
  5. Import existing records — call history is imported for Stream Telecom and Binotel. Unitalk and Ringostat have no history import: the step is shown, but the Import records tab says there is no bulk import for the source. An audio-only source skips this step.

The first step of the wizard: providers grouped into telephony, CRM and direct upload

The first step groups the cards by how a source connects:

  • Telephony — webhook + API key: Stream Telecom, Binotel, Unitalk and Ringostat. These cards are the ones that walk through steps 2-5 above. Step 4 is there because a telephony brings new calls by webhook: Aelo gives you the address, and it is registered with the provider as step 4 describes.
  • CRM — OAuth, app in your account: Bitrix24. The card has no steps of its own — it opens the Bitrix24 Market in a new tab, where you install the Aelo app.
  • Direct upload: the Public API and My system isn’t listed cards described below.

When you add a telephony as an audio-only source, the ladder is four steps long: there is no import step.

The Public API card on the select-source step is a separate path that skips steps 2-5 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.

If you are not the account owner, the Public API card is shown greyed out with “Issuing keys is available to the account owner”.

The My system isn’t listed card next to it is for a CRM or telephony Aelo does not connect yet: it opens a short form where you describe your stack, and we estimate a connector.

The "My system isn't listed" form

Current Support Model

Bitrix24

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

Unitalk

The Unitalk form: a single API key

  • direct telephony source, cloud PBX / contact center — beta
  • webhook ingest
  • test/setup through the Data Source flow
  • no bulk import of past calls: calls arrive by webhook, and Aelo also pulls new calls from Unitalk’s call history every few minutes, so a call the webhook missed still arrives
  • no CRM write-back

Streamtelecom

The Stream Telecom form: username, password and API key

  • 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:

  1. 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.
  2. 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 URL contains a secret token, so send it to Stream Telecom support only; it is always available again under Settings → Data Source → Connection via Show address (owner and admins).

Binotel

The Binotel form: key and secret

  • direct telephony source
  • webhook ingest (calls are accepted from Binotel’s addresses)
  • import/backfill from CDR history
  • can also be the audio-only source for records that arrive from Bitrix24
  • no CRM write-back

Ringostat

The Ringostat form: a single API key

  • cloud PBX, same category as Streamtelecom and Binotel — not a call-analytics tool
  • beta: webhook ingest through the Data Source flow — calls arrive once the webhook is set up in Ringostat with the Authorization header (setup steps)
  • the webhook payload format hasn’t been confirmed on live Ringostat data yet, and the connection test doesn’t call Ringostat: if calls don’t appear after setup, contact support
  • no bulk import: call-history (CDR) import isn’t available
  • no CRM write-back

Active Source Rules

  • one active telephony source per role (record source or audio-only source), not 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

  1. Open Settings -> Data Source
  2. Start the wizard or open Change
  3. Select the provider
  4. Enter vendor-specific credentials/config
  5. Run the connection test when available
  6. Start initial import if the source supports it
  7. For CRM sources, choose the fields for results under Analysis Setup → CRM Updates

CRM Updates Notes

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

  • the delivery destination: CRM card or Smart Process, with Smart Process creation and repair (Bitrix24)
  • the field table for analysis results (Bitrix24)
  • the What else to do in the CRM list (for Uspacy: report as comment, report as note and deal state comment)
  • the save panel

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 and Uspacy organizations. For Uspacy it exists for every organization, on any plan.

Smart Process controls are missing

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