Integration

Connect Rebrandly to Rendi

When something happens in Rebrandly, your agent does the next thing in Rendi. Describe it in plain language and the automation is built, tested on every branch and kept running.

Rebrandly1 triggerRebrandly3 actionsRendi5 actions

Browse all apps

Build it

What do you want Rebrandly and Rendi to do together?

Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Or work from Claude Code

Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.

Connect Claude Code

Everything your agent can do with Rebrandly and Rendi

Triggers and actions 1 trigger · 8 actions

Trigger
New Branded Link
Triggers when a new branded link is created.
Action
Create Branded Link
Create a short branded link from any URL.
Action
Find Branded Link
Find your branded link.
Action
Update Branded Link
Update the destination url of a branded link.
Action
Delete File
Deletes one stored file in Rendi by file_id. DELETE /v1/files/{file_id}.
Action
Get File
Returns the details of one stored file — its status, download link, size, format and media properties.
Action
List Commands
Lists FFmpeg commands previously sent to Rendi. GET /v1/commands.
Action
Poll FFmpeg Command
Get the status of a previously submitted FFmpeg command
Action
Run FFmpeg Command
Submit an FFmpeg command for processing with input and output file specifications

Each app on its own

The other way round: Rendi to Rebrandly