Tigris + Transloadit

Build the integration

This Template reads an image from Tigris, converts it to WebP, and stores a private result under processed/.

1. Create a Tigris bucket and S3-compatible access credentials.
2. Save the bucket, endpoint, region, key, and secret as my_tigris_credentials.
3. Paste the Instructions into a Template and start an Assembly from that Template.

{
  "steps": {
    "imported": {
      "robot": "/tigris/import",
      "credentials": "my_tigris_credentials",
      "path": "incoming/photo.jpg"
    },
    "converted": {
      "robot": "/image/resize",
      "use": "imported",
      "format": "webp",
      "width": 1600,
      "resize_strategy": "fit"
    },
    "exported": {
      "robot": "/tigris/store",
      "use": "converted",
      "credentials": "my_tigris_credentials",
      "acl": "private",
      "path": "processed/${file.basename}.webp"
    }
  }
}

Authentication

• Create S3-compatible credentials for the target Tigris bucket and keep the access key and secret in Transloadit Template Credentials.
• Use the canonical https://t3.storage.dev endpoint for new integrations and auto as the region unless your Tigris setup specifies another value.
• Use a credential dedicated to the bucket and workflow rather than reusing an application-wide key.

Limitations and operational notes

• Tigris is accessed through its S3-compatible API, so the workflow is limited to operations exposed by the Transloadit import and store Robots.
• The store Robot defaults to public-read. Set acl to private explicitly when outputs must not be public.
• Large recursive imports need pagination planning, and concurrent changes under the imported prefix can shift page contents.