Batch automation

Folder ingest automation for video libraries

Queue one encode job per video discovered in S3-compatible or Google Drive folders, with caps, metadata, output destinations, and webhook reconciliation.

Folder ingest is for imports, backfills, and customer libraries where the unit of work is not one hand-picked file but a controlled folder or prefix.

View API integrations Estimate pricing Developer settings

Folder ingest requestautomation

await client.onDemandIngestFolder({
  externalIdPrefix: "library-import-2026-07",
  sourceS3: {
    bucket: "customer-source",
    prefix: "incoming/"
  },
  outputDestination: "s3",
  outputS3: {
    bucket: "customer-output",
    prefix: "encoded/"
  },
  codec: "h264",
  resolution: "1080p",
  maxFiles: 50
});

Discover and queue supported video files from a folder or prefix.

Cap work with maxFiles while testing new workflows.

Group jobs with externalIdPrefix and metadata.

Reconcile every output independently through status reads or webhooks.

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
Choose a source folder in S3-compatible storage or Google Drive.
Step 2
Submit an ingest request with maxFiles, output destination, and shared encode settings.
Step 3
Store the returned job ids with your import or batch record.
Step 4
Use webhook events or status polling to update each asset as it completes.

Controlled discovery

Folder ingest queues video files only and supports maxFiles so initial runs remain bounded.

Shared encode recipe

Apply the same codec, resolution, audio, frame-rate, and scale policies across a discovered batch.

Per-job reconciliation

Each discovered file becomes a normal job with the same status, webhook, and report behavior as single encodes.

Automation questions

Is folder ingest a separate worker path?

No. Folder ingest creates normal durable jobs that are processed by the same Rust worker path.

Can I use Google Drive folders?

Yes, Google Drive folder workflows are supported for service-account based integrations.

How do I avoid a huge accidental batch?

Start with a small maxFiles value, verify output behavior, then raise the cap once the workflow is proven.

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.Batch video encodingQueue many videos from folders, asset libraries, imports, and customer batches with metadata, idempotency, webhooks, and storage destinations.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.

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.

Start Free Calculate Pricing