List Documents Databases

firestore.list_documents_databases
ActionDatabases & warehousesconnection required

Calls firestore v1 GET /v1/projects/{projectsId}/databases/{databasesId}/documents/{documentsId}/{documentsId1}/{collectionId}.

Lists documents.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Firestore
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

6 fields, 4 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
database
Database name or id.
stringYes———
document
Document name or id.
stringYes———
documents_id1
Documents id1 name or id.
stringYes———
collection
Collection name or id.
stringYes———
order_by
Sort expression, e.g. "name desc"; blank = the API order.
stringNo———
page_token
The previous response's nextPageToken; blank = first page.
stringNo———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
documents
array—
nextPageToken
string—
{
  "documents": [],
  "nextPageToken": ""
}

See List Documents Databases run in a workflow.

In a technical demo we add the Google Firestore connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.