---
schema_version: "1"
id: f948fb75b386be6deccb62c2553ed12fde86971e216a51ccee6e9a67370e020d
title: Google Pub/Sub Connector 1.3
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/google-pubsub-connector/latest/index.md
canonical_url: https://docs.mulesoft.com/google-pubsub-connector/latest/
source_site: docs.mulesoft.com
content_type: documentation
content_hash: f3d7303a30a492658608bc8e13dc7d24ab39645702e38f3dee990f8b6b04340a
description: MuleSoft Documentation Site
release: "1.3"
latest: true
---
---
product: Google Pub/Sub Connector
version: 1.3
is-latest-version: true
---

# Google Pub/Sub Connector 1.3

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Google Pub/Sub (Google Pub/Sub Connector) enables you to access the Google
Pub/Sub messaging platform. This connector exposes operations provided by the Google Pub/Sub client
libraries.

For compatibility information and fixed issues, refer to the Google Pub/Sub Connector Release Notes.

## Before You Begin

To use this connector, you must be familiar with:

- The Google Pub/Sub API

- Anypoint Connectors

- Mule runtime engine (Mule)

- Elements and global elements in a Mule flow

- Creating a Mule app using Anypoint Studio or Anypoint Code Builder

Before creating an app, you must have:

- Credentials to access the target resource

- Anypoint Studio or Anypoint Code Builder

## Common Use Cases for the Connector

Some common use cases for Google Pub/Sub Connector include:

- Publishing messages

- Listening to messages

- Managing snapshots

- Replaying messages

## Authentication Types

Google Pub/Sub Connector uses the PubSub Connection authentication method, in which you create a
service account and obtain credentials. For more information, refer to
[Google Cloud Service Accounts](https://docs.cloud.google.com/iam/docs/service-account-overview).

For **Workload Identity Federation with MuleSoft IdP**, you can set **Token Endpoint** so the same
app can request tokens from the US or EU1 control plane. If you leave **Token Endpoint** blank, the
connector uses the US token endpoint. For field details, see
[Wif MuleSoft Idp Config](https://docs.mulesoft.com/google-pubsub-connector/latest/google-pubsub-connector-reference#WifMuleSoftIdpConfig).

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange)

- [Google Pub/Sub Connector Reference](https://docs.mulesoft.com/google-pubsub-connector/latest/google-pubsub-connector-reference)

- [Salesforce Help](https://help.salesforce.com)