The /google/store Robot
We export to the storage platform of your choice.
The /google/store Robot exports encoding results to Google Storage.
||(required) String / Array of Strings / Object||
GeneralSpecifies which Step(s) to use as our input.
Special Step namesA special Step name is
Providing several Steps as inputYou can add arrays to
That's likely all you need to know about
› Advanced use cases
Step bundlingSome Robots can gather several Step results for a single invocation. For example, the /file/compress Robot would normally create one archive for each file passed to it. If you'd set
This is also a crucial parameter for the /video/adaptive Robot, otherwise you'll generate 1 playlist for each viewing quality.
Keep in mind that all input Steps must be present in your Template. If one of them is missing (for instance it is rejected by a filter), no result is generated because the Robot waits indefinitely for all input Steps to be finished. Here's a demo that showcases Step bundling.
Group by originalSticking with the /file/compress Robot example, you can set
FieldsYou can be more discriminatory by only using files that match a field name by setting the
Use AsSometimes Robots take several inputs. For instance, the /video/merge Robot can create a slideshow from audio and images. You can map different Steps to the appropriate inputs. Example:
Sometimes the ordering is important, for instance, with our concat Robots. In these cases, you can add an index that starts at 1. You can also optionally filter by the multipart field name. Like in this example, where all files are coming from the same source (end-user uploads), but with different
For times when it is not apparent where we should put the file, you can use Assembly Variables to be specific. For instance, you may want to pass a text file to the /image/resize Robot to burn the text in an image, but you are burning multiple texts, so where do we put the text file? We use specify it via
||(required) String||Create a new Google service account.
Set its role to "Storage Object Creator". Choose "JSON" for the key file format and download
it to your computer. You will need to upload this file when creating your Template Credentials.
Go back to your Google credentials project and enable the "Google Cloud Storage JSON API" for it. Wait around ten minutes for the action to propagate through the Google network. Grab the project id from the drop down menu in the header bar on the Google site. You will also need it later on.
Now you can set up the storage.objects.create and storage.objects.delete permissions. The latter is optional and only required if you intend to overwrite existing paths.
Then create your associated Template Credentials in your Transloadit account and use the name of your Template Credentials as this parameter's value.
||The path at which the file is to be stored. This may include any available Assembly Variables.|
||The permissions used for this file. This can be
Our /google/store Robot can be used in combination with other Robots, to create powerful workflows unique to your use case. Here are a few example scenarios that you can try live on our website:
Transloadit is a SaaS with a subscription model.
Just like with any File Exporting Robot, you can use our /google/store Robot free of charge, as long as you also perform some processing (encoding, resizing, etc). If you do not, and Transloadit is just moving files, we still offer a considerable discount of 90%, effectively counting only every tenth byte of files that you export with /google/store.
Just like with your mobile plan, pricing goes down considerably when you commit to larger monthly volumes. You can adjust this every month. More info and available plans on our Pricing page.
Blog posts about the /google/store Robot
We wrote the following posts about the /google/store Robot on our blog:
- Re-loadit: the /google/store Robot March 1, 2019