- Home
- Resources
- Integrations
- Google Cloud Pub/Sub
Google Cloud Pub/Sub Make integrationAutomate Google Cloud Pub/Sub with Make.
Can a message landing in Pub/Sub start a workflow on its own? The Google Cloud Pub/Sub Make integration gives you 12 modules: 1 instant trigger, 7 actions and 4 searches. It suits teams already on Google Cloud, and this page walks you from connection to a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Google Cloud Pub/Sub Make integration do?
The Google Cloud Pub/Sub Make integration links your Google Cloud project to Make, a visual tool where you build a scenario (the automation itself: a chain of modules). Each module is one brick of that chain, and here the bricks can listen to a topic, publish messages and manage topics and subscriptions for you.
Turn topic messages into actions elsewhere. Watch Messages fires the moment a message is published on the topic you subscribe to. From there, Make hands the message to the next module, so an event emitted by your backend can end up as a row, an email or a ticket in another tool without extra code.
Feed Pub/Sub from tools that cannot talk to it. Publish Messages sends a message to a topic by its name. Put it after a form, a CRM or a spreadsheet module and your services receive events from apps that have no Pub/Sub client of their own.
Keep the plumbing tidy. Create a Topic, Create a Subscription and their Update and Delete siblings let a scenario set up or clean up resources, while List Topics and List Subscriptions give you an inventory to review.
The modules do not cover every Pub/Sub API endpoint; Make an API Call fills that gap with the same connection. The documentation also warns that it was AI-generated from Google material, so double-check anything critical against Google. If you are weighing tools, read n8n vs Make, and when a run fails, Make troubleshooting lists the usual fixes. For a structured path, see Make training.
How do you connect Google Cloud Pub/Sub to Make?
- 01
Prepare Google Cloud
You need an active Google Cloud account with Pub/Sub enabled. For a custom connection, open the Google Cloud Console, pick your project, go to APIs and Services, then Credentials, and create an OAuth client ID. Keep the Client ID and Client secret at hand.
- 02
Add a module and create the connection
In your scenario, add any Google Cloud Pub/Sub module and click Create a connection. A connection is your Google account linked to Make once, then reused by every Pub/Sub module. The Connection name field is optional but helps when you juggle several projects.
- 03
Authorize and confirm
Paste the credentials you copied, or follow the instructions Make shows on screen. If Google asks for a callback URI while you set up the OAuth client, use
https://www.integromat.com/oauth/cb/google-cloud-pubsub. Once saved, Make can read your topics and subscriptions.
Your first scenario with Google Cloud Pub/Sub
GoalWhen a message is published on your orders topic, Make forwards it to a separate alerts topic that another service reads.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the big +. Search for Google Cloud Pub/Sub and pick Watch Messages as the first module.
- 02
Set up the webhook
Click Create a webhook, then Create a connection and authorize your Google account. Point the trigger at the topic whose messages should start the scenario.
- 03
Add Publish Messages
Click the + on the right of the trigger and add Publish Messages. Choose the alerts topic and map the content received by Watch Messages into the message. Use a different topic from the watched one.
- 04
Test with Run once
Click Run once, then publish a test message on the watched topic. Each module shows the bundles it received, one bundle per message, so you can check what reached the alerts topic.
- 05
Switch it on
When the test looks right, switch the scenario on. Being instant, it runs whenever a message arrives rather than waiting for the default 15 minute schedule that polling scenarios use.
What can start a Google Cloud Pub/Sub scenario?
1 module starts a scenario when something happens in Google Cloud Pub/Sub. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Google Cloud Pub/Sub as soon as it happens.
Watch Messages
Instant triggerIn Make“Triggers by messages published by the subscribed topic.”
You get a scenario that springs to life every time a message is published on the topic you subscribed to, carrying that message into the next module as a bundle.
What can Make do in Google Cloud Pub/Sub?
Google Cloud Pub/Sub gives you 11 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Modules index
Create a Subscription
ActionIn Make“Creates a new subscription.”
This gives a topic a new listener: the subscription is what lets a consumer, Make included, receive the messages published on that topic.
Create a Topic
ActionIn Make“Creates a new topic.”
You end up with a fresh topic, the named channel your services publish to and subscribe from, created straight from a scenario instead of the Console.
Delete a Subscription
ActionIn Make“Removes a subscription by its name. All messages retained in the subscription are immediately dropped.”
This removes a subscription by its name, which is how you retire a consumer that no longer needs the topic's messages.
Delete a Topic
ActionIn Make“Removes a topic by its name.”
You get rid of a topic by name, keeping your project free of channels nobody publishes to anymore.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
This one reaches any Pub/Sub API endpoint the other modules leave out, reusing the connection you already created, so no second login is needed.
Update a Subscription
ActionIn Make“Updates a subscription by its name.”
You change an existing subscription, found by its name, without deleting it and losing the messages it still holds.
Update a Topic
ActionIn Make“Updates a topic by its name.”
This edits a topic in place, located by its name, so publishers and subscribers keep working with the same channel.
List Subscriptions
SearchIn Make“Retrieves a list of subscriptions.”
You receive the subscriptions of your project, each one as its own bundle, ready to be logged, filtered or passed to another module.
List Topics
SearchIn Make“Retrieves a list of topics.”
This returns the topics of your project one bundle at a time, the starting point for any audit of what your services publish.
List Topic Subscriptions
SearchIn Make“Retrieves a list of subscriptions by the topic name.”
You see who listens to one given topic: the module retrieves the subscriptions attached to the topic name you enter.
Publish Messages
SearchIn Make“Publishes messages by the topic name.”
Your scenario becomes a publisher: it sends messages to a topic by name, and every subscription on that topic receives them.
Need help automating Google Cloud Pub/Sub with Make?
A person reads every message.