# Add video jobs to your Activepieces flows

The Rendobar piece runs FFmpeg commands and timeline videos as flow steps. A platform admin installs it from npm as a private piece, and the flow waits up to 30 days for the file.

912 downloads · Private piece · v0.2.1 · MIT · Activepieces 0.36.1+

Page: https://rendobar.com/integrations/activepieces/ · Get the piece: https://www.npmjs.com/package/@rendobar/piece-rendobar · Read the docs: https://rendobar.com/docs/automation/activepieces

```
@rendobar/piece-rendobar
```

- Status: Private piece, installed from npm
- Built by: Rendobar
- Package: `@rendobar/piece-rendobar`
- Version: 0.2.1, MIT licence
- Works with: Activepieces 0.36.1 or later, self-hosted or on a Cloud plan with private pieces
- Pricing: Free
- Category: Automation

## Overview

Install the piece and every Rendobar job becomes a flow step: [FFmpeg commands](https://rendobar.com/ffmpeg/), [timeline videos](https://rendobar.com/compose/), captions and compression. Run a Media Job loads the live job type list and builds its form from each type's schema, so a new job type shows up without a piece update. A long render doesn't count toward the run timeout. The flow pauses, and the job's callback resumes it, for up to 30 days. The Finished Job trigger starts a flow when a job ends. The piece isn't in the Activepieces catalog yet, so an admin installs it from npm.

## Run a Media Job

- Job Type: compress.target
- Variant: Not used by this job type
- Wait for the Result: On
- Download the Output File: Off
- Maximum Wait (seconds): 300
- Fail This Step if the Job Fails: On

## Set up

1. **Install.** In the platform admin, open Pieces, choose Install Piece and enter the piece's npm package name.

```
@rendobar/piece-rendobar
```

2. **Connect.** Add a connection with a [Rendobar API key](https://app.rendobar.com/api-keys?create=1&name=Activepieces), which the piece checks when you save. A key with narrowed scopes needs four of them.

```
jobs:write assets:write billing:read webhooks:write
```

3. **Run a job.** Add Run a Media Job and pick a job type. The form builds itself from the job's live schema, and the next step reads the file URL.

```
{{step_1.file_url}}
```


## Reference

### Package

- @rendobar/piece-rendobar 0.2.1, MIT
- Needs Activepieces 0.36.1 or later
- Not in the Activepieces catalog yet: install it from npm as a private piece

### Actions (11)

- Run a Media Job
- Upload File
- Get Job
- Find Jobs
- Get Job Logs
- Get Account
- Cancel Job
- Share Output
- Find Storage Connections
- List Storage Files
- Custom API Call

### Triggers

- Finished Job (webhook): Succeeded only, Failed only, Any finished job, or Storage deliveries settled
- Finished Job (Polling): Succeeded only, Failed only, or Any finished job, checked every few minutes, for an instance Rendobar can't reach

### Run a Media Job settings

- Job Type, Variant, Input Media and Parameters, built from the job type's live schema
- Deliver To and Delivery Folder or Path: write the output to connected buckets
- Wait for the Result (on): pause the flow until Rendobar's callback
- Download the Output File (off): attach the file to the step, capped at 10 MB on Cloud
- Maximum Wait (300 s): the polling limit when the callback can't reach the instance
- Fail This Step if the Job Fails (on), Idempotency Key (derived per run when empty)

### Connection

- API key starting rb_, checked on save
- Narrowed keys need jobs:write, assets:write, billing:read, and webhooks:write for Finished Job

### Waiting

- A paused flow resumes on Rendobar's callback, up to 30 days
- If the callback can't reach the instance, the step polls up to Maximum Wait (300 s by default)
- Activepieces Cloud caps a step file at 10 MB

## Questions

### Does the Rendobar piece work on Activepieces Cloud?

Custom pieces are a paid Activepieces Cloud feature: when we checked on 26 September 2026, the pricing page listed private pieces on the Ultimate plan. On a self-hosted instance, an admin installs it from npm.

### Does a long render hit the Activepieces run timeout?

No. Run a Media Job pauses the flow and Rendobar's callback resumes it. A paused flow doesn't count toward the run timeout, and it can stay paused for up to 30 days.

### What if Rendobar can't reach my self-hosted Activepieces?

Run a Media Job then polls for up to Maximum Wait, 300 seconds by default, and returns the job as it stands. The job keeps running either way. Use Finished Job (Polling) to pick up the result, and set `AP_FRONTEND_URL` to a public HTTPS address to get the pause back.

### How do I start a flow when a Rendobar job finishes?

Use the Finished Job trigger. It fires when a job succeeds by default, or on failure, on any finish, or when storage deliveries settle. It needs an API key with the `webhooks:write` scope.

## Resources

- [Docs](https://rendobar.com/docs/automation/activepieces): Install the piece, connect a key, and how a paused flow resumes.
- [npm](https://www.npmjs.com/package/@rendobar/piece-rendobar): @rendobar/piece-rendobar, the name to enter under Install Piece.
- [GitHub](https://github.com/rendobar/activepieces-piece): The piece's code and release notes, MIT licensed.
- [Callbacks](https://rendobar.com/docs/guides/callbacks): The per-job URL a paused flow listens on.
- [Storage](https://rendobar.com/docs/storage): The buckets Deliver To writes the output to.

## More

- [Video processing in Activepieces, without polling](https://rendobar.com/blog/activepieces-video-processing/)
- [FFmpeg recipes](https://rendobar.com/ffmpeg/recipes/)