Skip to content
Data warehouse ⇄ E-commerce

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

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

Make BigQuery the analytics and enrichment layer behind Easypost: orders, products, and customers stay current in both directions.

BigQuery is the analytical store where the business joins, models, and reports on its data; Easypost runs the storefront, catalog, and transactions that generate most of it. The overlap is every record that has to be counted and enriched on one side and acted on the other — and when the bridge is a nightly export, the warehouse reports on yesterday while the store operates without the segments and metrics the warehouse just computed.

Stacksync syncs Clustered tables, Datasets, Projects, Tables in BigQuery with Parcel, Rate, Tracker, Batch in Easypost field by field, in real time, and in both directions. Transactional records land in the warehouse as they change, computed attributes and cleaned catalog data flow back to the store, and you decide which system owns which fields so Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Activate modeled BigQuery tables by syncing computed attributes back into sales and marketing tools
  • 02 Maintain a customer master table in BigQuery joined across CRM, billing, and support sources
  • 03 Verify and normalize customer Addresses through EasyPost before they are saved to the CRM or OMS to cut failed deliveries and carrier address-correction surcharges.
  • 04 Sync CarrierAccount configuration and negotiated rates so shipping options stay consistent across the storefront, ERP, and 3PL systems.

Common sync patterns

Live analytics on store activity

Orders, products, and customer records from Easypost land in BigQuery as they change, so dashboards and models read current data instead of last night's export.

Where Easypost accepts writes: push computed attributes back

Segments, lifetime value, and scores built in BigQuery write onto the matching records in Easypost, so merchandising and messaging act on warehouse logic.

One product catalog

Where both systems hold product or catalog data, cleaned and enriched attributes stay aligned so the store and the warehouse describe the same items.

What you can sync between BigQuery and Easypost

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 Easypost objects How this pairing syncs
Clustered tables Supported; clustering is transparent to the sync. Webhook Event subscriptions delivering an Event via HTTP POST on object changes; full CRUD (create, retrieve, list, update, delete) and the mechanism for near-real-time change delivery to Stacksync. Clustered tables is specific to BigQuery and Webhook to Easypost — each maps to any object or custom field on the other side.
Datasets Organizational container — you pick which dataset’s tables to sync. Shipment The central writable object: create with a to/from Address and Parcel, receive Rate options, then buy a label to get postage_label and tracking_code; retrieve and list with cursor pagination. Datasets is specific to BigQuery and Shipment to Easypost — each maps to any object or custom field on the other side.
Projects Connection scope: the service account grants access per project. Address Origin and destination locations; create, retrieve, and list, plus address verification (delivery and residential) to normalize and validate addresses before they are saved downstream. Projects is specific to BigQuery and Address to Easypost — each maps to any object or custom field on the other side.
Tables The syncable unit: only tables can be synced per the Stacksync docs. Parcel Package dimensions and weight (or a predefined_package); created standalone or inline on a Shipment and reused across shipments and batches. Tables is specific to BigQuery and Parcel to Easypost — each maps to any object or custom field on the other side.
Partitioned tables Synced like regular tables; partition columns map to target fields. Rate Carrier service and price options EasyPost generates on a Shipment; read-only - you select a rate id and buy it, you do not create or edit rates directly. Partitioned tables is specific to BigQuery and Rate to Easypost — each maps to any object or custom field on the other side.

How changes propagate between BigQuery and Easypost

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 Easypost 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 Easypost through its API, with automatic retries and rate-limit backoff.

Easypost BigQuery Sub-second propagation

DetectionEasypost notifies Stacksync of record changes through webhook events. Webhooks deliver an Event via HTTP POST on object changes (e.g.

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.
  • Easypost: Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests.
What ships with BigQuery ⇄ Easypost

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your BigQuery ⇄ Easypost 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 Easypost.

How the BigQuery and Easypost 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

Easypost

Integration surface
REST API (EasyPost API v2, https://api.easypost.com/v2)
Authentication
HTTP Basic auth with the API key as the username and an empty password (Bearer token also accepted); separate Test and Production keys
Change detection
Webhooks deliver an Event via HTTP POST on object changes (e.g. tracker.updated); historical pulls via list/index endpoints using before_id/after_id cursor pagination
Capabilities
read · write · webhooks
Rate limits
Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests
Easypost setup guide
How it works

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

    Choose tables

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

BigQuery and Easypost 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 500 integrations available for BigQuery and Easypost.

Popular · 8 of 500
All BigQuery integrations All Easypost 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