Google Cloud Firestore Make integrationAutomate Google Cloud Firestore with Make.
Can your Firestore documents move on their own when your data changes? The Google Cloud Firestore Make integration gives you 13 modules: 2 scheduled triggers, 7 actions and 4 searches. This guide shows app builders how to connect a project and ship a first scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Google Cloud Firestore Make integration automate?
The Google Cloud Firestore Make integration links your Firestore database to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or writes data. Your documents can then be created, read, updated or backed up from other apps, without writing backend code.
Records from your other tools, stored as documents. A signup form or a CRM sends its data, and Create a Document writes it into the collection your app already reads. No custom endpoint to maintain.
New documents pushed to your team. Watch New Documents picks up each document added to a collection, and the next module sends it wherever it is useful: a spreadsheet, a chat channel, a support tool. The advanced version watches several collections and their descendants, filtered by criteria.
Backups you can restore. Backup to Google Cloud Storage copies documents out of Firestore, and Restore from Google Cloud Storage brings them back. Both need the Blaze plan on your Firestore account.
What Make does not give you here: an instant trigger. Both triggers are scheduled, so Make checks for new documents on the scenario's schedule. Anything the listed modules do not cover goes through Make an API Call. Firestore also has an n8n node, described on the Google Cloud Firestore n8n integration page; the n8n vs Make comparison helps you pick, and the Make pricing page explains what each plan counts.
How do you connect Google Cloud Firestore to Make?
- 01
Prepare your Google Cloud project
Start on the Google side. Create and configure a Google Cloud Platform project for Firestore, the one that holds the database your scenarios will read and write. Make relies on that project for every call.
- 02
Create the connection in Make
In a new scenario, click the +, search for Google Cloud Firestore and pick any module. Click Create a connection and complete the steps Make shows. A connection is your account linked to Make once, then reused by every Firestore module.
- 03
Check that Make sees your data
Back in the module, the fields open up once the connection exists. Fill one module and click Run once: if a bundle comes back, the link works. A bundle is one item passed from a module to the next, here one document.
Build your first scenario with Google Cloud Firestore
GoalWhen a lead fills in a form in another app, Make stores it as a new document in Google Cloud Firestore.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + in the middle of the editor. This first module decides when everything starts.
- 02
Pick the source of your leads
Search for the app that collects the form entries and choose its trigger. Connect that account the same way, with Create a connection or Add.
- 03
Add Create a Document
Click the + on the right of the first module, search for Google Cloud Firestore and choose Create a Document. Select your Firestore connection and fill the module fields.
- 04
Map the form answers
For each value of the document, click in the field and choose the matching answer from the first module. Make shows what the previous module returned, so no need to type anything by hand.
- 05
Test with Run once
Submit a test entry in the form, then click Run once. Open the bubble of each module to read the bundles it received, and check that the new document now sits in your collection.
- 06
Schedule and switch it on
Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your Make plan.
Which Google Cloud Firestore triggers start a scenario?
2 modules start a scenario when something happens in Google Cloud Firestore. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Google Cloud Firestore as soon as it happens.
Watch New Documents
Scheduled triggerIn Make“Triggers when a new document is created in a specific collection.”
Watch New Documents starts your scenario with every document added to one collection you choose, and hands each new document to the next module as a bundle. It is the simplest way to react to what your app writes.
Watch New Documents (Advanced)
Scheduled triggerIn Make“Triggers when a new document is created with specific criteria across multiple collections and their descendants.”
With the advanced watcher, one trigger covers several collections and the collections nested under them, and keeps only the new documents that match your criteria. You get one scenario instead of one per collection.
What can Make do in Google Cloud Firestore?
Google Cloud Firestore gives you 11 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.
Documents
8 modulesNote: Every query requires an index. For the most basic queries, Google Cloud Firestore creates indexes by default. Some queries require you to set up an index manually. Follow the steps below to set up the Index.
Create a Document
ActionIn Make“Creates a new document.”
Create a Document turns data from any other module into a fresh Firestore document, ready for your app to display. It is the entry point for leads, orders or sign-ups arriving from outside tools.
Get a Document
ActionIn Make“Gets a single document.”
You get the full content of one document you already know, so later modules can use its values. Think of it as opening one record instead of searching the whole collection.
Get Documents
SearchIn Make“Gets multiple documents across different collections.”
Several documents come back in one step, even when they live in different collections. Like any search, it can hand zero, one or many bundles to what follows.
List Documents
SearchIn Make“Lists documents of a collection.”
This search walks through the documents of one collection and hands them over one by one. Handy when you need the whole content of a collection rather than a filtered slice.
List Collection IDs
SearchIn Make“Lists all the collection IDs underneath a document.”
Here you find out which subcollections sit under a document, so a scenario can explore a structure it does not know in advance. The result is a list of IDs, not the documents themselves.
Query Documents
SearchIn Make“Runs a query.”
Query Documents brings back only the documents that match your conditions, the Make equivalent of a filtered query in your app. You save operations compared with listing everything.
Update a Document
ActionIn Make“Updates or inserts a document.”
Your document gets its new values, and if it does not exist yet, Make inserts it. Handy when you are unsure the record exists.
Delete a Document
ActionIn Make“Deletes a single document.”
One document disappears from Firestore, which keeps your collections free of records that no longer matter. The module removes a single document per run.
Note: You need to have the Blaze Plan for your Firestore account to use the Storage modules.
2 modulesBackup to Google Cloud Storage
ActionIn Make“Backups documents from Firestore to Google Cloud Storage.”
You get a copy of your Firestore documents saved in Google Cloud Storage, outside the database itself. It gives you a restore point before a risky change.
Restore from Google Cloud Storage
ActionIn Make“Restores documents from Google Cloud Storage into Firestore. Existing documents with the same name are overwritten.”
Documents saved in Google Cloud Storage come back into Firestore, so a bad import or a wrong update can be rolled back. It is the partner of the backup module.
Other
1 moduleMake an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
When no listed module does what you need, this one lets you call any endpoint of the Cloud Firestore API with the connection you already set up. No second login, no extra app.
Need help automating Google Cloud Firestore with Make?
A person reads every message.
