Specify the path to the object's key which contains the child objects to be queried, such as `foo/bar/here`.

The child key/path that should be used to compare objects/records. If nothing is specified, then the `$key` order is used. [Learn more here](https://firebase.google.com/docs/database/rest/retrieve-data#filtering-by-a-specified-child-key).

Indicates whether the new records are at the "top" of the ordering, or the "bottom". If nothing is selected, then the bottom/last result is assumed to be the "newest objects" (`limitToLast`).

This will be used as the `FROM` value within the `Structured Query` below.  Select a top-level collection, or to use a collection within an object/document, select `Use a Custom Value`, and then enter the path like `topCollection/someDocument/nestedCollection`

The key/path that should be searched/compared within the child objects.

You may need to define an index within your Firebase settings, [learn more here](https://firebase.google.com/docs/database/security/indexing-data).

Indicates whether the search-value is a `string` (and needs double-quotes), or if the search value is a number (don't add quotes). If nothing is selected, then quotes will automatically be used.

If multiple child objects match, this setting specifies whether the "best match" is at the top or the bottom of the result set. If nothing is selected, then the bottom/last result is assumed to be the "best match" (`limitToLast`).

This will be used as the `FROM` value within the `Structured Query` below.  Select a top-level collection, or to use a collection within an object/document, select `Use a Custom Value`, and then enter the path like `topCollection/someDocument/nestedCollection`.

The JSON contents of the [Structured Query](https://cloud.google.com/firestore/docs/reference/rest/v1beta1/StructuredQuery).

 * • the [where property](https://cloud.google.com/firestore/docs/reference/rest/v1beta1/StructuredQuery#Filter) is required
 * • the [orderBy property](https://cloud.google.com/firestore/docs/reference/rest/v1beta1/StructuredQuery#Order) is recommended, but may be omitted.

**Note:** the fields `select`, `from`, and `limit` are assigned/handled automatically.

You can learn more info, and see an example, [in this help guide.](https://zapier.com/help/firebase/#creating-a-firestore-structured-query-for-a-search)

Specify the path to the object's key where the fields will be created, such as `foo/bar/here`.

If any field/value is a valid number (integer or double), this tells the database to save it as a `number` rather than a `string`.

The key to use for this object, or leave empty to let Firebase generate one.

Select a top-level collection. If you want to use a collection within an object/document, select `Use a Custom Value`, and then enter the path like `topCollection/someDocument/nestedCollection`.

If empty, the newly created document will be assigned a unique ID. Otherwise, any existing document with the same ID will be replaced/overwritten.

Requests can only be made to domains associated by this application. View [documentation](https://help.zapier.com/hc/en-us/articles/12899607716493) for more details.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, `{"foo": "bar"}` is perfectly valid.

Firebase Realtime Database and Google Cloud Firestore are flexible databases that give you the ability to easily store and sync app data at global scale.

Building an app is hard enough without worrying about the infrastructure. Zapier helps make sure your Firebase data is accurate by automatically keeping your records updated. You can use Zapier's custom tools to schedule updates or add RSS feed items to Firebase so you can spend less time worrying about your infrastructure and more time focused on your users.

Firebase / Firestore

MySQL is a premier database used in millions of production environments around the world. Easily plug your MySQL database into any web service.

MySQL

PostgreSQL is a powerful, open-source database engine with a uniquely advanced query optimizer and dozens of built in features, making it an easy choice for production databases.

PostgreSQL

SQL server (or MS SQL) is a top of the line database geared for the cloud

SQL Server

Amazon Relational Database Services (RDS) allow you to set up, operate, and scale relational databases in the cloud.

Amazon Relational Database Services (RDS)

emaill address that will be added to Sensorpro.

Use the formid from Tools, Signup forms, step 1

Sensorpro is an EU-made email marketing platform.

Sensorpro

Here are some creative ways to use Firebase with Zapier:

Need to update contact information or user IDs in your app? Add or update Firebase records when there are new rows in a Google Sheets spreadsheet.

Use Zapier to add new entries from Typeform to Firebase, saving you time and giving you room to scale your app's usage.

Update Firebase records by ID daily, weekly, or monthly so you can spend more time focusing on improving and monetizing your app.

This integration creates Sensorpro contacts from new child objects in a Firebase Realtime Database in Firebase / Firestore.

Firebase / Firestore + Sensorpro

Create Sensorpro contacts from new child objects in a Firebase Realtime Database in Firebase / Firestore

Supported triggers and actions

New Child Object in a Firebase Realtime Database

Create or Replace Firebase Realtime Database Record

API Request (Beta)

Find Cloud Firestore Document

New Document Within a Firestore Collection

Create Cloud Firestore Document

Find Firebase Realtime Database Record

Create Contact

About Firebase / Firestore

Related categories

Similar apps

MySQL

PostgreSQL

SQL Server

About Sensorpro

Related categories