Firebase Cloud Messaging

• Push Notifications: Send notifications to users’ devices via Firebase.

• Customizable Messages: Include text, emojis, and structured JSON payloads.

• Sound Support: Configure notifications with or without sound.

• Token-Based Messaging: Send messages to specific users based on their unique FCM tokens.

• Delivery Tracking: Get structured JSON responses indicating the success or failure of messages.

• Log in to Firebase Console.

• Select your project or create a new one.

• Navigate to Project Settings > Service Accounts.

• Click Generate New Private Key and download the JSON file.

• Open the JSON file and locate:

• client_email

• private_key

• Go to the Plugin Tab:

• In your Bubble editor, navigate to the Plugins section.

• Add Plugin.
• Once in the Plugins tab, click the Add Plugins button.

• Search for the Plugin:
• In the search bar, type "Firebase Cloud Messaging.

• Install/Buy
• If the plugin is free, click Install to add it to your application.
• For a paid plugin, click Buy and follow the purchase instruction

• Payment Information (For Paid Plugins)
• If the plugin is a paid one, fill in your payment details and make payment.
• Charges will be added to your Bubble billing account.
• Remember, if you unsubscribe from the plugin shortly after installation, charges will be prorated based on the days used.

• Plugin Installed:
• Once installed, the plugin should appear in the Plugin list.

• In your Bubble Editor, navigate to Plugins > Firebase Cloud Messaging.

• Enter the following values:
• Issuer (account email): Paste the client_email from the JSON file.
• Private Key: Paste the private_key from the JSON file.

• Create a new Workflow in Bubble.

• Add a Button to the Page:
• Place a button labeled Send Push Notification.

• Add a Workflow:
• Select When Button Send Push Notification is Clicked.



• Add an Action:

• Select Plugins > Send Notification (Firebase Cloud Messaging).

• Configure the Notification Action:
• Project ID: The ID of your Firebase project (e.g., "abcdu-86e63")
• FcmToken: Enter the user’s device token.
• Body: Notification text (e.g., "You have a new message from John.")
• Title: Notification title (e.g., "New Message!")

• Set a Custom State to Store the Response:
• Element: Select the index page.
• Custom State: Name it "response".
• Value: Set it to Result of Step 1 (Firebase Cloud Messaging) Body Name.

• Run the Workflow to send the notification and store the response.

• Service Account Authentication:
• The old API used server keys, while the new API requires a service account JSON key.
• Ensure you have set up the private key and client email as described in the setup section.

• Updated API URL:
• Old API: https://fcm.googleapis.com/fcm/send
• New API: https://fcm.googleapis.com/v1/projects/{project_id}/messages:send

• New Request Format:
• You must now structure your requests in the HTTP v1 format:

json
{
  "message": {
    "token": "device_fcm_token",
    "notification": {
      "title": "New Alert",
      "body": "You have a new notification"
    },
    "data": {
      "customKey": "customValue"
    }
  }
}

• OAuth 2.0 Authentication:
• The HTTP v1 API uses OAuth 2.0 authentication instead of API keys.
• The Bubble plugin has been updated to handle this automatically when you input your Firebase credentials.

• If you are using the latest version of the Zeroqode plugin, it already supports the FCM HTTP v1 API.

• Ensure you have the correct Firebase Service Account Key.

• Format notifications using the new request structure for compatibility.

json
{
  "multicast_id": "number",
  "success": "number",
  "failure": "number",
  "canonical_ids": "number",
  "results": {
    "error": "text"
  }
}

• Minor update.

• Updated demo/service links.

• Updated the API and the authorization method.

• updated description.

• minor updates.

• updated description.

• added the ability to enable sound in notifications.

• Update icon.

• Update docs.

• Add the capability to send additional data with notification.

• update support emails.

• Version 1.0.