Skip to content
Data warehouse ⇄ CRM

BigQuery to Crustdata integration — real-time data sync

Keep BigQuery and Crustdata 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 BigQuery and Crustdata

Flow Crustdata data into BigQuery in real time — no exports, no schedulers, no custom scripts.

Crustdata is a read-only source: Stacksync reads its data in real time and delivers it into BigQuery, so BigQuery always reflects the current state of Crustdata — without exports, scripts, or schedulers.

The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.

Stacksync does both with one connection. Enrichment Responses, Companies, People, Headcount and Growth Metrics from Crustdata land in BigQuery as live tables, updated within seconds, and columns computed in BigQuery write back to fields in Crustdata. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.

Common use cases

  • 01 Stream screener results into a warehouse to maintain a living TAM and target-account universe.
  • 02 Append enrichment at lead-capture time so new records arrive scored and routable.
  • 03 Activate modeled BigQuery tables by syncing computed attributes back into sales and marketing tools
  • 04 Maintain a customer master table in BigQuery joined across CRM, billing, and support sources

Common sync patterns

A single customer view

Join Crustdata's relationship data with billing, product, and support data in BigQuery to build the customer picture the CRM alone cannot hold.

Cleanup that sticks

Deduplication and normalization done in BigQuery can be written back, so warehouse-side cleanup actually fixes the CRM.

CRM analytics on live data

Accounts, contacts, and activity from Crustdata are queryable in BigQuery moments after they change, so dashboards stop lagging the reality they describe.

What you can sync between BigQuery and Crustdata

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.

BigQuery objects Crustdata objects How this pairing syncs
Tables The syncable unit: only tables can be synced per the Stacksync docs. People Contact and profile data for decision-makers; read into a CRM or outreach tool to fill missing titles, emails, and LinkedIn profiles. Tables is specific to BigQuery and People to Crustdata — each maps to any object or custom field on the other side.
Partitioned tables Synced like regular tables; partition columns map to target fields. Headcount and Growth Metrics Time-series employee counts by department and region; read to score accounts on hiring momentum and expansion signals. Partitioned tables is specific to BigQuery and Headcount and Growth Metrics to Crustdata — each maps to any object or custom field on the other side.
Clustered tables Supported; clustering is transparent to the sync. Tech Stack Detected technologies per company; read to build segments and route accounts by the tools they already use. Clustered tables is specific to BigQuery and Tech Stack to Crustdata — each maps to any object or custom field on the other side.
Datasets Organizational container — you pick which dataset’s tables to sync. Screener Results Saved company searches with filter criteria; read on a schedule so target-account lists in the CRM refresh as companies enter the criteria. Datasets is specific to BigQuery and Screener Results to Crustdata — each maps to any object or custom field on the other side.
Projects Connection scope: the service account grants access per project. Enrichment Responses Real-time enrichment lookups keyed by domain or profile URL; read to append fresh firmographic and contact data at form-fill or record-creation time. Projects is specific to BigQuery and Enrichment Responses to Crustdata — each maps to any object or custom field on the other side.

How changes propagate between BigQuery and Crustdata

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.

BigQuery Crustdata 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").

DeliveryCrustdata does not accept inbound record writes, so this direction carries requests rather than records: Crustdata's output flows back as field updates on the originating BigQuery records.

Crustdata BigQuery Interval-based propagation

DetectionStacksync polls Crustdata for changes on an incremental schedule, reading only records changed since the previous pass. Pull-based: real-time enrichment endpoints for on-demand lookups plus periodic re-pulls of screeners and datasets.

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

Rate-limit considerations

  • 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.
  • Crustdata: Requests are metered by plan credits and per-minute rate limits; bulk dataset pulls are the efficient path for large refreshes rather than per-record enrichment calls.
What ships with BigQuery ⇄ Crustdata

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever BigQuery or Crustdata 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 BigQuery or Crustdata record.

Observability

Monitoring

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

Trading partners

EDI

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

How the BigQuery and Crustdata connectors work

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

Crustdata

Integration surface
REST API (JSON)
Authentication
API token — Authorization: Token header issued per workspace
Change detection
Pull-based: real-time enrichment endpoints for on-demand lookups plus periodic re-pulls of screeners and datasets; no webhooks or change feed
Capabilities
read
Rate limits
Requests are metered by plan credits and per-minute rate limits; bulk dataset pulls are the efficient path for large refreshes rather than per-record enrichment calls.
How it works

How to connect BigQuery to Crustdata — 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 BigQuery and Crustdata 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
    BigQuery connected
    Crustdata connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the BigQuery and Crustdata 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 · BigQuery ⇄ Crustdata
    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
    BigQuery Crustdata
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

BigQuery and Crustdata 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
CSA STAR
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 340 integrations available for BigQuery and Crustdata.

Popular · 4 of 340
All BigQuery integrations All Crustdata 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