Skip to content
Developer tools ⇄ Business productivity

Google Pubsub to Microsoft Dynamics 365 integration — real-time, two-way sync

Keep Google Pubsub and Microsoft Dynamics 365 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 Microsoft Dynamics 365

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

Microsoft Dynamics 365 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 Activities, Custom Tables, Accounts, Contacts in Microsoft Dynamics 365 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 Keep opportunities and orders consistent with the ERP or billing system without manual re-entry.
  • 02 Sync cases with external ticketing or product systems so support works one queue.
  • 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 tracks engineering work: requests become issues

A ticket or request raised in Microsoft Dynamics 365 opens or updates a matching issue in Google Pubsub, and status, comments, and resolution flow back, so support and engineering work the same item instead of retyping it.

Where Google Pubsub moves messages between services: activity lands on the stream

Records created or changed in Microsoft Dynamics 365 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 Microsoft Dynamics 365 stay matched to the users in Google Pubsub, so access, provisioning, and org changes propagate instead of being keyed in twice.

What you can sync between Google Pubsub and Microsoft Dynamics 365

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 Microsoft Dynamics 365 objects How this pairing syncs
Messages The synced unit: base64-encoded data plus attributes, ordering key, messageId and publishTime; capped at 10 MB each. Products Catalog records aligned with ERP item masters. Messages is specific to Google Pubsub and Products to Microsoft Dynamics 365 — 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. Activities Emails, calls, and tasks captured for engagement analytics. Schemas is specific to Google Pubsub and Activities to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Snapshots Captured subscription state for seek/replay; lets already-acknowledged messages be redelivered from a point in time. Custom Tables Dataverse tables that carry business-specific entities through the same API surface. Snapshots is specific to Google Pubsub and Custom Tables to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Message attributes Up to 100 key-value pairs per message; carry routing metadata and drive subscription filter expressions. Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. Message attributes is specific to Google Pubsub and Accounts to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Dead-letter topics Destination for messages that exceed a subscription's max delivery attempts; isolates poison messages for later handling. Contacts Person records kept consistent with marketing, support, and data-warehouse copies. Dead-letter topics is specific to Google Pubsub and Contacts to Microsoft Dynamics 365 — 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. Leads Inbound records enriched and routed from external sources into sales queues. Ordering keys is specific to Google Pubsub and Leads to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.

How changes propagate between Google Pubsub and Microsoft Dynamics 365

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 Microsoft Dynamics 365 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 Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.

Microsoft Dynamics 365 Google Pubsub Sub-second propagation

DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.

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.
What ships with Google Pubsub ⇄ Microsoft Dynamics 365

Connect Google Pubsub and Microsoft Dynamics 365 for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Google Pubsub ⇄ Microsoft Dynamics 365 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 Microsoft Dynamics 365.

How the Google Pubsub and Microsoft Dynamics 365 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

Microsoft Dynamics 365

Integration surface
REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
Authentication
Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities)
Change detection
Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties
Capabilities
read · write · CDC · webhooks
Microsoft Dynamics 365 setup guide
How it works

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

    Choose tables

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

Google Pubsub and Microsoft Dynamics 365 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 325 integrations available for Google Pubsub and Microsoft Dynamics 365.

Popular · 7 of 325
All Google Pubsub integrations All Microsoft Dynamics 365 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