Event-driven encoding

Video encoding webhooks for event-driven media pipelines

Receive signed job.completed, job.failed, and job.canceled events so your app can publish assets, update records, and notify customers automatically.

Polling works for simple scripts, but production products need events. Convertrilo webhooks let your app react when long-running video work changes state.

Open webhook settingsView API integrationsDeveloper settings
Verify a webhook signatureautomation
const expected = crypto
  .createHmac("sha256", webhookSecret)
  .update(rawBody)
  .digest("hex");

if (signature !== expected) {
  throw new Error("Invalid Convertrilo webhook signature");
}

Publish encoded files only after the worker has completed upload.

Update CMS, LMS, DAM, or SaaS records from terminal job events.

Diagnose downstream delivery failures with webhook history.

Avoid brittle long-polling workers in your own product.

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.

  1. Step 1

    Create a managed webhook endpoint from developer settings.

  2. Step 2

    Store the one-time signing secret in your backend secret manager.

  3. Step 3

    Verify each incoming event before trusting the payload.

  4. Step 4

    Update your asset record, notify users, or trigger follow-up automation.

Signed delivery

Managed webhooks include HMAC signatures so your receiver can reject spoofed job events.

Delivery attempts

Inspect delivery status, response codes, and retry timing when your receiver is unavailable.

Job metadata included

Use external ids and metadata in webhook payloads to connect events back to your own records.

Automation questions

Which webhook events should I listen for first?

Most integrations start with job.completed and job.failed. Add job.canceled when your product exposes user-driven cancellation.

Are one-off webhook URLs and managed webhooks the same?

No. One-off callback URLs are useful for simple jobs, while managed webhooks provide signed delivery and delivery history.

Should I still poll status when using webhooks?

For critical workflows, use webhooks as the trigger and status reads as a reconciliation fallback when delivery fails or a receiver is redeployed.

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.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.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.

Start FreeCalculate Pricing