Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

Push Notifications on the Web for Conversations



Push Notifications on the Web

push-notifications-on-the-web page anchor

Push notifications are an important part of the web experience. Users have grown accustomed to push notifications being part of virtually every app that they use. The Twilio Conversations JavaScript SDK can integrate Firebase Cloud Messaging (FCM) for push notifications.

Managing your push credentials is necessary, as your registration token is required for the Conversations SDK to be able to send any notifications through FCM. Let's go through the process of managing your push credentials.


Step 1 - Enable push notifications for your Service instance

step-1---enable-push-notifications-for-your-service-instance page anchor

The default enabled flag for new Service instances for all Push Notifications is false. This means that Push will be disabled until you explicitly enable it. You can follow this guide to do so.


Step 2 - Configure Firebase

step-2---configure-firebase page anchor

The developer must configure Firebase Cloud Messaging (FCM) before configuring notifications. Google provides an easy-to-use Firebase Console(link takes you to an external page) to manage Firebase services and configurations.

Create a project on Firebase

create-a-project-on-firebase page anchor

To use push notifications for your JavaScript app, you will need to create a project on the Firebase Console(link takes you to an external page):

Firebase-project-name-.

Get the project's configuration

get-the-projects-configuration page anchor

The Firebase Cloud Messaging (FCM) requires configuration to initialize. The Firebase console has an easy way to create this configuration.

After you create a Firebase project, you can select the option to add Firebase to your web app. From the project overview page, under the text "Get started by adding Firebase to your app", select the Web icon.

Project-overview-page.

As a next step, register your app. Give the app a nickname and click the Register app button.

Register-your-application.

Once the app is registered, a customized code snippet will be displayed.

Add-Firebase-SDK.

This dialog contains sample JavaScript code with filled-in parameters that you can use in your newly created project.

Save this sample code with configuration - we will use it later in this guide.


Step 3 - Upload your API Key to Twilio

step-3---upload-your-api-key-to-twilio page anchor

Now that we have our app configured to receive push notifications, let's upload our API Key by creating a Credential resource. Check out the Credentials page in the Twilio console(link takes you to an external page) page to generate a credential SID using your API key. Click the Create button.

Credentials.

Step 4 - Pass the API Credential Sid in your Access Token

step-4---pass-the-api-credential-sid-in-your-access-token page anchor

This step is to ensure that your Conversations JS SDK client Access Token includes the correct credential_sid - the one you created in Step 3 above. Each of the Twilio Helper Libraries enables you to add the push_credential_sid. You can see the relevant documentation for your preferred Helper Library for the details. Here is an example using the Node.js Twilio helper Library:


_10
const chatGrant = new ChatGrant({
_10
serviceSid: ConversationServiceSid,
_10
pushCredentialSid: FCM_Credential_Sid
_10
});


Step 5 - Initialize Firebase in your web app

step-5---initialize-firebase-in-your-web-app page anchor

Now it's time to initialize the Firebase with the sample code from Step 2 above.

In your web app's early initialization sequence, use the sample code (and do not forget to include/import the Firebase library provided by Google). We recommend including an additional check for the correct import of the Firebase libraries.


_12
// Initialize Firebase
_12
var config = {
_12
apiKey: "...",
_12
authDomain: "...",
_12
projectId: "...",
_12
storageBucket: "...",
_12
messagingSenderId: "...",
_12
appId: "..."
_12
};
_12
if (firebase) {
_12
firebase.initializeApp(config);
_12
}


Step 6 - Request push permissions from the user and get your FCM token

step-6---request-push-permissions-from-the-user-and-get-your-fcm-token page anchor

In this step, we are requesting permission from the user to subscribe to and to display notifications. We recommend adding checks for the correct initialization of Firebase.


_17
if (firebase && firebase.messaging()) {
_17
// requesting permission to use push notifications
_17
firebase.messaging().requestPermission().then(() => {
_17
// getting FCM token
_17
firebase.messaging().getToken().then((fcmToken) => {
_17
// continue with Step 7 here
_17
// ...
_17
// ...
_17
}).catch((err) => {
_17
// can't get token
_17
});
_17
}).catch((err) => {
_17
// can't request permission or permission hasn't been granted to the web app by the user
_17
});
_17
} else {
_17
// no Firebase library imported or Firebase library wasn't correctly initialized
_17
}


Step 7 - Pass the FCM token to the Conversations JS SDK and register an event listener for new push arrival

step-7---pass-the-fcm-token-to-the-conversations-js-sdk-and-register-an-event-listener-for-new-push-arrival page anchor

If you got to this step, then you have Firebase correctly configured and an FCM token ready to be registered with Conversations SDK.

This step assumes that you have Conversation's Client created with the correct Access Token from Step 4.


_10
// passing FCM token to the `conversationClientInstance` to register for push notifications
_10
conversationClientInstance.setPushRegistrationId('fcm', fcmToken);
_10
_10
// registering event listener on new message from Firebase to pass it to the Conversations SDK for parsing
_10
firebase.messaging().onMessage(payload => {
_10
conversationClientInstance.handlePushNotification(payload);
_10
});


Rate this page: