--- title: "Google Cloud Pub/Sub connector | Stacksync" description: "Google Cloud Pub/Sub integration guide: plan Messages, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/google-pubsub last_modified: 2026-09-15 --- Developer tools · Two-way sync platform # Google Cloud Pub/Sub integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your Google Cloud Pub/Sub workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Messages. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Topics** - **Subscriptions** - **Messages** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=google-pubsub) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Google Cloud Pub/Sub records to discuss. These Google Cloud Pub/Sub record examples help scope a technical review. They are not a list of verified Stacksync operations. Topics Identify this record type and the operation you need to review with Stacksync. Subscriptions Identify this record type and the operation you need to review with Stacksync. Messages Retain message ID, conversation/thread ID, channel, and sender identity. ### See 3 more record examples Schemas Identify this record type and the operation you need to review with Stacksync. Snapshots Identify this record type and the operation you need to review with Stacksync. Message attributes Identify this record type and the operation you need to review with Stacksync. Connection setup ## Google Cloud Pub/Sub connection requirements. Review Google Cloud Pub/Sub access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Google Cloud Pub/Sub account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Google Cloud Pub/Sub, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Google Cloud Pub/Sub integration. Define repository/project context, issue or change identity, and relationships to operational records. Moving metadata does not authorize a code change, build, or deployment. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Google Cloud Pub/Sub **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Retain message ID, conversation/thread ID, channel, and sender identity. Load related records in the right order Resolve conversation, participant, and customer context before associating messages. ### Mapping checks by record type #### Messages Confirm object support with Stacksync Identity Retain message ID, conversation/thread ID, channel, and sender identity. Fields to consider Source message ID · Thread reference · Delivery state · Timestamp · Related record ID Related records to resolve first Resolve conversation, participant, and customer context before associating messages. Test before going live Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Google Cloud Pub/Sub integration in four steps. A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. ### View the four setup tests and expected results 1. ### Confirm the intended Google Cloud Pub/Sub account and grant After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity. **Expected result:** The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure. 2. ### Test record matching for Messages Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. **Expected result:** A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. 3. ### Test the operation your workflow needs Review one Google Cloud Pub/Sub record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Google Cloud Pub/Sub integration. ### Diagnose record matching, delayed changes, and rejected operations A Google Cloud Pub/Sub record appears under the wrong destination record Retain message ID, conversation/thread ID, channel, and sender identity. Resolve conversation, participant, and customer context before associating messages. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Google Cloud Pub/Sub implementation’s change-detection method for Messages. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Google Cloud Pub/Sub object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Google Cloud Pub/Sub workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=google-pubsub) ## Google Cloud Pub/Sub integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## Google Cloud Pub/Sub connector FAQ ### How should I plan an integration with Google Cloud Pub/Sub? Define repository/project context, issue or change identity, and relationships to operational records. Moving metadata does not authorize a code change, build, or deployment. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Google Cloud Pub/Sub connector write changes back? Write-back support is not established for this connection. Review the Google Cloud Pub/Sub records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Google Cloud Pub/Sub data? Retain message ID, conversation/thread ID, channel, and sender identity. ### Which related records should I load first for Google Cloud Pub/Sub? Resolve conversation, participant, and customer context before associating messages. ### How do I validate Google Cloud Pub/Sub changes after the initial load? Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. ### What should I include when estimating Google Cloud Pub/Sub integration costs? Estimate the number of Messages records, the history to load, ongoing changes, and required environments. Include API access, the integration service, destination storage or processing, and the work to maintain mappings and recover from errors. Review current provider pricing against that workload, including any account or API upgrades. AI assistant ## Set up Google Cloud Pub/Sub from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Google Cloud Pub/Sub and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Google Cloud Pub/Sub. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Google Cloud Pub/Sub record changes.” - “Create a Genie that answers questions about our Google Cloud Pub/Sub data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Google Cloud Pub/Sub connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Google Cloud Pub/Sub and ServiceNow](https://www.stacksync.com/integrations/google-pubsub-and-servicenow) - [Google Cloud Pub/Sub and SQL Server](https://www.stacksync.com/integrations/google-pubsub-and-sql-server) - [Google Cloud Pub/Sub and Microsoft Teams](https://www.stacksync.com/integrations/google-pubsub-and-microsoft-teams) - [Google Cloud Pub/Sub and Smartsheet](https://www.stacksync.com/integrations/google-pubsub-and-smartsheet) - [Google Cloud Pub/Sub and Okta](https://www.stacksync.com/integrations/google-pubsub-and-okta) - [Auth0 and Google Cloud Pub/Sub](https://www.stacksync.com/integrations/auth0-and-google-pubsub) - [Amazon SES and Google Cloud Pub/Sub](https://www.stacksync.com/integrations/amazon-ses-and-google-pubsub) - [Elasticsearch and Google Cloud Pub/Sub](https://www.stacksync.com/integrations/elasticsearch-and-google-pubsub) ### Database · 12 - [Google Cloud Pub/Sub and Airtable](https://www.stacksync.com/integrations/airtable-and-google-pubsub) - [Google Cloud Pub/Sub and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-google-pubsub) - [Google Cloud Pub/Sub and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-google-pubsub) - [Google Cloud Pub/Sub and Firebase](https://www.stacksync.com/integrations/firebase-and-google-pubsub) - [Google Cloud Pub/Sub and InfluxDB](https://www.stacksync.com/integrations/google-pubsub-and-influxdb) - [Google Cloud Pub/Sub and MongoDB](https://www.stacksync.com/integrations/google-pubsub-and-mongodb) - [Google Cloud Pub/Sub and MySQL](https://www.stacksync.com/integrations/google-pubsub-and-mysql) - [Google Cloud Pub/Sub and Neo4j](https://www.stacksync.com/integrations/google-pubsub-and-neo4j) - [Google Cloud Pub/Sub and PostgreSQL](https://www.stacksync.com/integrations/google-pubsub-and-postgresql) - [Google Cloud Pub/Sub and SAP HANA](https://www.stacksync.com/integrations/google-pubsub-and-sap-hana) - [Google Cloud Pub/Sub and SQL Server](https://www.stacksync.com/integrations/google-pubsub-and-sql-server) - [Google Cloud Pub/Sub and Supabase](https://www.stacksync.com/integrations/google-pubsub-and-supabase) ### Data warehouse · 8 - [Google Cloud Pub/Sub and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-google-pubsub) - [Google Cloud Pub/Sub and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-google-pubsub) - [Google Cloud Pub/Sub and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-google-pubsub) - [Google Cloud Pub/Sub and BigQuery](https://www.stacksync.com/integrations/bigquery-and-google-pubsub) - [Google Cloud Pub/Sub and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-google-pubsub) - [Google Cloud Pub/Sub and Databricks](https://www.stacksync.com/integrations/databricks-and-google-pubsub) - [Google Cloud Pub/Sub and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-google-pubsub) - [Google Cloud Pub/Sub and Snowflake](https://www.stacksync.com/integrations/google-pubsub-and-snowflake) ### Business productivity · 29 - [Google Cloud Pub/Sub and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-google-pubsub) - [Google Cloud Pub/Sub and Asana](https://www.stacksync.com/integrations/asana-and-google-pubsub) - [Google Cloud Pub/Sub and Atlassian](https://www.stacksync.com/integrations/atlassian-and-google-pubsub) - [Google Cloud Pub/Sub and Braze](https://www.stacksync.com/integrations/braze-and-google-pubsub) - [Google Cloud Pub/Sub and Campfire](https://www.stacksync.com/integrations/campfire-and-google-pubsub) - [Google Cloud Pub/Sub and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-google-pubsub) - [Google Cloud Pub/Sub and Docusign](https://www.stacksync.com/integrations/docusign-and-google-pubsub) - [Google Cloud Pub/Sub and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-google-pubsub) - [Google Cloud Pub/Sub and Front](https://www.stacksync.com/integrations/front-and-google-pubsub) - [Google Cloud Pub/Sub and Gainsight](https://www.stacksync.com/integrations/gainsight-and-google-pubsub) - [Google Cloud Pub/Sub and GitHub](https://www.stacksync.com/integrations/github-and-google-pubsub) - [Google Cloud Pub/Sub and Google Sheets](https://www.stacksync.com/integrations/google-pubsub-and-google-sheets) - [Google Cloud Pub/Sub and Ironclad](https://www.stacksync.com/integrations/google-pubsub-and-ironclad) - [Google Cloud Pub/Sub and Klaviyo](https://www.stacksync.com/integrations/google-pubsub-and-klaviyo) - [Google Cloud Pub/Sub and Microsoft 365](https://www.stacksync.com/integrations/google-pubsub-and-microsoft-365) - [Google Cloud Pub/Sub and Microsoft Dynamics 365](https://www.stacksync.com/integrations/google-pubsub-and-microsoft-dynamics-365) - [Google Cloud Pub/Sub and Microsoft Teams](https://www.stacksync.com/integrations/google-pubsub-and-microsoft-teams) - [Google Cloud Pub/Sub and Monday](https://www.stacksync.com/integrations/google-pubsub-and-monday) - [Google Cloud Pub/Sub and Notion](https://www.stacksync.com/integrations/google-pubsub-and-notion) - [Google Cloud Pub/Sub and Quip](https://www.stacksync.com/integrations/google-pubsub-and-quip) - [Google Cloud Pub/Sub and SendGrid](https://www.stacksync.com/integrations/google-pubsub-and-sendgrid) - [Google Cloud Pub/Sub and ServiceMax](https://www.stacksync.com/integrations/google-pubsub-and-servicemax) - [Google Cloud Pub/Sub and ServiceNow](https://www.stacksync.com/integrations/google-pubsub-and-servicenow) - [Google Cloud Pub/Sub and Slack](https://www.stacksync.com/integrations/google-pubsub-and-slack) - [Google Cloud Pub/Sub and Smartsheet](https://www.stacksync.com/integrations/google-pubsub-and-smartsheet) - [Google Cloud Pub/Sub and SysAid](https://www.stacksync.com/integrations/google-pubsub-and-sysaid) - [Google Cloud Pub/Sub and Twilio](https://www.stacksync.com/integrations/google-pubsub-and-twilio) - [Google Cloud Pub/Sub and Wrike](https://www.stacksync.com/integrations/google-pubsub-and-wrike) - [Google Cloud Pub/Sub and Zendesk](https://www.stacksync.com/integrations/google-pubsub-and-zendesk) ### Analytics · 2 - [Google Cloud Pub/Sub and Pendo](https://www.stacksync.com/integrations/google-pubsub-and-pendo) - [Google Cloud Pub/Sub and Splunk](https://www.stacksync.com/integrations/google-pubsub-and-splunk) ### Communications · 5 - [Google Cloud Pub/Sub and Aircall](https://www.stacksync.com/integrations/aircall-and-google-pubsub) - [Google Cloud Pub/Sub and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-google-pubsub) - [Google Cloud Pub/Sub and Infobip](https://www.stacksync.com/integrations/google-pubsub-and-infobip) - [Google Cloud Pub/Sub and RingCentral](https://www.stacksync.com/integrations/google-pubsub-and-ringcentral) - [Google Cloud Pub/Sub and Zoom](https://www.stacksync.com/integrations/google-pubsub-and-zoom) ### Security and identity · 6 - [Google Cloud Pub/Sub and Active Directory](https://www.stacksync.com/integrations/active-directory-and-google-pubsub) - [Google Cloud Pub/Sub and Auth0](https://www.stacksync.com/integrations/auth0-and-google-pubsub) - [Google Cloud Pub/Sub and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-google-pubsub) - [Google Cloud Pub/Sub and JumpCloud](https://www.stacksync.com/integrations/google-pubsub-and-jumpcloud) - [Google Cloud Pub/Sub and Okta](https://www.stacksync.com/integrations/google-pubsub-and-okta) - [Google Cloud Pub/Sub and OneLogin](https://www.stacksync.com/integrations/google-pubsub-and-onelogin) ### Storage · 4 - [Google Cloud Pub/Sub and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-google-pubsub) - [Google Cloud Pub/Sub and Box](https://www.stacksync.com/integrations/box-and-google-pubsub) - [Google Cloud Pub/Sub and Egnyte](https://www.stacksync.com/integrations/egnyte-and-google-pubsub) - [Google Cloud Pub/Sub and SharePoint](https://www.stacksync.com/integrations/google-pubsub-and-sharepoint) 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](https://www.stacksync.com/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](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)