STEP 1
Connect Google Firestore and Supabase
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Google Firestore and Supabase Integration
Keep Google Firestore and Supabase in sync by integrating their events and actions. When database events happen in Google Firestore, update the Supabase automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Google Firestore and Supabase
Detailed info you need to know about Google Firestore and Supabase integrations in WEXTL. Explore which modules apps support and how you connect them.
Google Firestore
Cloud Firestore NoSQL database for realtime app data. [5]
How to connect Google Firestore to Supabase
Set up your Google Firestore and Supabase integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Google Firestore and Supabase nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Google Firestore and Supabase. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Google Firestore and Supabase work in WEXTL?
WEXTL exposes actions and triggers for Google Firestore and Supabase that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Google Firestore triggersSupabase actions
Google Firestore modules
- Batch Get DocumentsBatches get documents.
- Batch WriteBatches the write.
- Begin TransactionBegins the transaction.
- Bulk Delete DocumentsPerforms bulk delete documents.
- Cancel OperationCancels the operation.
- Clone DatabaseClones the database.
- CommitCommits the record.
- Create Backup ScheduleCreates backup schedule.
- Create DatabaseCreates a new database.
- Create DocumentCreates a new document.
- Create User CredsCreates user creds.
- Delete BackupDeletes an existing backup.
- Delete Backup ScheduleDeletes backup schedule.
- Delete DatabaseDeletes an existing database.
- Delete DocumentDeletes an existing document.
- Delete IndexDeletes an existing index.
- Delete OperationDeletes an existing operation.
- Delete User CredsDeletes user creds.
- Disable User CredsDisables user creds.
- Enable User CredsEnables user creds.
- Execute PipelineExecutes the pipeline.
- Export DocumentsExports the documents.
- Get BackupReturns a single backup.
- Get Backup ScheduleRetrieves backup schedule.
- Get DatabaseReturns a single database.
- Get DocumentReturns a single document.
- Get FieldReturns a single field.
- Get IndexReturns a single index.
- Get LocationReturns a single location.
- Get OperationReturns a single operation.
- Get User CredsRetrieves user creds.
- Import DocumentsImports the documents.
- List BackupsRetrieves a list of backups.
- List Backup SchedulesLists backup schedules.
- List Collection IdsLists collection IDs.
- List DatabasesRetrieves a list of databases.
- List DocumentsRetrieves a list of documents.
- List FieldsRetrieves a list of fields.
- List IndexesRetrieves a list of indexes.
- List LocationsRetrieves a list of locations.
- List OperationsRetrieves a list of operations.
- List User CredsLists user creds.
- Partition QueryPartitions the query.
- Reset User Creds PasswordResets user creds password.
- Restore DatabaseRestores the database.
- RollbackRollbacks the record.
- Run Aggregation QueryRuns aggregation query.
- Run QueryRuns the query.
- Update Backup ScheduleUpdates backup schedule.
- Update DatabaseUpdates an existing database.
Supabase modules
- Create a RowCreates a new row.
- Create a UserCreates a new user with a given email and password.
- Create a User LinkCreates a link (auth, restore, magic log in, update password) for a specified user.
- Create Multiple RowsCreates multiple rows (batch).
- Delete a BucketDeletes an existing bucket by ID.
- Delete a RowDeletes a single or multiple rows.
- Delete a UserDeletes an existing user.
- Download an ObjectDownloads an existing object from a storage bucket.
- Get a Bucket DetailsRetrieves a detailed info about existing bucket.
- Get a UserRetrieves a single user details.
- Get Rows CountRetrieves rows count in a specified table.
- List BucketsRetrieves a list of all available buckets.
- List UsersRetrieves a list of users from Supabase Auth.
- Make API CallPerforms an arbitrary authorized API call.
- Search RowsSearches for rows.
- Update a RowUpdates a single or multiple rows.
- Upload an ObjectUploads an object to an existing bucket.
- Watch EventsTriggers when your Supabase database posts an event to the generated webhook URL. Supabase has no webhook-registration API — copy the generated URL and add it under your Supabase project → Database → Webhooks (or Database → Triggers) for the table/events you want to watch.
- Watch RowsTriggers when a row is created or updated.
- Watch UsersTriggers when a new user is created using Supabase authentication.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Google Firestore and Supabase integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Google Firestore and Supabase.
Connect your Google Firestore and Supabase accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Google Firestore's "Watch Backups" fires, WEXTL can "Create a Row" in Supabase. Google Firestore has 5 triggers (including Watch Backups, Watch Backup Schedules, and Watch Databases); Supabase has 17 actions (including Create a Row, Create a User, and Create a User Link). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Google Firestore-to-Supabase automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Google Firestore (or Supabase) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Google Firestore + Supabase automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Google Firestore and Supabase integration.
- Google Firestore and Supabase integration source code, module specs and credentials implementation.
- Our Google Firestore and Supabase integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Google Firestore and Supabase — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Google Firestore integration information
- Supabase integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library