Sending Notification With Firebase Cloud Functions

Updated 24 October 2017

Save

Firebase has launched a new tool to make Application development more easier. The Firebase Cloud Functions is currently in its Beta version and is introduced to help developers creating an application without their own servers. They can use Firebase Servers and write their code over Firebase Servers directly using Firebase Cloud Functions.

Yes I know you will think why I should use it if I have my own server. But wait, because there is more to it. Even if you have your own server, its time and resource taking to first hit your server and then your server will hit Firebase server for some result. You might think what’s the idle scenario for that to happen so let me give you one or two scenarios.

  1. Suppose you want to implement real-time chat in your application. You can opt for implementing it with various ways but we all know the best and easiest way is using Firebase Database. So now you have implemented Firebase Database Real-time chat feature. Now I want that the user must be notified every time a new message has been added to the database. So you have to send the changes to your server and then your server will create a notification key for the recipients and then will use Firebase Push Notification to send the Notification. While On the other hand you could use Firebase Cloud Functions and handle the event whenever anything is added in the Database generate a notification for the same.
  2. In another scenario, suppose you want to don’t want your user to have full access to the database. You can yourself create an HTTP request on cloud servers from where you can provide a particular potion of the database to that user.

Here we are implementing the first scenario of sending push notification. But before that lets see what our database looks like.Firebase cloud functionsAs you can see I have two different sections namely data and message. In data section all the customer related properties are added. While in message section there are messages stored.

Instructions to follow

Step 1: You need Firebase CLI and Node.js for cloud functions to work and then you have to initialize your project. If you haven’t done it yet, please follow the firebase guide.

Step2: Now when everything is setup, open <your_firebase_directory>/functions/index.js file. Here we will write our code for sending push notification when a new message is added in message section of database.

  1. Create a function to hit whenever a new entry is added to your database message section
  2. Here {userId} will be the customer-id of the user and we can get it from event’s param. Also we will get all the nodes added to a random push-Id ( {pushId} ) in event’s data like
  3. Now as we have got our userId as well as the whole message we can send a notification to the user as
  4. Now as your function is ready you can deploy the function to the Firebase Cloud through command line as

And here you go. You are ready with a cloud function that will execute whenever a new message is added to your Firebase database. And you can do many more with the new Firebase cloud functions. For more such examples go to Firebase Cloud Functions documentation.

author
. . .

Leave a Comment

Your email address will not be published. Required fields are marked*


5 comments

  • Malik Azhan
    i just want some help,,,actually i just want to push a notification to two different modules in same app like notification for attendance node and notification for Result node …but i cant understand how to do this plz help me if anyone know how to do this…….Thank u 🙂
    using this code

    const functions = require(‘firebase-functions’);

    const admin = require(‘firebase-admin’);
    admin.initializeApp(functions.config().firebase);

    exports.pushNotification = functions.database.ref(‘/messages/{pushId}’).onWrite(( change,context) => {

    console.log(‘Push notification event triggered’);

    // Grab the current value of what was written to the Realtime Database.
    // var valueObject = event.data.val();
    const message = change.after.val();
    const payload = {
    notification: {
    title: ‘App Name’,
    body: “New message”,
    sound: “default”
    },
    data: {
    title: message.title,
    message: message.message
    }
    };

    const options = {
    priority: “high”,
    timeToLive: 60 * 60 * 24 //24 hours
    };

    return admin.messaging().sendToTopic(“notifications”, payload, options);
    })

    • V
      What did you come up with? If your sending the notifications as a topic, you just need to subscribe to the topic on the client. You can sign up for multiple topics if thats what you want to do. Everything else looks correct.

      Firebase has updated the API to a send function. They recommend this structure now.

      // The topic name can be optionally prefixed with “/topics/”.
      var topic = ‘highScores’;

      // See documentation on defining a message payload.
      var message = {
      data: {
      score: ‘850’,
      time: ‘2:45’
      },
      topic: topic
      };

      // Send a message to devices subscribed to the provided topic.
      admin.messaging().send(message)
      .then((response) => {
      // Response is a message ID string.
      console.log(‘Successfully sent message:’, response);
      })
      .catch((error) => {
      console.log(‘Error sending message:’, error);
      });

    • Bhargav Kaneriya
      timeToLive: 60 * 60 * 24 it means after 24 hours it will send push notification. Am I Right?
      • anchit (Moderator)
        Hello bhargav,

        No, the timeToLive property does not mean that the notification will be sent after 24 hours.

        It actually means the default time for which the notification will be kept in FCM storage while the device is offline.

        So, for this particular case if the receiving device is offline and not able to receive the notification then the FCM will try to keep this notification in their storage for the next 24 hours and if in the next 24 hours the device is in the state to receive the notification then the notification will be delivered to the device, else the notification will fail to deliver.

        For more details on these params of the notification request, you can check the official explaination from the FCM panel over here –> https://firebase.google.com/docs/cloud-messaging/http-server-ref#downstream-http-messages-json

      • anchit (Moderator)
        Hello bhargav,

        No, the timeToLive property does not mean that the notification will be sent after 24 hours.

        It actually means the default time for which the notification will be kept in FCM storage while the device is offline.

        So, for this particular case if the receiving device is offline and not able to receive the notification then the FCM will try to keep this notification in their storage for the next 24 hours and if in the next 24 hours the device is in the state to receive the notification then the notification will be delivered to the device, else the notification will fail to deliver.

        For more details on these params of the notification request, you can check the official explanation from the FCM panel over here –> https://firebase.google.com/docs/cloud-messaging/http-server-ref#downstream-http-messages-json

  • Start a Project


      Message Sent!

      If you have more details or questions, you can reply to the received confirmation email.

      Back to Home