List Delivery Data
fcm_data.list_delivery_data
ActionGoogle Cloudconnection required
Calls Firebase Cloud Messaging Data GET /v1beta1/projects/{projectsId}/androidApps/{androidAppsId}/deliveryData.
List aggregate delivery data for the given Android application.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Firebase Cloud Messaging Data
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
android_app Android app id. | string | Yes | — | — | — |
page_size The maximum number of entries to return. The service may return fewer than this value. If unspecified, at most | number | No | 50 | ≥ 1 | — |
page_token A page token, received from a previous `ListAndroidDeliveryDataRequest` call. Provide this to retrieve the sub | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"page_size": 50
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
androidDeliveryData | array | — |
nextPageToken | string | — |
{
"androidDeliveryData": [],
"nextPageToken": "",
"ok": false
}See List Delivery Data run in a workflow.
In a technical demo we add the Firebase Cloud Messaging Data connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.