Skip to content
Data warehouse ⇄ Developer tools

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

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

Close the gap between analytics and operations: Google Cloud Platform holds the record while Google Pubsub runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.

Google Cloud Platform is the central store where teams keep Pub/Sub topics, Firestore documents, Spanner tables, BigQuery datasets for reporting and analysis; Google Pubsub runs the operational side of engineering work — tracking issues, moving messages and events, watching systems, and managing users and access. The two overlap wherever the same operational data matters to both: the Topics, Subscriptions, Messages, Schemas produced in Google Pubsub are exactly what analysts want to measure in Google Cloud Platform, and the curated rows in Google Cloud Platform are what should drive the next action in Google Pubsub. When that overlap is bridged by nightly ETL or hand-written scripts, dashboards lag a day behind reality and the tools that should react to warehouse signals never see them.

Stacksync syncs Pub/Sub topics, Firestore documents, Spanner tables, BigQuery datasets in Google Cloud Platform with Topics, Subscriptions, Messages, Schemas in Google Pubsub field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync matches records on a stable external key, keeps every copy consistent, and resolves conflicts by rules you set — so analytics and operations work from the same current data instead of two drifting copies.

Common use cases

  • 01 Publish change events to Pub/Sub so downstream services react to record updates as they happen.
  • 02 Publish new and changed database rows as messages to a Pub/Sub topic so multiple downstream subscriptions consume the change stream independently.
  • 03 Consume messages from a subscription via StreamingPull and write them into a Postgres or warehouse table for durable, SQL-queryable storage.

Common sync patterns

Operational data lands in Google Cloud Platform for analytics

Records created in Google Pubsub — issues, events, messages, metrics, or user changes — replicate into Google Cloud Platform tables as they happen, so reporting runs on current data instead of last night's export.

Warehouse signals reach Google Pubsub

A row scored, flagged, or enriched in Google Cloud Platform creates or updates the matching record in Google Pubsub, so the operational tool acts on the same data the analysts already see.

Backfill history, then stay live

Load the existing set of Topics, Subscriptions, Messages, Schemas into Google Cloud Platform once, then keep it current with every change — you get full history plus real-time updates without a separate pipeline.

What you can sync between Google Cloud Platform and Google Pubsub

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.

Google Cloud Platform objects Google Pubsub objects How this pairing syncs
BigQuery tables The primary analytics destination, written through load jobs or the Storage Write API and queried with SQL. Schemas Avro or Protocol Buffer definitions bound to a topic; validate that every published message matches the agreed structure. BigQuery tables is specific to Google Cloud Platform and Schemas to Google Pubsub — each maps to any object or custom field on the other side.
Cloud SQL databases Managed Postgres, MySQL, and SQL Server instances synced like ordinary relational databases. Snapshots Captured subscription state for seek/replay; lets already-acknowledged messages be redelivered from a point in time. Cloud SQL databases is specific to Google Cloud Platform and Snapshots to Google Pubsub — each maps to any object or custom field on the other side.
Cloud Storage objects Staging area for file-based bulk loads into BigQuery and other services. Message attributes Up to 100 key-value pairs per message; carry routing metadata and drive subscription filter expressions. Cloud Storage objects is specific to Google Cloud Platform and Message attributes to Google Pubsub — each maps to any object or custom field on the other side.
Pub/Sub topics Event streams used to move change events between systems in near real time. Dead-letter topics Destination for messages that exceed a subscription's max delivery attempts; isolates poison messages for later handling. Pub/Sub topics is specific to Google Cloud Platform and Dead-letter topics to Google Pubsub — each maps to any object or custom field on the other side.
Firestore documents Document data read and written through the Firestore API for app-facing syncs. Ordering keys Tag messages so those sharing a key deliver in publish order when message ordering is enabled; throughput capped at 1 MBps per key. Firestore documents is specific to Google Cloud Platform and Ordering keys to Google Pubsub — each maps to any object or custom field on the other side.
Spanner tables Strongly consistent relational tables accessed via SQL for transactional workloads. Topics Named resource publishers send to; Stacksync publishes each record change as a message to a topic for downstream subscribers to consume. Spanner tables is specific to Google Cloud Platform and Topics to Google Pubsub — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Platform and Google Pubsub

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.

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

Google Pubsub Google Cloud Platform Sub-second propagation

DetectionGoogle Pubsub notifies Stacksync of record changes through webhook events. Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST.

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

Rate-limit considerations

  • Google Cloud Platform: Quotas are set per service and per project; BigQuery, Pub/Sub, and Cloud SQL each enforce their own limits.
  • Google Pubsub: Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key.
What ships with Google Cloud Platform ⇄ Google Pubsub

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Google Cloud Platform and Google Pubsub connectors work

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

Google Pubsub

Integration surface
REST and gRPC (Cloud Pub/Sub API v1)
Authentication
Google Cloud IAM via OAuth 2.0 / service-account credentials (JSON key or workload identity); requires roles such as pubsub.publisher and pubsub.subscriber
Change detection
Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST; no modified-date polling
Capabilities
read · write · webhooks
Rate limits
Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key
How it works

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

    Choose tables

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

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

Popular · 4 of 351
All Google Cloud Platform integrations All Google Pubsub 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