Google Cloud Firestore n8n integrationAutomate Google Cloud Firestore with n8n.

Writes a new document into a collection and returns what Firestore stored. Each listed attribute becomes a field.

• Project Name or ID: the project as displayed in the firebase console URL, from the list or from an expression, the n8n syntax that reads a field of the incoming item ({{ $json.projectId }}).
• Database: the database to write to, usually the provided default value.
• Collection: the collection that receives the document.
• Columns / Attributes: the attributes to save, for example productId, modelName, description.
• Document ID: optional. Empty, Firestore generates an id; filled, it keeps your own key.

One call covers both cases: the document is created when it does not exist, updated when it does. A workflow that runs twice on the same record leaves one document, not two.

• Project Name or ID: same project picker as the other operations.
• Database: the target database, usually the provided default value.
• Collection: the collection holding the documents to upsert.
• Update Key: the field of the input item that carries the document ID, documentId for instance. It decides create against update.
• Columns /Attributes: the columns to insert, such as age, city, location.

Removes one document from a collection. Firestore deletes by path, so the operation needs the exact id, not the value of a field inside the document.

• Project Name or ID: the Firestore project, chosen in the list or built from an expression.
• Database: the database that holds the collection.
• Collection: the collection name.
• Document ID: the id of the document to remove, often {{ $json.documentId }} from an earlier node.

Reads a single document back and hands its fields to the next node. Nothing is written, which makes it the safe way to check a record before acting on it.

• Project Name or ID: the project shown in the firebase console URL.
• Database: the database to read from.
• Collection: the collection to look into.
• Document ID: the id to fetch. A required field blocks the node when it comes in empty, so guard it with an If node.
• Simplify: on, n8n returns a flat version of the document instead of the raw typed payload.

Pulls the documents of one collection as a list of items, one item per document, ready for a loop or an export.

• Project Name or ID: the Firestore project.
• Database: the database that contains the collection.
• Collection: the collection to read.
• Return All: on, n8n walks the API pages until every document of the collection is in. Off, it stops at Limit.
• Limit: the maximum number of documents returned when Return All stays off.
• Simplify: returns the documents in their simplified shape rather than the raw response.

Runs a query against your documents and returns the ones that match, which beats fetching a whole collection and filtering it in a Code node.

• Project Name or ID: the project the query runs against.
• Database: the database holding the data.
• Query JSON: the query to execute, in Firestore structured query syntax, for example {"structuredQuery": {"where": {"fieldFilter": {"field": {"fieldPath": "age"},"op": "EQUAL", "value": {"integerValue": 28}}}, "from": [{"collectionId": "users-collection"}]}}. The collection is named inside the query itself, not in a separate field.
• Simplify: trims the response to the document fields.

Lists the root collections of a database, so a workflow can discover what exists instead of hardcoding collection names.

• Project Name or ID: the project whose collections you want.
• Database: the database to inspect, usually the provided default value.
• Return All: on, every root collection comes back. Off, the node stops at Limit.
• Limit: how many collections to return when Return All is off.