New FFmpeg Command

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 deployed = await pd.triggers.deploy({
  id: "rendi-new-ffmpeg-command",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    rendi: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
  },
  webhookUrl: "https://example.com/webhooks/rendi",
})

console.log(deployed.id)

curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
  -H "Content-Type: application/json" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}" \
  -d '{
    "external_user_id": "{external_user_id}",
    "id": "rendi-new-ffmpeg-command",
    "webhook_url": "https://example.com/webhooks/rendi",
    "configured_props": {
      "rendi": { "authProvisionId": "apn_xxxxxxx" },
      "timer": { "intervalSeconds": 900 }
    }
  }'

MCP servers expose Rendi actions as on-demand tools.

New FFmpeg Command is an event source, so your application deploys it
with the Connect SDK or API and then either receives each event at a
webhook URL or retrieves events on demand with the trigger events API.