Skip to content
Communications ⇄ Data warehouse

Aircall to BigQuery integration — real-time, two-way sync

Keep Aircall and BigQuery in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Aircall and BigQuery

Land the messages, calls, and events from Aircall in BigQuery as live tables, and write results back, without building or maintaining a pipeline.

Aircall produces a constant stream of activity — messages sent and received, calls placed and answered, meetings held, and the delivery and engagement events attached to them. That record is what the rest of the company wants to analyze, and it usually sits behind an API rather than in the warehouse. Building and babysitting an extraction pipeline is the tax most teams pay to get it out.

Stacksync syncs Users, Numbers, Tags, Teams from Aircall into tables in BigQuery in real time, handling schema, rate limits, and retries. Because the connection works in both directions, results computed in BigQuery — segments, contact updates, suppression flags — can be written back into fields in Aircall wherever it exposes them, so analysis lands where outreach actually happens.

Common use cases

  • 01 Provision and deprovision Users and Team membership from an HR system or IdP so the agent roster, seats, and routing groups stay current.
  • 02 Send outbound SMS/MMS through the Messages API when a CRM or database record changes (appointment reminders, alerts) and write inbound replies back.
  • 03 Land CRM and ERP records in BigQuery continuously so dashboards reflect business systems without nightly batch jobs
  • 04 Activate modeled BigQuery tables by syncing computed attributes back into sales and marketing tools

Common sync patterns

Communications analytics without ETL

Messages, calls, and events from Aircall arrive in BigQuery as queryable tables, current within seconds instead of a day behind.

Engagement and delivery on live data

Sends, opens, clicks, bounces, and call outcomes from Aircall land in BigQuery as they happen, so deliverability and response monitoring stop lagging the reality they describe.

Activity joined with everything else

Combine Aircall's activity with the CRM, product, and support data already in BigQuery to attribute outcomes to the touches that drove them, which no single tool can do alone.

What you can sync between Aircall and BigQuery

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Aircall objects BigQuery objects How this pairing syncs
Calls Inbound and outbound call records with recording URL, duration, tags, comments, and metadata; the record itself is read-only, but you can add tags, comments, insight cards, transfer, archive, and control recording. Datasets Organizational container — you pick which dataset’s tables to sync. Calls is specific to Aircall and Datasets to BigQuery — each maps to any object or custom field on the other side.
Users Agent seats with name, email, and availability; full CRUD to provision or deprovision seats and map Aircall agents to CRM, HR, or directory identities. Projects Connection scope: the service account grants access per project. Users is specific to Aircall and Projects to BigQuery — each maps to any object or custom field on the other side.
Numbers Provisioned phone numbers with settings, open hours, and IVR config; read and update to keep routing and business-hours data aligned across systems. Tables The syncable unit: only tables can be synced per the Stacksync docs. Numbers is specific to Aircall and Tables to BigQuery — each maps to any object or custom field on the other side.
Tags Call tags with name and color; full CRUD, applied to calls for disposition and outcome reporting in the CRM or warehouse. Partitioned tables Synced like regular tables; partition columns map to target fields. Tags is specific to Aircall and Partitioned tables to BigQuery — each maps to any object or custom field on the other side.
Teams Groups of users for routing and reporting; create and delete teams and add or remove members to mirror org structure from an HR system or IdP. Clustered tables Supported; clustering is transparent to the sync. Teams is specific to Aircall and Clustered tables to BigQuery — each maps to any object or custom field on the other side.

How changes propagate between Aircall and BigQuery

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Aircall BigQuery Sub-second propagation

DetectionAircall notifies Stacksync of record changes through webhook events. Webhooks (POST /v1/webhooks) for call, contact, user, message, and number events.

DeliveryEach detected change is applied to BigQuery as a row-level write, with types converted between the two schemas.

BigQuery Aircall Sub-second propagation

DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").

DeliveryEach detected change is written to Aircall through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Aircall: 60 requests per minute per company by default (120/min for Advanced Messaging customers); responses carry X-AircallApi-Limit, X-AircallApi-Remaining, and X-AircallApi-Reset headers.
  • BigQuery: Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes.
What ships with Aircall ⇄ BigQuery

Connect Aircall and BigQuery for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Aircall–BigQuery connection.

Real-time

Two-way sync

Changes in Aircall or BigQuery instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Aircall or BigQuery data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Aircall or BigQuery record.

Observability

Monitoring

Track your Aircall ⇄ BigQuery sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Aircall and BigQuery.

How the Aircall and BigQuery connectors work

Aircall

Integration surface
REST API (Aircall Public API v1, https://api.aircall.io/v1)
Authentication
HTTP Basic auth (base64 api_id:api_token) for single-account integrations, or OAuth 2.0 authorization_code flow for multi-tenant Technology Partner apps
Change detection
Webhooks (POST /v1/webhooks) for call, contact, user, message, and number events; historical pulls via list endpoints paged with from/to timestamps and order
Capabilities
read · write · webhooks
Rate limits
60 requests per minute per company by default (120/min for Advanced Messaging customers); responses carry X-AircallApi-Limit, X-AircallApi-Remaining, and X-AircallApi-Reset headers
Aircall setup guide

BigQuery

Integration surface
GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
Authentication
Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide
How it works

How to connect Aircall to BigQuery — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Aircall and BigQuery with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Aircall connected
    BigQuery connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Aircall and BigQuery objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Aircall ⇄ BigQuery
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Aircall BigQuery
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Aircall and BigQuery integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 446 integrations available for Aircall and BigQuery.

Popular · 7 of 446
All Aircall integrations All BigQuery integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own