---
title: 'Push add-on'
description: 'How to use the Push add-on to send files from MediaLab to destinations such as FTP, SFTP, S3, Azure, YouTube or MediaLab Connect.'
url: https://www.medialab.co/support/core/downloading/push-add-on
---

# Push add-on

The Push add-on allows you to send files directly from MediaLab to external servers. Each push destination is linked to a cloud connection, and a variety of target destinations are supported:

- MediaLab Connect desktop application
- MediaLab accounts
- FTP/FTPS servers
- SFTP servers
- UDP uploads
- S3 storage
- Azure Blob storage
- YouTube

### Setting Up a Push Destination

1. Go to **Settings → Cloud integrations → Push destinations**.
2. Click Add and complete the form:
   - Name – the name of the push destination.
   - Cloud connection – select an existing one or create a new one.
   - Folder – specify the target folder on the external server.
   - Overwrite existing files – decide whether existing files should be replaced.
   - Users – choose which users receive notifications when files are pushed.

3. Click Save to add the new profile.

Depending on the chosen protocol, additional fields may need to be completed.

Once configured, you can send files to this destination from any folder using the Push button.

**Note:** Note: Only administrators can configure push destinations. The Push add-on must be enabled for your Lab — contact support if it is not available.

### Setting Up Auto-Push Rules

Auto-push rules let you automatically forward files to a push destination when they meet specific
conditions. This is useful for building automated push workflows, where files arriving in a folder
are sent on to an external server without any manual action.

1. Go to **Settings → Workflows → Auto-push rules**. This page lists the rules of all your push destinations.
   The auto-push icon next to a push destination opens it for that destination only.
2. Click the **+** button and choose the **Push destination**.
3. Define the rule, including:
   - **Folder** – the source folder the file must arrive in.
   - **File format** – choose which version of the file to push. This setting does not filter
   which incoming files trigger the rule; it determines what gets sent to the
   destination, either the original source file or MediaLab’s transcoded MP4.
   - **Metadata** – optionally include metadata alongside the pushed file. Custom
   metadata templates can also be linked to a push destination — contact the
   helpdesk to set this up.
   - **Additional conditions** – any further requirements the file must satisfy before
   being pushed like approval status.
4. Click **Add** to activate the rule.

<br/> 

You can attach one or more auto-push rules to a folder, allowing the same incoming file to be
routed to multiple destinations when needed. FTP upload accounts can be created separately
and linked to a folder, so files uploaded through those accounts will trigger the auto-push rules
set on that folder.

Administrators can manage the rules of all push destinations. Media managers can manage the rules of the
destinations they are allowed to push to.

**Note:** Each auto-push rule can only be triggered once per file, so the same file will not be
pushed repeatedly to the same destination. Auto-push rules also only apply to files added after
the rule has been saved — existing files in the folder are not retroactively pushed until the auto-push rules are evaluated.

### Push queue priority

When many files are waiting to be pushed, you can decide which of your own pushes go first, per folder or for a single push. See [Push queue priority](https://www.medialab.co/support/core/transcoding/push-queue-priority).
