Skip to content
Business productivity ⇄ Developer tools

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

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

Connect the tickets, records, and events in Campfire to the systems engineering runs in Google Pubsub, kept current in real time and in both directions.

Campfire is where customer-facing and operational work happens: the tickets, conversations, contacts, and records a team touches every day. Google Pubsub is where engineering runs the systems behind that work — the issue trackers, message brokers, directories, and monitors that keep services moving. The same items, people, and events matter to both, and when the only link between them is a manual hand-off or an overnight export, each side acts on a stale copy of what the other already knows.

Stacksync syncs Bill, Debit Memo, Invoice, Credit Memo in Campfire with Messages, Schemas, Snapshots, Message attributes in Google Pubsub field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync maps the overlap, resolves conflicts by rules you set, and keeps every copy current, with no middleware to build and no API limits to babysit.

Common use cases

  • 01 Route inbound lead or form submissions into the right room via a bot.
  • 02 Send scheduled digest messages built from synced database queries.
  • 03 Attach an Avro or Protocol Buffer schema to a topic so every message Stacksync publishes is validated against an agreed contract.
  • 04 Publish new and changed database rows as messages to a Pub/Sub topic so multiple downstream subscriptions consume the change stream independently.

Common sync patterns

Where Google Pubsub is the directory or identity source: one set of users

People and accounts in Campfire stay matched to the users in Google Pubsub, so access, provisioning, and org changes propagate instead of being keyed in twice.

Where Google Pubsub watches operations: live volumes for visibility

Open items, throughput, and error counts from Campfire replicate into Google Pubsub, so the operational view reflects what is actually happening in the business.

One shared record across both systems

Where both systems keep records for the same contacts, items, or users, a correction in either updates the other, ending dual maintenance and keeping IDs aligned for every other flow.

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

Campfire objects Google Pubsub objects How this pairing syncs
Invoice Synced with incremental and full sync per the Stacksync docs. 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. Invoice is specific to Campfire and Ordering keys to Google Pubsub — each maps to any object or custom field on the other side.
Credit Memo Synced with incremental and full sync per the Stacksync docs. Topics Named resource publishers send to; Stacksync publishes each record change as a message to a topic for downstream subscribers to consume. Credit Memo is specific to Campfire and Topics to Google Pubsub — each maps to any object or custom field on the other side.
Bank Account Synced with incremental and full sync per the Stacksync docs. Subscriptions A stream of messages from one topic; Stacksync consumes here via StreamingPull or a push endpoint, acknowledging each message after a successful write. Bank Account is specific to Campfire and Subscriptions to Google Pubsub — each maps to any object or custom field on the other side.
Bank Transaction Synced with incremental and full sync per the Stacksync docs. Messages The synced unit: base64-encoded data plus attributes, ordering key, messageId and publishTime; capped at 10 MB each. Bank Transaction is specific to Campfire and Messages to Google Pubsub — each maps to any object or custom field on the other side.
Journal Entry Synced with incremental and full sync per the Stacksync docs. Schemas Avro or Protocol Buffer definitions bound to a topic; validate that every published message matches the agreed structure. Journal Entry is specific to Campfire and Schemas to Google Pubsub — each maps to any object or custom field on the other side.
Intercompany Journal Entry Synced with incremental and full sync per the Stacksync docs. Snapshots Captured subscription state for seek/replay; lets already-acknowledged messages be redelivered from a point in time. Intercompany Journal Entry is specific to Campfire and Snapshots to Google Pubsub — each maps to any object or custom field on the other side.

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

Campfire Google Pubsub Sub-second propagation

DetectionCampfire pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking (incremental sync).

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

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

Rate-limit considerations

  • Campfire: Limits depend on the self-hosted deployment; confirm against the instance's documentation.
  • 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 Campfire ⇄ Google Pubsub

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Campfire and Google Pubsub connectors work

Campfire

Integration surface
HTTP endpoints for bot integrations on a self-hosted instance
Authentication
API key — create an API user with a Super User Role in Campfire (Settings -> API Keys), generate an API Key secret, and provide it in the Stacksync connection setup
Change detection
Near real-time updates via change tracking (incremental sync); delete detection per object (some objects detected every 24h)
Capabilities
read · write · CDC · webhooks
Rate limits
Limits depend on the self-hosted deployment; confirm against the instance's documentation.
Campfire setup guide

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

    Choose tables

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

Campfire 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 304 integrations available for Campfire and Google Pubsub.

Popular · 8 of 304
All Campfire 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