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.

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).

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.

API docs for Firebase / Firestore are located here https://firebase.google.com/docs/reference/

Requests can only be made to domains associated by this application.

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.

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.

• • the where property is required
• • the orderBy property 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.

API docs for WPForms are located here https://wpforms.com/?p=8374&post_type=wpforms_doc&preview=1&_ppp=857193bee8

Requests can only be made to domains associated by this application.

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.

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

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 any field/value is a valid number (integer or double), this tells the database to save it as a number rather than a string.

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

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

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.

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).