Google Chrome (v2)

with google chrome modules in make, you can send a notification in your google chrome account to use the google chrome modules, you must have a google account and set up a google chrome extension with notifications allowed for more information, review the get started with chrome extensions documentation https //developer chrome com/docs/extensions/get started as well as the information on setting up a firebase cloud messaging client app https //firebase google com/docs/cloud messaging/js/client refer to the google chrome api documentation https //developer chrome com/docs/extensions/reference/api and the firecloud base messaging api documentation https //firebase google com/docs/reference/fcmdata/rest for a list of available endpoints connect google chrome to make to establish the connection in make log in to your make account, add a google chrome module to your make, and click create a connection optional in the connection name field, enter a name for the connection optional switch on the show advanced settings toggle and enter your google cloud platform project client credentials for more information, see the google chrome (v2) docid\ itfgjb ux0tniywtsb0ey below click sign in with google if prompted, authenticate your account and confirm access you have successfully established the connection you can now edit your {{scenario singular lowercase}} and add more modules if your connection requires reauthorization at any point, follow the connection renewal steps here docid\ so88fm6pkt0g adkddfzz create and configure a google cloud platform project for google chrome to connect to make using your own client credentials, you can create and configure a project in the google cloud platform create a google cloud platform project for google chrome to create a google cloud platform project log in to the google cloud platform https //console cloud google com/ using your google credentials on the welcome page, click create or select a project > new project enter a project name and select the location for your project click create in the top menu, check if your new project is selected in the select a project dropdown if not, select the project you just created to create a new project or work in the existing one, you need to have the serviceusage services enable permission if you don’t have this permission, ask the google cloud platform project owner or project iam admin to grant it to you enable apis for google chrome to enable the required apis open the left navigation menu and go to apis & services > library search for the following apis firebase management api and firebase cloud messaging api click the relevant api, then click enable configure your oauth consent screen for google chrome to configure your oauth consent screen in the left sidebar, click google auth platform click get started in the overview section, under app information , enter make as the app name and provide your gmail address click next under audience , select external for more information regarding user types, refer to google's exceptions to verification requirements documentation https //support google com/cloud/answer/9110914#exceptions ver reqts under contact information , enter your gmail address under finish , agree to the google user data policy click continue > create in the branding section, under authorized domains , add make com and integromat com click save optional in the audience section, add your gmail address on the test users page, then click save and continue if you want the project to remain in the testing publishing status in the data access section, click add or remove scopes , add the following scopes, and click update click save publishing status testing if you keep your project in the testing status, you will be required to reauthorize your connection in make every week to avoid weekly reauthorization, update the project status to in production in production if you update your project to the in production status, you will not be required to reauthorize the connection weekly to update your project's status, go to the google auth platform , the audience section, and click publish app if you see the notice needs verification , you can choose whether to go through the google verification process https //support google com/cloud/answer/13463073?authuser=1\&visit id=638718595933013017 1855034908\&rd=1 for the app or to connect to your unverified app currently connecting to unverified apps works in make, but we cannot guarantee the google will allow connections to unverified apps for an indefinite period for more information regarding the publishing status, refer to the publishing status section of google's setting up your oauth consent screen help https //support google com/cloud/answer/10311615#zippy= create your google chrome client credentials to create your client credentials in google auth platform, click clients click + create client in the application type dropdown, select web application update the name of your oauth client this will help you identify it in the platform in the authorized redirect uris section, click + add uri and enter the following redirect uri https //www make com/oauth/cb/chrome click create click the oauth 2 0 client you created, copy your client id and client secret values, and store them in a safe place you will use these values in the client id and client secret fields in make build google chrome {{scenario plural}} after connecting the app, you can perform the following action actions send a notification sends a notification to the browser connection establish a connection to your google chrome account project id select the project id recipient select the recipient category token corresponds to a single recipient or a group of recipients specified by the fcm registration token of a recipient topic corresponds to the fcm topic that sends the notification to all recipients subscribed to the topic title enter the title of the notification body enter the body of the notification icon url enter the url of an icon to be displayed as part of the notification priority set the relative priority for this notification priority is an indication of how much of the user's valuable attention should be consumed by this notification low priority notifications may be hidden from the user in certain situations, while the user might be interrupted for a higher priority notification the system will determine how to interpret this priority when presenting the notification low priority notifications may not be supported for some versions collapse key enter the collapse key this is a string that groups notifications and prevents similar multiple notifications from occurring corresponds to the topic web push header disable the auto dismiss of notifications select yes or no if enabled (yes), the notification will be displayed until it is closed by clicking the close button url enter the url (including the https prefix) that will open in a new tab when the user clicks the notification validate only select yes , no , or empty select yes to test the request without delivering the message