Can NoClick write to Firestore automatically?

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.

Can a workflow react to changes in Firestore?

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.

Does the node support transactions and batch operations?

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.

Can it manage databases and backups, not just documents?

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.

How do I connect Firestore to NoClick?

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.

Firestore Integration

Google Cloud Firestore automation

56 operations availableDatabases & Storage

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.

What you can automate with Firestore

Pick one to start building it.

Firestore Operations

Triggers1

Documents5

Batch2

Queries5

Transactions3

Advanced3

Databases10

Indexes6

Operations4

Backups8

User Creds7

Locations2

Frequently asked questions

Use Firestore as an AI agent tool

Wire Firestore into a coding agent and let it use these operations as tools.

Ready to build with Firestore?

Start building workflows in minutes with our visual builder. No code required.

Book Demo

Browse all integrations

Firestore Integration

What you can automate with Firestore

Firestore Operations

Triggers1

On Document Changed

Documents5

Get Document

List Documents

Create Document

Update Document

Delete Document

Batch2

Batch Get

Batch Write

Queries5

Run Query

Run Aggregation Query

List Collection Ids

Execute Pipeline

Partition Query

Transactions3

Begin Transaction

Commit

Rollback

Advanced3

Listen

Write

Custom Api Call

Databases10

Get Database

List Databases

Create Database

Clone Database

Restore Database

Update Database

Delete Database

Export Documents

Import Documents

Bulk Delete Documents

Indexes6

List Indexes

Get Index

Delete Index

List Fields

Get Field

Update Field

Operations4

Get Operation

List Operations

Cancel Operation

Delete Operation

Backups8

Create Backup Schedule

Get Backup Schedule

List Backup Schedules

Update Backup Schedule

Delete Backup Schedule

Get Backup

List Backups

Delete Backup

User Creds7

Create User Creds

Get User Creds

List User Creds

Enable User Creds

Disable User Creds

Delete User Creds

Reset User Creds Password

Locations2

Get Location

List Locations

Frequently asked questions

Use Firestore as an AI agent tool

Related integrations

Ready to build with Firestore?