Firestore Import

Service account key in JSON format. You can get it from Firebase Console -> Project Settings -> Service accounts -> Generate new private key. Paste the whole JSON string here.

ID of the Apify dataset to import data from.

Firestore collection to import data to. If it doesn't exist, it will be created. Note: you can customize the collection for each document using the transformFunction input. This can be useful when you want to import data to sub-collections.

Name of the Firestore database. If not provided, the default database ("(default)") will be used.

Field in the dataset item that will be used as a Firestore document ID. If not provided, all documents will be created with a random ID generated by Firestore (it means that value of documentConflictResolution is ignored in that case). This is useful when you want to update existing documents in Firestore. Note: you can customize the ID for each document independently using the transformFunction input field.

How to handle conflicts when importing data to Firestore:

• overwrite: replace existing Firestore documents with the same ID.
• merge: merge data from the dataset items with existing Firestore documents.
• skip: documents with existing IDs will be skipped. ⚠️ Please note that the skip resolution has really bad performance on large scale and can't use batch writes.

Function that transforms each item from the dataset before importing it to Firestore. The function must return an object (or array of objects) with the data key that contains the transformed document and other optional fields. See README for more details and examples.

Number of items to import in a single batch. Lower values are safer but slower, see Firestore limits (10 MiB batch write). Please note that skip conflict resolution does not use batch writes and will always import one item at a time.