GCP Uploader
Pricing
Pay per usage
Go to Apify Store
Pricing
Pay per usage
Rating
5.0
(1)
Developer
Cir◎cle
Maintained by CommunityActor stats
7
Bookmarked
52
Total users
5
Monthly active users
12 days ago
Last modified
Categories
Share
GCP Uploader
Pricing
Pay per usage
Pricing
Pay per usage
Rating
5.0
(1)
Developer
Cir◎cle
Maintained by CommunityActor stats
7
Bookmarked
52
Total users
5
Monthly active users
12 days ago
Last modified
Categories
Share
Path where files should be uploaded to. If not provided, files will be uploaded to the root of the bucket. Example: 'my-folder/my-subfolder'
The format of the dataset to be uploaded. It's the same as the available dataset export formats.
File name to be uploaded to the bucket, otherwise the dataset ID will be used.
If checked, the source dataset will be deleted from Apify once it has been successfully uploaded to the bucket. Nothing is deleted during a dry run.
The ID of the key-value store to be uploaded to the GCP bucket.
Only records matching this regex will be uploaded to the key-value store.
Function that creates the name of the uploaded file from the record key. It receives the record key as an argument and must return the new file name.
If checked, each key-value store record will be deleted from Apify once it has been successfully uploaded to the bucket. Nothing is deleted during a dry run.
The compression method to be applied to the uploaded files.
Maximum number of files uploaded in parallel. Lower this if you hit rate limits.
Wait this many milliseconds before starting each file upload. Useful to avoid rate limiting when uploading many small files.
If checked, metadata (currently only contentType) will be uploaded to the bucket along with the file.
If checked, uploaded file entries will be stored to the Apify dataset.