Skip to content
E-commerce ⇄ Data warehouse

Easypost to Google Cloud Platform integration — real-time, two-way sync

Keep Easypost and Google Cloud Platform 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 Easypost and Google Cloud Platform

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

Google Cloud Platform 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 BigQuery tables, Cloud SQL databases, Cloud Storage objects, Pub/Sub topics in Google Cloud Platform with Webhook, Shipment, Address, Parcel 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 Publish change events to Pub/Sub so downstream services react to record updates as they happen.
  • 02 Sync CarrierAccount configuration and negotiated rates so shipping options stay consistent across the storefront, ERP, and 3PL systems.
  • 03 Pull Shipment, Rate, and Refund records into a warehouse to report shipping cost per carrier and service and reclaim postage on labels that were never scanned.

Common sync patterns

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.

Inventory and order status reconciled

Stock levels and order or fulfillment status move between Google Cloud Platform and Easypost so counts and states agree across reporting and operations.

One customer master

Where both systems keep customer records, corrections in either propagate to the other so analytics and the storefront share one identity.

What you can sync between Easypost and Google Cloud Platform

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.

Easypost objects Google Cloud Platform objects How this pairing syncs
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. Cloud Storage objects Staging area for file-based bulk loads into BigQuery and other services. Address is specific to Easypost and Cloud Storage objects to Google Cloud Platform — each maps to any object or custom field on the other side.
Parcel Package dimensions and weight (or a predefined_package); created standalone or inline on a Shipment and reused across shipments and batches. Pub/Sub topics Event streams used to move change events between systems in near real time. Parcel is specific to Easypost and Pub/Sub topics to Google Cloud Platform — each maps to any object or custom field on the other side.
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. Firestore documents Document data read and written through the Firestore API for app-facing syncs. Rate is specific to Easypost and Firestore documents to Google Cloud Platform — each maps to any object or custom field on the other side.
Tracker Tracking for a shipment by tracking_code and carrier; create a Tracker to begin tracking, read status and tracking_details, and receive tracker.updated events via webhook as the parcel moves. Spanner tables Strongly consistent relational tables accessed via SQL for transactional workloads. Tracker is specific to Easypost and Spanner tables to Google Cloud Platform — each maps to any object or custom field on the other side.
Batch Bulk shipment processing; create a batch, add or remove shipments, buy all labels at once, and generate a consolidated label or ScanForm for the day's orders. BigQuery datasets Namespaces that group tables; syncs target tables within a dataset. Batch is specific to Easypost and BigQuery datasets to Google Cloud Platform — each maps to any object or custom field on the other side.
CarrierAccount Carrier credentials and settings that control which carriers and negotiated rates are available; create, update, and delete to manage enabled carriers across accounts. BigQuery tables The primary analytics destination, written through load jobs or the Storage Write API and queried with SQL. CarrierAccount is specific to Easypost and BigQuery tables to Google Cloud Platform — each maps to any object or custom field on the other side.

How changes propagate between Easypost and Google Cloud Platform

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.

Easypost Google Cloud Platform 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 Google Cloud Platform as a row-level write, with types converted between the two schemas.

Google Cloud Platform Easypost Sub-second propagation

DetectionGoogle Cloud Platform pushes changes as they happen — webhook events backed by change data capture. Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery.

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

Rate-limit considerations

  • 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.
  • Google Cloud Platform: Quotas are set per service and per project; BigQuery, Pub/Sub, and Cloud SQL each enforce their own limits.
What ships with Easypost ⇄ Google Cloud Platform

Connect Easypost and Google Cloud Platform for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Easypost ⇄ Google Cloud Platform sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Easypost and Google Cloud Platform.

How the Easypost and Google Cloud Platform connectors work

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

Google Cloud Platform

Integration surface
Per-service REST and gRPC APIs; BigQuery speaks SQL and Cloud SQL exposes standard database wire protocols
Authentication
IAM service accounts with OAuth 2.0 tokens
Change detection
Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery tables
Capabilities
read · write · CDC · webhooks
Rate limits
Quotas are set per service and per project; BigQuery, Pub/Sub, and Cloud SQL each enforce their own limits
How it works

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

    Choose tables

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

Easypost and Google Cloud Platform 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 497 integrations available for Easypost and Google Cloud Platform.

Popular · 8 of 497
All Easypost integrations All Google Cloud Platform 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