List Releases
firebase_rules.list_releases
ActionBusiness appsconnection required
Calls Firebase Rules GET /v1/projects/{projectsId}/releases.
List the Release values for a project. This list may optionally be filtered by Release name, Ruleset name, TestSuite name, or any combination thereof.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Firebase Rules
- 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, none 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 | — | — | — |
filter Optional. `Release` filter. The list method supports filters with restrictions on the `Release.name`, and `Rel | string | No | — | — | — |
page_size Optional. Page size to load. Maximum of 100. Defaults to 10. | number | No | 50 | ≥ 1 | — |
page_token Optional. Next page token for the next batch of `Release` instances. | 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 | — |
releases | array | — |
nextPageToken | string | — |
{
"nextPageToken": "",
"ok": false,
"releases": []
}Related Firebase Rules nodes
See List Releases run in a workflow.
In a technical demo we add the Firebase Rules connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.