Rendi ACTION
Run FFmpeg Command
Submit an FFmpeg command for processing with input and output file specifications. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Rendi account once, then configure and run Run FFmpeg Command 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: "rendi-run-ffmpeg-command",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
rendi: { authProvisionId: "apn_xxxxxxx" },
inputFiles: "Input File URL(s)",
outputFiles: "Output File Name(s)",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "rendi-run-ffmpeg-command",
"configured_props": {
"rendi": { "authProvisionId": "apn_xxxxxxx" },
"inputFiles": "Input File URL(s)",
"outputFiles": "Output File Name(s)"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "rendi",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "rendi-run-ffmpeg-command",
arguments: {
inputFiles: "Input File URL(s)",
outputFiles: "Output File Name(s)",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
inputFiles Input File URL(s) | object | Dictionary mapping file aliases to their publicly accessible paths, file name should appear in the end of the url, keys must start with 'in_'. You can use public file urls, google drive, dropbox, rendi stored files, s3 stored files, etc. as long as they are publicly accessible. See the documentation for more information Required |
outputFiles Output File Name(s) | object | Dictionary mapping file aliases to their desired output file names, keys must start with 'out_'. See the documentation for more information Required |
command FFmpeg Command | string | FFmpeg command string using {{alias}} placeholders for input and output files. {{}} is a reserved string, instead you can use \{\{\}\} , so for example {{in_1}} should be \{\{in_1\}\}. Example: -i \{\{in_1\}\} \{\{out_1\}\} Required |
maxCommandRunSeconds Max Command Run Seconds | string | Maximum allowed runtime in seconds for a single FFmpeg command, the default is 300 seconds Optional |
waitForCompletion Wait for Completion | boolean | Set to true to poll the API in 3-second intervals until the command is completed Optional |
syncDir SyncDir | dir | 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
- rendi-run-ffmpeg-command
- Version
- 0.0.3
- App
- Rendi
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗