Real-time
Two-way sync
Changes in Google Pubsub or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Developer tools ⇄ Business productivity
Google Pubsub to Servicemax integration — real-time, two-way sync
Keep Google Pubsub and Servicemax 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 Pubsub and Servicemax
Connect the tickets, records, and events in Servicemax to the systems engineering runs in Google Pubsub, kept current in real time and in both directions.
Servicemax 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 Products, Work Orders, Work Details, Installed Products in Servicemax 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 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 Consolidate Service Contracts and entitlement data into a warehouse for renewal forecasting and SLA compliance dashboards.
- 02 Mirror Accounts and Contacts between ServiceMax and the CRM system of record so customer and site data stays consistent.
- 03 Publish new and changed database rows as messages to a Pub/Sub topic so multiple downstream subscriptions consume the change stream independently.
- 04 Consume messages from a subscription via StreamingPull and write them into a Postgres or warehouse table for durable, SQL-queryable storage.
Common sync patterns
Where Google Pubsub moves messages between services: activity lands on the stream
Records created or changed in Servicemax publish to the queue or topic in Google Pubsub as they happen, so downstream services react to real events rather than polling for them.
Where Google Pubsub is the directory or identity source: one set of users
People and accounts in Servicemax 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 Servicemax replicate into Google Pubsub, so the operational view reflects what is actually happening in the business.
What you can sync between Google Pubsub and Servicemax
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 Pubsub objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Dead-letter topics Destination for messages that exceed a subscription's max delivery attempts; isolates poison messages for later handling. | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Dead-letter topics is specific to Google Pubsub and Stock History to Servicemax — each maps to any object or custom field on the other side. | |
| 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. | Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. | Ordering keys is specific to Google Pubsub and Accounts to Servicemax — each maps to any object or custom field on the other side. | |
| Topics Named resource publishers send to; Stacksync publishes each record change as a message to a topic for downstream subscribers to consume. | Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. | Topics is specific to Google Pubsub and Contacts to Servicemax — each maps to any object or custom field on the other side. | |
| Subscriptions A stream of messages from one topic; Stacksync consumes here via StreamingPull or a push endpoint, acknowledging each message after a successful write. | Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. | Subscriptions is specific to Google Pubsub and Cases to Servicemax — each maps to any object or custom field on the other side. | |
| Messages The synced unit: base64-encoded data plus attributes, ordering key, messageId and publishTime; capped at 10 MB each. | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Messages is specific to Google Pubsub and Products to Servicemax — each maps to any object or custom field on the other side. | |
| Schemas Avro or Protocol Buffer definitions bound to a topic; validate that every published message matches the agreed structure. | Work Orders SVMXC__Service_Order__c; the core field-service job record for install, repair, and maintenance; synced two-way with databases and pushed to ERPs at close. | Schemas is specific to Google Pubsub and Work Orders to Servicemax — each maps to any object or custom field on the other side. |
How changes propagate between Google Pubsub and Servicemax
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 Pubsub Servicemax 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 Servicemax through its API, with automatic retries and rate-limit backoff.
Servicemax Google Pubsub Sub-second propagation
DetectionChanges in Servicemax are captured at the source via change data capture — no polling loop against its API. Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object.
DeliveryEach detected change is written to Google Pubsub through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- 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.
- Servicemax: Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count.
What ships with Google Pubsub ⇄ Servicemax
Connect Google Pubsub and Servicemax for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Pubsub–Servicemax connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Google Pubsub or Servicemax 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 or Servicemax record.
Observability
Monitoring
Track your Google Pubsub ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Google Pubsub and Servicemax.
How the Google Pubsub and Servicemax connectors work
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
Servicemax
- Integration surface
- Salesforce REST, SOAP, and Bulk APIs (ServiceMax is a managed package on the Salesforce platform)
- Authentication
- Salesforce OAuth login via a user with API access; the connecting profile needs object and field permissions on ServiceMax's SVMXC__ objects
- Change detection
- Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled
- Capabilities
- read · write · CDC
- Rate limits
- Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count
How it works
How to connect Google Pubsub to Servicemax — 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.
- 01
Connect your apps
Authenticate Google Pubsub and Servicemax with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Google Pubsub
connected
Servicemax
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Google Pubsub and Servicemax 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.
objects · Google Pubsub ⇄ ServicemaxCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Google Pubsub ServicemaxCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Google Pubsub and Servicemax integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Google Pubsub and Servicemax: authenticate both systems, choose the objects to sync (such as Google Pubsub's Dead-letter topics and Ordering keys), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Google Pubsub and Servicemax records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Google Pubsub and Servicemax connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Google Pubsub–Servicemax integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Google Pubsub and Servicemax. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Google Pubsub: 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. On Servicemax: Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Servicemax side: Products, Work Orders, Work Details, Installed Products, plus custom fields where Servicemax exposes them. On the Google Pubsub side: Topics, Subscriptions, Messages, Schemas. Stacksync auto-detects both schemas and converts types between the two systems.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 323 integrations available for Google Pubsub and Servicemax.
Popular · 5 of 323
-
Google Pubsub ⇄ Microsoft Teams -
Servicemax ⇄ Microsoft Graph -
Servicemax ⇄ Jms -
Servicemax ⇄ Newrelic -
Servicemax ⇄ Opsgenie
No integrations match .
