Capped folder ingest
Use maxFiles to keep batch submits predictable while testing new pipelines or customer imports.
Library automation
Batch video encoding for folders, libraries, and scheduled workflows
Queue many videos from folders, asset libraries, imports, and customer batches with metadata, idempotency, webhooks, and storage destinations.
Batch work is where automation matters most. Convertrilo lets teams process folders and media libraries without asking someone to babysit uploads in a dashboard.
Queue a folder ingestautomation
await client.onDemandIngestFolder({
externalIdPrefix: "customer-import-2026-07",
sourceS3: {
bucket: "customer-source",
prefix: "incoming/"
},
outputDestination: "s3",
outputS3: {
bucket: "customer-output",
prefix: "encoded/"
},
codec: "h264",
resolution: "1080p",
maxFiles: 25
});Queue one job per video from a controlled source prefix.
Group jobs with external id prefixes and shared metadata.
Send each output to the right destination without manual downloads.
Use webhooks to reconcile large batches as each file completes.
Workflow
Built for jobs that should run without a human babysitting a tab
Each automation page maps to the same production path: API request, durable job row, queue, Rust worker, storage upload, terminal event, and reconciliation.
- Step 1
Pick a source folder or prefix in customer-owned storage.
- Step 2
Submit a capped ingest request with codec, resolution, and destination policy.
- Step 3
Track each returned job id independently through status or webhooks.
- Step 4
Update your library, CMS, or customer dashboard as outputs complete.
Batch reconciliation
External ids and metadata keep each queued job connected to the original asset, tenant, or campaign.
Automation-ready retries
Idempotency keys and webhook history make batch workflows easier to restart safely.
Automation questions
Can Convertrilo process every file in a folder automatically?
Folder ingest can discover video files from supported storage sources and queue one job per file, with maxFiles available as a safety cap.
How should I track a batch after submission?
Store returned job ids with your batch record, use externalIdPrefix for stable naming, and reconcile terminal states through webhooks or bulk status reads.
Is batch encoding only for S3?
S3-compatible folder ingest is the most automation-friendly path today, and Google Drive folder workflows are also supported for service-account based integrations.
Related automation pages
API integration guideSDK, idempotency, S3, Google Drive, and webhook workflows.Video encoding APICreate video encoding jobs from your backend with API keys, idempotency, metadata, priority queues, webhooks, and storage destinations you control.Video encoding CLIAutomate video compression from terminals, deployment jobs, content pipelines, and scheduled scripts with a Convertrilo CLI workflow.Video encoding MCPConnect Convertrilo to MCP clients so agents can create encoding jobs, check status, wait for completion, cancel work, and inspect token balance.Video encoding webhooksReceive signed job.completed, job.failed, and job.canceled events so your app can publish assets, update records, and notify customers automatically.Automated S3 video compressionCompress videos from S3-compatible storage and write finished MP4 outputs back to your own bucket with API keys, idempotency, and worker execution reports.Agent video workflow automationGive MCP-capable agents a narrow video encoding tool surface for creating jobs, waiting for completion, inspecting reports, and handing outputs back to your workflow.Folder ingest automationQueue one encode job per video discovered in S3-compatible or Google Drive folders, with caps, metadata, output destinations, and webhook reconciliation.
Start with a real estimate
Choose your codec, resolution, FPS, bitrate, quality, and optimization settings. Convertrilo shows the NEU estimate before credits are reserved, and failed jobs release reserved credits back to your balance.