View as Markdown
Renderio icon

Renderio ACTION

Run Multiple FFmpeg Commands

Execute multiple independent FFmpeg commands in one request. See the documentation
  • Action
  • Writes data
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Renderio account once, then configure and run Run Multiple FFmpeg Commands from your backend or agent.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "renderio-run-multiple-ffmpeg-commands",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    renderio: { authProvisionId: "apn_xxxxxxx" },
    commands: "Commands JSON Array",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Run Multiple FFmpeg Commands inputs
Property Type Description
commands Commands JSON Array string
JSON array of command objects. Each object should include input_files, output_files, and ffmpeg_command. Example: [{"input_files":{"in_video":"https://example.com/video.mp4"},"output_files":{"out_video":"output.mp4"},"ffmpeg_command":"-i {{in_video}} {{out_video}}"}].
Required

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
renderio-run-multiple-ffmpeg-commands
Version
0.0.2
App
Renderio
Authentication
API key
Read-only
No
Destructive
No
Open world
Yes