What is a Robot?
A Robot is a specialized Transloadit processing unit that performs a particular file operation. Multiple Robots can be connected as steps in an Assembly to create a custom processing and encoding workflow.
How Robots work
Within an Assembly, a Robot represents one processing capability with a documented input contract, parameter set, and result shape. Step names provide the graph nodes, while input selectors connect a Robot to uploads or earlier results, allowing branching and fan-in workflows. The same Robot type can appear in multiple steps with different configurations. This abstraction lets orchestration describe media work declaratively, while Transloadit schedules the underlying execution and exposes each step’s outputs.
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
- 1A Robot’s type identifies the operation family, while the user-defined step name is how other Assembly steps refer to that configured instance.
- 2One step can consume results from selected earlier steps, so changing a dependency can alter both the files processed and when the step becomes runnable.
- 3Robot outputs retain step provenance in Assembly results, enabling clients to distinguish an original upload from resized, encoded, inspected, or exported derivatives.
When Robots matter
Select each Robot according to the required operation, then connect its inputs to earlier Assembly steps. An unsupported input type or incorrect step dependency can stop processing or produce an unintended result.
- 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 Robots.
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 Robots
When Robots 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.