What are Template Credentials?
Template Credentials are access credentials for storage providers, such as Amazon S3 or Google Storage, stored securely in a Transloadit account. Multiple Templates can reference the same credential record.
How Template Credentials work
Template Credentials are reusable account-side secret records that Templates can reference when a robot needs to read from or write to an external storage service. The workflow stores an indirection to the credential instead of embedding provider keys in Assembly Instructions or browser code. Access still depends on the external provider’s permissions, expiration rules, and resource policies. They connect Transloadit’s execution environment to storage operations and therefore require dependency tracking, least-privilege scoping, and planned rotation.
A client authenticates and submits files or references together with workflow instructions. The platform validates the request, schedules dependent operations, records state transitions, and exposes results through a response, polling endpoint, or notification.
Platform concepts become reliable only when their lifecycle is explicit. Authentication, idempotency, retries, timeouts, observability, quotas, and terminal states should be designed together rather than added after failures occur.
Key facts
- 1One credential record may be shared by several Templates, which simplifies rotation but turns its deletion, expiration, or permission loss into a multi-workflow failure domain.
- 2A successful credential lookup does not guarantee an operation will succeed: bucket policy, object path, region, provider-side role, and allowed actions can independently deny access.
- 3Keeping provider secrets behind a Template reference prevents their disclosure in submitted instructions, logs, or client bundles, but editors with account access still need appropriately limited privileges.
When Template Credentials matter
Reuse Template Credentials when several workflows need the same storage access, reducing duplicated secret configuration. Rotate or replace them carefully because one change may disrupt every dependent Template.
- Running repeatable upload, import, processing, AI, storage, and notification pipelines.
- Tracking long-running media work independently from an application request.
- Applying credentials, quotas, retries, and error policies consistently across integrations.
Working with platform at scale
Guidance that holds across every platform term in this glossary, not just Template Credentials.
What you gain
- Reusable workflows separate application intent from processing infrastructure.
- Stable job identifiers and lifecycle events improve observability and recovery.
- Managed queues and workers let products scale without embedding every media tool.
What it costs
- Synchronous responses are simple but keep connections open while long work executes.
- Aggressive retries improve recovery from transient faults but can duplicate work or overload a dependency.
- Higher concurrency reduces queue time until resource contention or a downstream limit becomes the bottleneck.
Answer these before production
- 1Define authentication, authorization, idempotency, retries, and terminal error behavior.
- 2Observe queue time, execution time, callbacks, and partial results with stable identifiers.
- 3Exercise malformed, duplicate, interrupted, and unauthorized requests before launch.
How Transloadit helps with Template Credentials
When Template Credentials are relevant to your workflow, you can hand the surrounding platform work to Transloadit instead of maintaining the processing stack yourself. Transloadit models file workflows as reusable Assembly Instructions. Upload, import, processing, AI, storage, delivery, status updates, and error handling can be composed without operating the underlying media tools yourself.
Support for a specific codec, container, parameter, or combination can vary by Robot and processing stack. Check the linked documentation for the exact inputs and outputs available for your use case.