Skip to content
Database ⇄ Developer tools

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

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

Keep Firebase and Google Pubsub in step: the rows in your database and the Message attributes, Dead-letter topics, Ordering keys, Topics your engineering tools track stay consistent in real time, in both directions.

Firebase is where your application's durable data lives; Google Pubsub is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.

Stacksync syncs Cloud Functions Triggers, Firestore Collections, Firestore Documents, Subcollections in Firebase with Message attributes, Dead-letter topics, Ordering keys, Topics in Google Pubsub field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set, so the database and the tooling around it never drift apart.

Common use cases

  • 01 Write CRM-side changes (plan, status, owner) back into Firestore documents the app reads.
  • 02 Combine Firebase Authentication users with billing and CRM records into one customer table.
  • 03 Bridge order or billing events off a topic into an ERP or ticketing system as they arrive, mapping message attributes to target fields.
  • 04 Attach an Avro or Protocol Buffer schema to a topic so every message Stacksync publishes is validated against an agreed contract.

Common sync patterns

Turn rows into the records your tools track

A new or changed row in Firebase creates or updates the matching record in Google Pubsub, whether that is an issue, an event, a message, or a user, so the tool reflects the database without a custom API job.

Land tool activity as queryable rows

Records and events from Google Pubsub arrive in Firebase as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.

One integration pattern instead of per-tool API code

Read and write the synced tables in Firebase and Stacksync keeps Google Pubsub current, replacing the auth, webhooks, rate limits, and retry logic you would otherwise maintain for each tool.

What you can sync between Firebase 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.

Firebase objects Google Pubsub objects How this pairing syncs
Cloud Storage Objects Files referenced from documents; usually synced as metadata plus URLs. Snapshots Captured subscription state for seek/replay; lets already-acknowledged messages be redelivered from a point in time. Cloud Storage Objects is specific to Firebase and Snapshots to Google Pubsub — each maps to any object or custom field on the other side.
Cloud Functions Triggers Server-side hooks that fire on document changes and can push updates outward. Message attributes Up to 100 key-value pairs per message; carry routing metadata and drive subscription filter expressions. Cloud Functions Triggers is specific to Firebase and Message attributes to Google Pubsub — each maps to any object or custom field on the other side.
Firestore Collections Top-level groupings of documents that a sync maps to tables or SaaS objects. Dead-letter topics Destination for messages that exceed a subscription's max delivery attempts; isolates poison messages for later handling. Firestore Collections is specific to Firebase and Dead-letter topics to Google Pubsub — each maps to any object or custom field on the other side.
Firestore Documents Schemaless JSON-like records, the primary unit synced to and from external systems. 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 Firebase and Ordering keys to Google Pubsub — each maps to any object or custom field on the other side.
Subcollections Nested collections under documents, typically flattened into related tables during sync. Topics Named resource publishers send to; Stacksync publishes each record change as a message to a topic for downstream subscribers to consume. Subcollections is specific to Firebase and Topics to Google Pubsub — each maps to any object or custom field on the other side.
Realtime Database Nodes JSON tree paths in the older Realtime Database, synced by path. Subscriptions A stream of messages from one topic; Stacksync consumes here via StreamingPull or a push endpoint, acknowledging each message after a successful write. Realtime Database Nodes is specific to Firebase and Subscriptions to Google Pubsub — each maps to any object or custom field on the other side.

How changes propagate between Firebase 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.

Firebase Google Pubsub Interval-based propagation

DetectionStacksync polls Firebase for changes on an incremental schedule, reading only records changed since the previous pass. Real-time snapshot listeners on Firestore queries and Cloud Functions triggers on document changes.

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

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

Rate-limit considerations

  • Firebase: Subject to Firestore's documented operation quotas and per-document write throughput 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 Firebase ⇄ Google Pubsub

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Firebase ⇄ 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 Firebase and Google Pubsub.

How the Firebase and Google Pubsub connectors work

Firebase

Integration surface
REST and gRPC APIs, typically accessed through the Firebase Admin SDK
Authentication
Google service account credentials (IAM) for server-side access; Firebase Auth tokens for client contexts
Change detection
Real-time snapshot listeners on Firestore queries and Cloud Functions triggers on document changes
Capabilities
read · write
Rate limits
Subject to Firestore's documented operation quotas and per-document write throughput 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 Firebase 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 Firebase 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
    Firebase connected
    Google Pubsub connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Firebase 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 344 integrations available for Firebase and Google Pubsub.

Popular · 5 of 344
All Firebase 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