Reference · built on requestConnectorDatabases & warehouses

Cloud Firestore

Documents, queries, and change events from Cloud Firestore over its REST and RPC APIs and Firestore triggers.

Request accessPricing ↗

About

Cloud Firestore is Google's NoSQL document database in Firebase and Google Cloud. Data lives in documents grouped in collections, with subcollections nested up to 100 levels deep and each document at most 1 MiB. Every REST endpoint sits under https://firestore.googleapis.com/v1/, addressing projects/PROJECT_ID/databases/(default)/documents; the RPC API adds bidirectional Listen and Write streams, and Google recommends the RPC API where gRPC is available. Server access uses IAM roles such as roles/datastore.viewer and roles/datastore.user rather than Security Rules. Cloud Run functions subscribe to document events: onDocumentCreated, onDocumentUpdated, onDocumentDeleted, and onDocumentWritten.

An operator on Fibric reads the collections you grant, takes document events from a trigger, and proposes document writes for your approval, each with a receipt and an undo.

This is a reference listing. It documents what Fibric would read from Cloud Firestore and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Documents by path with documents.get, several at once with documents.batchGet, and pages with documents.list
  • Structured queries with documents.runQuery, and counts or sums with documents.runAggregationQuery
  • Document changes over the bidirectional Listen stream, or SDK onSnapshot listeners that deliver an initial snapshot and then each change
  • Create, update, delete, and write events from Firestore triggers, with before and after document data
  • Collection IDs under a document with documents.listCollectionIds

Proposed actions

  • Target capability: propose documents.patch to update or insert one document, sent once after approval
  • Target capability: propose a documents.commit transaction that writes several documents together or not at all
  • Target capability: propose documents.createDocument in a named collection

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Act on an order document the moment it changes

    Bind an onDocumentUpdated trigger to orders/{orderId}, compare before and after data, and propose a hold or a note when the status moves in a way you flag.

    With Order Risk, Anomaly Notice

  • Answer a question from the documents

    Run a structured query or an aggregation over a collection and show the reviewer the documents behind the figure rather than a cached total.

    With Operations Analyst, Metric Reconciliation

  • Watch the daily quota

    Track document reads and writes against the free-tier or billed quota and warn before a batch job would be refused.

    With Quota Headroom, Cost Anomaly

Requirements

  • A Firebase or Google Cloud project with a Cloud Firestore database
  • A service account granted roles/datastore.viewer for reads, or roles/datastore.user to write
  • For document events, a Cloud Run function with a Firestore trigger bound to the one database it watches
  • Reads and writes within your plan's quota; the free tier allows 50,000 document reads and 20,000 writes per day
Authentication
A Google Cloud service account whose OAuth 2.0 access token carries the https://www.googleapis.com/auth/datastore scope, sent as Authorization: Bearer; IAM roles set what it may read and write.

Limits

  • Trigger events arrive at least once and may arrive out of order; a rapid burst of changes can invoke handlers in an unexpected sequence
  • A no-op write that leaves data unchanged emits no update or write event
  • A single commit or transaction allows at most 500 field transformations, and a transaction expires after 270 seconds
  • Realtime listeners are not available on pipeline operations in Enterprise edition databases

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Cloud Firestore ↗

Questions and answers

Does the connector use Security Rules?
No. Security Rules govern the mobile and web SDKs. Server access over REST or RPC with a service account is authorized by IAM, using roles such as roles/datastore.viewer and roles/datastore.user and permissions like datastore.entities.get.
Are Firestore trigger events delivered exactly once?
No. Google documents at-least-once delivery, and a single event can invoke a function more than once. Ordering is not guaranteed. Anything built on these events has to tolerate a repeat of the same change.
Which API should a server use, REST or RPC?
Google recommends the RPC API in languages with gRPC support. REST endpoints under https://firestore.googleapis.com/v1/ cover get, list, runQuery, patch, commit, and batchWrite; the Listen and Write methods are streaming and suit the RPC path.
Ask about Cloud Firestore

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Cloud Firestore through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy