Google Cloud Storage + Transloadit

Build the integration

This Template reads a Google Cloud Storage object, resizes it, and writes a result under processed/ using the bucket’s IAM policy.

1. Create a private Google Cloud Storage bucket with uniform bucket-level access and grant a dedicated service account the required bucket permissions.
2. Save its JSON key and project values as Template Credentials named my_gcs_credentials.
3. Paste the Instructions into a Template and start an Assembly from that Template.

{
  "steps": {
    "imported": {
      "robot": "/google/import",
      "credentials": "my_gcs_credentials",
      "path": "incoming/photo.jpg"
    },
    "resized": {
      "robot": "/image/resize",
      "use": "imported",
      "width": 1200,
      "height": 1200,
      "resize_strategy": "fit"
    },
    "exported": {
      "robot": "/google/store",
      "use": "resized",
      "credentials": "my_gcs_credentials",
      "acl": null,
      "path": "processed/${file.url_name}"
    }
  }
}

Authentication

• Create a dedicated Google Cloud service account and grant the bucket permissions required by the workflow.
• For this round-trip recipe, the service account needs to list and read the input object and create the output object. Overwriting an existing path also requires delete permission.
• Download the service-account JSON key once, upload it into Transloadit Template Credentials, and protect and rotate it as a long-lived credential.

Limitations and operational notes

• Transloadit Template Credentials use an uploaded service-account JSON key; workload identity and Application Default Credentials are not available inside these Robots.
• The store Robot defaults to public-read. This recipe sets acl to null for a bucket with uniform bucket-level access, where IAM controls access and object ACL requests are rejected. Keep the bucket private through its IAM policy.
• Non-recursive directory imports only include direct descendants. Enable recursive and use pagination tokens for deeper or larger imports.