Source connector

Babelforce connector

Babelforce integration for databases, warehouses and BI tools

Contact center automation and call workflows. Datrise captures Babelforce entities such as calls, workflows, agents, queues, call events and dispositions, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The babelforce API v2 — Manager collection (OpenAPI 3.0.3, spec version 0.7.0, served from https://services.babelforce.com) authenticates with OAuth 2.0, API key, incremental runs key on dateCreated.start / dateCreated.end.

Of the 6 objects, 4 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `babelforce_calls`) with a schema derived from the Babelforce API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Babelforce pipeline page, and join the waitlist to get the Babelforce connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Babelforce data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
calls	babelforce_calls	Append-only, incremental by timestamp
workflows	babelforce_workflows	Upsert by primary key, incremental on updated-at
agents	babelforce_agents	Upsert by primary key, incremental on updated-at
queues	babelforce_queues	Upsert by primary key, incremental on updated-at
call events	babelforce_call_events	Append-only, incremental by timestamp
dispositions	babelforce_dispositions	Upsert by primary key, incremental on updated-at

Babelforce API: setup facts for the connector

Verified against the vendor documentation on 2026-09-14. Unknown values are left blank rather than guessed.

API	babelforce API v2 — Manager collection (OpenAPI 3.0.3, spec version 0.7.0, served from https://services.babelforce.com)
Authentication	OAuth 2.0, API key — The Manager collection's OpenAPI security block declares two alternatives: an OAuth2 password grant against /oauth/token with a single `*` (All Access) scope, or the API-key header pair `X-Auth-Access-Id` plus `X-Auth-Access-Token`.
Pagination	page — GET /api/v2/calls/reporting takes `page` and `max` query integers and returns a `pagination` object carrying `pages`, `total`, `current`, `max` and an optional `next`.
Rate limit	Not published
Incremental cursor	dateCreated.start / dateCreated.end — These two query parameters (also accepted as `filters.dateCreated.start` / `filters.dateCreated.end`) are `UnixTimestamp` integers bounding the call-creation window, and they are the only time filter GET /api/v2/calls/reporting accepts.
Webhooks	Yes — Event-triggered global automations (GET/POST /api/v2/events/triggers) fire outbound HTTP requests from the platform, which the separate Http-Proxy API exposes for monitoring at GET https://services.babelforce.com/api/v1/outbound/requests.
Bulk export	No
Deletes detectable	Yes — The `CallState` enum includes a `purged` value and the `RecordingState` enum includes a `deleted` value, both filterable through the `state` / `filters.state` query parameters, so removed calls and recordings surface as a changed state rather than silently dropping out of /api/v2/calls/reporting.

Official API reference

What bites when replicating Babelforce

Both the `Call` and `ReportingCall` schemas return a `lastUpdated` date-time, but /api/v2/calls/reporting exposes no filter on it — only `dateCreated.start` / `dateCreated.end` — so a modified-since sync is impossible and late updates force a re-pull of whole creation-date windows.
The date filters are `UnixTimestamp` integers (the spec's example is 1607904000) while the records come back with ISO-8601 `dateCreated` and `lastUpdated` strings (example 2020-04-16T22:21:38.000Z), so a connector has to convert in both directions on every request.
Historical call events cannot be swept globally: GET /api/v2/events returns the event catalog (`code` values such as `call.inbound`), and the only per-record event log, GET /api/v2/conversations/{conversationId}/events, takes `conversationId` as its sole parameter with no `page`, `max` or date filter.
Credentials are not interchangeable across collections — the Manager API accepts either the OAuth2 bearer token or the `X-Auth-Access-Id` + `X-Auth-Access-Token` pair, while the Http-Proxy API declares only a bearer `accessToken` scheme, so the header pair alone will not reach every babelforce API.

Compare this against every other documented API

Popular destinations for Babelforce

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Babelforce connector FAQ

What Babelforce data does the connector extract?: 6 objects: calls, workflows, agents, queues, call events and dispositions. Each lands in its own table with types preserved; history-style objects (2: calls and call events) load as append-only streams.
Is the Babelforce integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Babelforce data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Babelforce → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Babelforce pipeline with guided onboarding

Join the waitlist to get priority access for Babelforce integrations with guided setup, schema-aware mapping, and production-grade incremental sync.