Google plugin
Last updated
Was this helpful?
Last updated
Was this helpful?
Google is a tech giant best known for its search engine. It also offers a wide range of services and products including Gmail, Google Maps, Google Drive, and Android, among others. It's integral to many aspects of digital life, from web browsing to cloud storage. Google is a subsidiary of holding company Alphabet Inc.
The Bubble-made Google OAUth plugin lets end-users log in with their Google account, and fetch their profile data.
First, open the Install new plugins screen in the Bubble editor.
To find this plugin, search for Google. Optionally, you can check the Login service checkbox to further filter the results. You can also scroll to the bottom of the filters list, under Built by and select Official to single out official plugins.
Check that the Bubble logo is visible in the bottom-right, and then click Install.
The Google API follows a common pattern of requiring two different keys to authenticate your app.
App ID: The App ID (also referred to as the API Key in some contexts) is essentially the public identifier for your app. Think of it like the name tag your app wears when it talks to Google. In this context, it's not to be confused with your secret access token: In fact, the Client ID doesn't need to be kept secret.
App Secret (access token): The Secret Key, on the other hand, is like a password. It's used to secure communication between your app and Google's servers. Exposure of the Secret Key can lead to security risks, unlike the App ID.
After installing the plugin, you'll find it in your list of installed plugins and can click it to access its settings:
To see the plugin's actions and data sources, as well as their properties, please see the core reference article below:
Reference: Google
The App ID is a public identifier, and does not need to be replaced if it's exposed.
The secret key should be kept securely private, as exposure can lead to security risks. We strongly recommend revoking the exposed key and creating a new one immediately. Remember to deploy the changes in your app to Live after replacing the secret key.
