Resources · Make integration

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 you can automate

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.

Connect

How do you connect Google Cloud Pub/Sub to Make?

  1. 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.

  2. 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.

  3. 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.

First scenario

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Triggers

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.

Google Cloud Pub/Sub1Watch Messages

Watch Messages

Instant trigger

In MakeTriggers 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.

How it fires
instant, Google Cloud Pub/Sub calls Make through a webhook as soon as the message is published, so there is no polling interval to wait for.
When to use it
your backend already emits events such as a new order or a failed job, and you want a no-code reaction in another app.
Watch out
create the webhook before the connection, and never publish back to the same topic from this scenario, or each run triggers the next one.
Modules

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.

Google Cloud Pub/Sub1

Create a Subscription

Action

In MakeCreates 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.

When to use it
a scenario provisions a new environment or client and each one needs its own subscription on an existing topic.
Watch out
run it with Run once before activating, since every run adds another subscription.
Google Cloud Pub/Sub2

Create a Topic

Action

In MakeCreates 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.

When to use it
onboarding a new product line or customer where the convention is one topic each, triggered by the record that announces it.
Watch out
chain Create a Subscription right after if a service has to read this channel from day one.
Google Cloud Pub/Sub3

Delete a Subscription

Action

In MakeRemoves 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.

When to use it
offboarding a client or shutting down a test environment whose listener should disappear with it.
Watch out
every message still held in that subscription is dropped immediately, with no way back, so drain or check it first.
Google Cloud Pub/Sub4

Delete a Topic

Action

In MakeRemoves a topic by its name.

You get rid of a topic by name, keeping your project free of channels nobody publishes to anymore.

When to use it
the closing step of a cleanup scenario, after List Topics has shown you which channels belong to a retired project.
Watch out
add a filter on the topic name before this module, so the run only removes the channels List Topics flagged.
Google Cloud Pub/Sub5

Make an API Call

Action

In MakePerforms 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.

When to use it
you need an operation the 12 listed modules do not offer and you know which endpoint the Google documentation points to.
Watch out
you write the request yourself, so read the Google API reference rather than guessing paths or payloads.
Google Cloud Pub/Sub6

Update a Subscription

Action

In MakeUpdates a subscription by its name.

You change an existing subscription, found by its name, without deleting it and losing the messages it still holds.

When to use it
a consumer's settings must evolve after a deployment, and recreating the subscription would throw away the backlog.
Watch out
the name must match exactly; pull it from List Subscriptions instead of typing it by hand to avoid a failed operation.
Google Cloud Pub/Sub7

Update a Topic

Action

In MakeUpdates 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.

When to use it
a governance scenario aligns topic settings across projects after a policy change, topic by topic.
Watch out
pair it with List Topics and a filter, otherwise one run may touch channels you meant to leave alone.
Google Cloud Pub/Sub8

List Subscriptions

Search

In MakeRetrieves 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.

When to use it
building an inventory sheet, or spotting listeners that a cleanup scenario should update or remove.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle, which adds operations.
Google Cloud Pub/Sub9

List Topics

Search

In MakeRetrieves 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.

When to use it
before a bulk update or deletion, to see exactly which channels exist and pick the right ones with a filter.
Watch out
an empty project gives zero bundles, so the rest of the scenario simply does not run.
Google Cloud Pub/Sub10

List Topic Subscriptions

Search

In MakeRetrieves 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.

When to use it
before deleting a topic, to check which consumers would lose their feed, or to document one data flow.
Watch out
unlike List Subscriptions, it only looks at one topic, so a typo in the name returns nothing.
Google Cloud Pub/Sub11

Publish Messages

Search

In MakePublishes 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.

When to use it
a form submission, a paid invoice or a CRM update should reach services that already consume Pub/Sub.
Watch out
Make lists it as a search, not an action, so read its output bundles during Run once before mapping them further.
Need help

Need help automating Google Cloud Pub/Sub with Make?

A person reads every message.

FAQ

Google Cloud Pub/Sub and Make: frequent questions

01Is the Google Cloud Pub/Sub Make integration free?
Yes, on the Make side: Google Cloud Pub/Sub is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits, one operation being one module run on one bundle. Your Pub/Sub subscription itself is a Google matter: the Google Cloud Pub/Sub pricing page covers it.
02What do you need to connect Google Cloud Pub/Sub to Make?
An active Google Cloud account with Pub/Sub enabled and the right OAuth authorization. In Make, add a Pub/Sub module, click Create a connection, optionally name it, then enter your credentials or follow the on-screen steps. For your own OAuth client, create an OAuth client ID under APIs and Services, Credentials in the Google Cloud Console, and copy the Client ID and Client secret. For the Watch Messages trigger, click Create a webhook before creating the connection.
03Does the Google Cloud Pub/Sub trigger in Make react in real time?
Yes. Watch Messages is an instant trigger: Google Cloud Pub/Sub calls Make through a webhook as soon as a message is published on the subscribed topic, so the scenario does not wait for the 15 minute default schedule. It is the only trigger of the app. Every other module is an action or a search that runs after it, or after a trigger from another app, or on a schedule you set on the first module.
04What if the Google Cloud Pub/Sub module you need is missing in Make?
Use Make an API Call. It sends any authorized request to the Pub/Sub API with the connection you already have, so an endpoint missing from the 12 modules is still reachable. You build the request from the Google API reference. Keep in mind that the Make documentation for this app states it was AI-generated from Google's material and may contain mistakes, so confirm important details with Google Cloud Pub/Sub directly.
05Should you use Make or n8n for Google Cloud Pub/Sub?
It depends on the tool your team already uses. Many apps also have an n8n node, so check the n8n side for Pub/Sub before comparing. In Make you get 12 ready modules including an instant trigger, plus Make an API Call for the rest, all built visually. Compare how each tool fits your existing scenarios and skills before deciding, and read the n8n vs Make comparison linked above for the full criteria.