Google Cloud Firestore automation
Firestore is Google's serverless NoSQL document database, part of Firebase and Google Cloud. The NoClick Firestore node works directly against the Firestore API, so a single workflow can create and delete documents, batch-get many at once, run batch writes, and commit changes inside a transaction. It also handles the database itself: create, clone, or delete a database, set up backup schedules, and clear out stale indexes. Drop it on the canvas and your app data becomes something workflows can read and write on their own.
Yes. The Firestore node creates and deletes documents, runs batch writes, commits changes, and bulk-deletes documents in one call. Wire any of these to a trigger, so a form submission, a schedule, or an inbound message can produce real writes in your database.
Yes. The On Document Created/Updated trigger starts a workflow whenever a document is added or modified in a collection you watch. The new document data flows into the next node, so you can enrich it, validate it, or fan it out to other systems as it changes.
It does. You can Begin Transaction and Commit to group writes atomically, and Batch Get Documents, Batch Write, and Bulk Delete Documents to handle many records at once. That keeps large updates consistent instead of writing one document at a time.
Yes. Beyond document operations, the node can create, clone, and delete a database, create and delete backup schedules, delete a backup, and delete an index. There is also a Custom API Call operation for any Firestore endpoint not covered by a dedicated action.
Connect the node once with your Google Cloud credentials for the project that holds your Firestore database. After that the same credential drives every operation, from creating documents to managing backup schedules, across all of your workflows.