Google Pub/ Sub Integration

google pub/ sub logo


  1. Overview
  2. Setup

1. Overview

Google Cloud Pub/Sub Integration is a streaming data integration that pushes data from the Smart Network into a client's Google Cloud Pub/Sub tenancy in real-time. Data is typically made available to Google Cloud Pub/Sub Topics, on which Subscribment can be set up to ensure that event handling and analytics are fed with the most current state of the measured space. Google Cloud Pub/Sub Integration creates a pathway to advanced storage, visualization, and analytics in the Google Cloud ecosystem from the Microshare Smart Network.

2. Setup


Client Side

Requirements :

  • A. Create a Service Account
  • B. Generate a Key

A. Create a Service Account

In order to create a Service Account, first log into your Google Cloud Platform (GCP).

image 1

Then go to Menu > API & Services > Credentials.

image 2

image 3

Click on Create Credentials and on Service Account.

image 4

Then you will have to give it name such as "Microshare® Data" for example, and a Service Account Id , which could be the same as the name. And finally you can add your own description.

image 5

Our example :

image 6

Regarding the permissions, it is important to select PubSub Editor or PubSub Admin for better maintenance.

image 7

You can leave the last page as is and click Done.

image 8

The Service Account is now set up, and the email is :

  • Service Account Id@Project

If at any time you need to change the role, you can change the settings for the email in the role interface.

image 9

B. Generate the needed key

Now let's click on the created Service Account.

image 10

Then go to the bottom of the page to find the "Keys" section .

image 11

And Click on Add Key > Create new Key.

image 12

Pick JSON and click on CREATE.

image 13 Your key is now created and automatically downloaded on your computer.

image 14

You can open it to check that it's all right like that :

image 15

Be careful to store and transmit the resulting file in a secure fashion. These access credentials are stored in plain text and are vulnerable to security leaks.

Your Microshare Service or Support contact will need the .json file. It is recommended that this information be sent securely via GPG encrypted email or through an encrypted chat connection using

Did this doc help you?

For further questions or support, please contact us at
ms logo