Skip to content
Developer tools

Connect Google Pubsub to any app with two-way sync.

Two-way sync Google Pubsub across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in Google Pubsub.

These objects sync between Google Pubsub and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Google Pubsub exposes them.

Topics
Named resource publishers send to; Stacksync publishes each record change as a message to a topic for downstream subscribers to consume.
Subscriptions
A stream of messages from one topic; Stacksync consumes here via StreamingPull or a push endpoint, acknowledging each message after a successful write.
Messages
The synced unit: base64-encoded data plus attributes, ordering key, messageId and publishTime; capped at 10 MB each.
Schemas
Avro or Protocol Buffer definitions bound to a topic; validate that every published message matches the agreed structure.
Snapshots
Captured subscription state for seek/replay; lets already-acknowledged messages be redelivered from a point in time.
Message attributes
Up to 100 key-value pairs per message; carry routing metadata and drive subscription filter expressions.
Dead-letter topics
Destination for messages that exceed a subscription's max delivery attempts; isolates poison messages for later handling.
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.
API surface

How Stacksync connects to Google Pubsub.

The connector runs on Google Pubsub's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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
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

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
What ships with Google Pubsub

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

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

Real-time

Two-way sync

Changes in Google Pubsub instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever 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 Pubsub record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Google Pubsub connector.

Google Cloud Pub/Sub is the asynchronous messaging backbone on Google Cloud, owned by platform, data, and backend engineering teams. It is a system of engagement and event bus rather than a system of record: publishers send order events, clickstream and IoT telemetry, database change events, and service-to-service messages to topics, and any number of subscriptions consume them independently. Data is in-flight and transient, retained seven days by default (up to 31), so it decouples producers from consumers rather than storing state long term.

  • Platform engineering
  • Data engineering
  • Backend application engineers
  • DevOps / SRE
  • Cloud architects

  1. Publish new and changed database rows as messages to a Pub/Sub topic so multiple downstream subscriptions consume the change stream independently.

  2. Consume messages from a subscription via StreamingPull and write them into a Postgres or warehouse table for durable, SQL-queryable storage.

  3. Fan out CRM record changes to a topic and let billing, analytics, and notification subscriptions each react without coupling to the source.

  4. Bridge order or billing events off a topic into an ERP or ticketing system as they arrive, mapping message attributes to target fields.

  5. Attach an Avro or Protocol Buffer schema to a topic so every message Stacksync publishes is validated against an agreed contract.

  6. One-way out: Stacksync reads new and changed rows from a database or a CRM such as Salesforce and publishes them as messages to a Pub/Sub topic, so downstream subscriptions consume the change stream without touching the source system directly.

All Google Pubsub integrations

Pick the system you need to keep in sync with Google Pubsub. Each page covers the sync setup, field mapping, and common workflows for that pair.

Database · 12

Data warehouse · 8

Business productivity · 29

How it works

Set up Google Pubsub in minutes, without APIs.

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 Pubsub with its 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 Pubsub connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Google Pubsub objects to sync — Stacksync auto-detects the schema, 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 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 Pubsub database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Google Pubsub connector FAQ

What can I sync with the Google Pubsub connector?

Google Pubsub's core objects — Topics, Subscriptions, Messages, Schemas and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Google Pubsub?

Via REST and gRPC (Cloud Pub/Sub API v1), authenticated with Google Cloud IAM via OAuth 2.0 / service-account credentials (JSON key or workload identity); requires roles such as pubsub.publisher and pubsub.subscriber. Changes are detected as follows — 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. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Google Pubsub connector two-way?

Yes. Changes made in Google Pubsub propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Google Pubsub integration take to set up?

Most Google Pubsub integrations go live in minutes: authenticate Google Pubsub and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Google Pubsub data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Google Pubsub data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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
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