Resources · Make integration

Firebase Cloud Messaging Make integrationAutomate Firebase Cloud Messaging with Make.

What if your app users got a push notification when something happens in another tool? The Firebase Cloud Messaging Make integration gives you 1 action, Send a Message. This page shows product and ops teams how to connect a Firebase project and wire that action into a first working flow.

Try the Firebase Cloud Messaging integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Firebase Cloud Messaging Make integration do?

It lets Make push a message to the devices of your app users without writing a line of backend code. You build a scenario, the automation you assemble in Make, and its last step is the Send a Message module, which delivers the notification to the devices you point it at.

Order updates that reach the phone. A shop app can start its scenario with the trigger of the e-commerce tool it already uses, then hand the order data to Send a Message so the buyer sees a notification about their purchase.

Form replies turned into alerts. When a lead fills in a form, a team app can ping the sales rep on mobile. The 123FormBuilder Make integration is one way to start that flow.

Scheduled reminders. With no trigger at all, a scenario can simply run on the clock Make puts on its first module and send a reminder to a group of devices each time it runs.

Keep the scope in mind: the app has a single module, no trigger and no Make an API Call module, so Make only sends, it never reads anything back from Firebase. If you are still weighing tools, the n8n vs Make comparison lays out the differences, and the Make training covers scenario building from scratch.

Connect

How do you connect Firebase Cloud Messaging to Make?

  1. 01

    Prepare your Firebase project

    You need an active Firebase project and credentials allowed to use the Cloud Messaging API. In the Google Cloud console, open APIs & Services, then Credentials, click Create credentials and choose OAuth client ID. Copy the Client ID and the Client secret it shows.

  2. 02

    Add the module and open the connection

    In Make, add Send a Message to your scenario and click Create a connection. A connection is your Firebase account linked to Make once, then reused by every module of the app. You can type a label in Connection name if you plan to have several.

  3. 03

    Paste your credentials

    Enter the Client ID and Client secret you copied, or follow the instructions on screen. Once saved, the connection appears in the module and you can move on to the message fields.

First scenario

Your first scenario with Firebase Cloud Messaging

GoalWhen a new order lands in your shop tool, Make pushes a notification to the buyer's devices through Firebase Cloud Messaging.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. This one belongs to your shop tool, since Firebase Cloud Messaging has no trigger.

  2. 02

    Pick the starting event

    Search your shop app by name, choose the module that watches new orders and connect that account. Each order it finds becomes a bundle, one item passed on to the next module.

  3. 03

    Add Send a Message

    Click the + to the right of the first module, search Firebase Cloud Messaging and pick Send a Message. Link your connection, then map the order data from the previous module into the message.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received and check that the notification reached a test device.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What Firebase Cloud Messaging can do in Make

Firebase Cloud Messaging gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Firebase Cloud Messaging1

Send a Message

Action

In Make“Sends a message to the specified devices (clients).”

You get a push notification delivered to the devices, or clients, you target in your Firebase project, filled with data coming from earlier modules in the scenario.

When to use it
as the final step after an event in another app, such as a paid order or a new support ticket, when the user should hear about it on their phone.
Watch out
the module runs once per bundle, so a search returning many items upstream sends many notifications and uses as many operations.
Need help

Need help automating Firebase Cloud Messaging with Make?

A person reads every message.

FAQ

Firebase Cloud Messaging and Make: common questions

01Is the Firebase Cloud Messaging Make integration free?
Yes, on the Make side. Firebase Cloud Messaging is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Your Firebase subscription is separate: check the Firebase pricing page for that side.
02What does the Firebase Cloud Messaging Make integration need to connect?
An active Firebase project and credentials with access to the Cloud Messaging API. In the Google Cloud console you create an OAuth client ID under APIs and Services, set the callback URI given by the Make documentation, then copy the Client ID and Client secret. In Make you click Create a connection on the Send a Message module and paste both values. The connection is then reused by any scenario that sends messages through that project.
03Does the Firebase Cloud Messaging Make integration have a trigger?
No. The app offers no trigger, so Make cannot start a scenario from something happening inside Firebase. You have two ways to start anyway. Put the trigger of another app first, for example a form or a shop tool, and let Send a Message follow it. Or leave the first slot to the schedule of the scenario, every 15 minutes by default, down to 1 minute on paid plans, when you want reminders sent at regular intervals.
04What if a Firebase Cloud Messaging module is missing in Make?
It depends on what you need. The app only has Send a Message and no Make an API Call module, so there is no generic way to reach other parts of the Firebase API from this app. If you need to read data back or manage something else in Firebase, look for another app in Make that covers that part, or ask the team at the Make agency to review your case. The documentation also lists no specific limit for the module.
05Make or n8n for Firebase Cloud Messaging?
It depends on the rest of your stack more than on this one app. In Make, Firebase Cloud Messaging comes down to one action, Send a Message, driven by the trigger of another app or by the scenario schedule. The same app often exists as a node in n8n as well. Compare which of your other tools each platform connects to and how each one counts usage, then pick the one where your whole flow fits.
Same platform

Other docs you might need on this stack.

Browse all integrations