Run FFmpeg Command with Rendi API on New Requests (Payload Only) from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Rendi, HTTP / Webhook and 2,500+ other apps remarkably fast.

Trigger workflow on

New Requests (Payload Only) from the HTTP / Webhook API

Next, do this

Run FFmpeg Command with the Rendi API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a HTTP / Webhook trigger and Rendi action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Requests (Payload Only) trigger
1. Connect your HTTP / Webhook account
Configure the Run FFmpeg Command action
1. Connect your Rendi account
2. Configure Input File URL(s)
3. Configure Output File Name(s)
4. Configure FFmpeg Command
5. Optional- Configure Max Command Run Seconds
6. Optional- Configure Wait for Completion
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Requests (Payload Only) on HTTP / Webhook

Description:Get a URL and emit the HTTP body as an event on every request

Version:0.1.1

Key:http-new-requests-payload-only

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

import http from "../../http.app.mjs";

// Core HTTP component
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
N/A	`httpInterface`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

Action#

Run FFmpeg Command on Rendi

Description:Submit an FFmpeg command for processing with input and output file specifications. [See the documentation](https://docs.rendi.dev/api-reference/endpoint/run-ffmpeg-command)

Version:0.0.1

Key:rendi-run-ffmpeg-command

View on GitHub

Action Code#

import rendi from "../../rendi.app.mjs";
import { ConfigurationError } from "@pipedream/platform";
import { parseObject } from "../../common/utils.mjs";
import { axios } from "@pipedream/platform";
import fs from "fs";

export default {
  key: "rendi-run-ffmpeg-command",
  name: "Run FFmpeg Command",
  description: "Submit an FFmpeg command for processing with input and output file specifications. [See the documentation](https://docs.rendi.dev/api-reference/endpoint/run-ffmpeg-command)",
  version: "0.0.1",
  type: "action",
  props: {
    rendi,
    inputFiles: {
      type: "object",
      label: "Input File URL(s)",
      description: "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](https://docs.rendi.dev/api-reference/endpoint/run-ffmpeg-command) for more information",
    },
    outputFiles: {
      type: "object",
      label: "Output File Name(s)",
      description: "Dictionary mapping file aliases to their desired output file names, keys must start with 'out_'. [See the documentation](https://docs.rendi.dev/api-reference/endpoint/run-ffmpeg-command) for more information",
    },
    command: {
      type: "string",
      label: "FFmpeg Command",
      description: "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\\}\\}`",
    },
    maxCommandRunSeconds: {
      type: "string",
      label: "Max Command Run Seconds",
      description: "Maximum allowed runtime in seconds for a single FFmpeg command, the default is 300 seconds",
      optional: true,
    },
    waitForCompletion: {
      type: "boolean",
      label: "Wait for Completion",
      description: "Set to `true` to poll the API in 3-second intervals until the command is completed",
      optional: true,
      reloadProps: true,
    },
  },
  additionalProps() {
    if (this.waitForCompletion) {
      return {
        downloadFilesToTmp: {
          type: "boolean",
          label: "Download Files to /tmp",
          description: "Set to `true` to download the output files to the workflow's /tmp directory",
          optional: true,
        },
      };
    }
    return {};
  },
  async run({ $ }) {
    const inputFiles = parseObject(this.inputFiles);
    const outputFiles = parseObject(this.outputFiles);

    if (Object.keys(inputFiles).some((key) => !key.startsWith("in_"))) {
      throw new ConfigurationError("Input file keys must start with 'in_'");
    }
    if (Object.keys(outputFiles).some((key) => !key.startsWith("out_"))) {
      throw new ConfigurationError("Output file keys must start with 'out_'");
    }

    let response = await this.rendi.runFfmpegCommand({
      $,
      data: {
        input_files: inputFiles,
        output_files: outputFiles,
        ffmpeg_command: this.command,
        max_command_run_seconds: this.maxCommandRunSeconds,
      },
    });

    if (this.waitForCompletion) {
      const commandId = response.command_id;
      const timer = (ms) => new Promise((res) => setTimeout(res, ms));
      while (response?.status !== "SUCCESS" && response?.status !== "FAILED") {
        response = await this.rendi.getFfmpegCommand({
          $,
          commandId,
        });
        await timer(3000);
      }
      if (response?.status === "SUCCESS" && this.downloadFilesToTmp) {
        response.tmpFiles = [];
        for (const value of Object.values(response.output_files)) {
          const resp = await axios($, {
            url: value.storage_url,
            responseType: "arraybuffer",
          });
          const filename = value.storage_url.split("/").pop();
          const downloadedFilepath = `/tmp/${filename}`;
          fs.writeFileSync(downloadedFilepath, resp);

          response.tmpFiles.push({
            filename,
            downloadedFilepath,
          });
        }
      }

      if (response?.error_message) {
        throw new ConfigurationError(response.error_message);
      }
    }

    $.export("$summary", `FFmpeg command ${this.waitForCompletion
      ? "submitted and completed"
      : "submitted"} successfully`);
    return response;
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Rendi	`rendi`	`app`	This component uses the Rendi app.
Input File URL(s)	`inputFiles`	`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
Output File Name(s)	`outputFiles`	`object`	Dictionary mapping file aliases to their desired output file names, keys must start with 'out_'. See the documentation for more information
FFmpeg Command	`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\}\}`
Max Command Run Seconds	`maxCommandRunSeconds`	`string`	Maximum allowed runtime in seconds for a single FFmpeg command, the default is 300 seconds
Wait for Completion	`waitForCompletion`	`boolean`	Set to `true` to poll the API in 3-second intervals until the command is completed

Action Authentication#

Rendi uses API keys for authentication. When you connect your Rendi account, Pipedream securely stores the keys so you can easily authenticate to Rendi APIs in both code and no-code steps.

About Rendi#

Rendi is a REST API for FFmpeg. We take care of the cloud infrastructure, so you don't have to.

More Ways to Connect Rendi + HTTP / Webhook#

Other Popular Integrations#

Get FFmpeg Command Status with Rendi API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Rendi