​

Rendi and Make Integration

Rendi’s integration with Make enables seamless automation of video processing workflows by combining Rendi’s FFmpeg capabilities with Make’s robust automation platform.

​

Tutorial - Running FFmpeg Commands in Make using Rendi

The tutorial below shows how to create a make scenario that tracks a google drive folder, when a new video file is uploaded to it, make it publicly available and send the video file to a command in Rendi that turns it into a GIF, then it saves the stored GIF URL in a google sheet. The tutorial also shows how to use Rendi’s webhooks feature in Make and how to delete stored files in Rendi.

​

Integration Details

You can find our official integration on Make’s marketplace: Make - Rendi - FFmepg API To establish the integration between Make and Rendi:

1. Obtain your API key from the Rendi dashboard
2. Create a new connection in Make
3. Use your Rendi API key to authenticate the connection

​

Available Actions

Rendi provides two native actions within Make:

1. Run FFmpeg Command: The primary action for triggering video processing tasks. The full documentation for this action can be found in API reference - run FFmpeg command endpoint
2. Make API Call: For additional API interactions

These actions are accessible through Make’s module search widget when building your automation scenarios.

​

Handling Curly Brackets {{}}

Make uses curly brackets {{}} as special characters for its stored variables. When using these brackets in Rendi FFmpeg commands, you need to escape them with backslashes, like this: \{\{\}\}. Here’s an example of a configured FFmpeg command in Make:

​

Processing Workflow

After submitting a command to Rendi, you have two options to track the processing status:

1. Polling Method: Monitor the job status using our API reference - poll command endpoint
2. Webhook Integration: Configure webhooks to automatically trigger Make workflows upon job completion. See our webhooks documentation for details.