Google Firebase Direct

The Google Firebase channel allows RPI to send push messages using the Google Firebase provider.

A Google Firebase channel exposes the following channel-specific fields:

• Registration token: you must select an attribute that will provide the channel's registration token, which is used to identify the device that will receive notifications from Google Firebase.

• Project ID: this mandatory text property can be a maximum of 200 characters in length and represents the ID of the Google Firebase project.

• Client ID: this mandatory text property can be a maximum of 200 characters in length, and is used to capture the client ID, which will be used when making OAuth 2.0 access token requests.

• Client secret: this password-masked text property can be a maximum of 100 characters. It is used in conjunction with Client ID when making OAuth 2.0 access token requests.

• API key: this password-masked text property can be a maximum of 100 characters. It is used to specify the Google Firebase project's API key.

• Redirect URI: this mandatory text property can be a maximum of 200 characters in length, and is used to specify the authorized redirect URI associated with the client ID.

• Authorization: the channel must be authorized with Google before being used.

• Collapsible: this checkbox is unchecked by default. If checked, messages sent using the channel can be replaced by newer messages if they have yet to be delivered to a device.

• Send message as JSON payload: this checkbox is unchecked by default. When checked, messages sent via an offer using the channel will be delivered as a JSON-formatted payload.

• Notification lifetime: this property consists of an integer field (which defaults to 0) and a units dropdown, exposing values Hours (the default), Days and Weeks. It allows you specify the length of time for which the channel will attempt to resend messages when devices are unavailable.

• Fail at no merge files: this checkbox is unchecked by default. If checked, execution of an offer via the channel will fail if no mail merge files are generated.

The following property is exposed at the Advanced tab:

• Enable trace: if checked, API requests and responses will be logged at offer execution using the channel.
  Note the following message, displayed when the property is checked: