Resources · Zapier integration

MediaSilo Legacy Zapier integrationAutomate MediaSilo Legacy with Zapier.

MediaSilo Legacy Zapier integration: 10 triggers and 4 actions to react the moment an asset, a comment, a project or a QuickLink changes, and to create files, projects and users or invite people without opening the admin screens.

See the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MediaSilo Legacy Zapier integration does for you

The MediaSilo Legacy Zapier integration lets Zapier, an automation service, follow your video management platform and act on what happens there. All 10 of its triggers are reported by MediaSilo Legacy itself, so nothing waits for a scheduled check. On the way back, Zapier can create files, projects and users, and invite people to a project.

Feedback that reaches people. New Comment fires each time someone comments on an asset, so the comment can land in the chat or the task list of whoever has to act on it, instead of waiting for them to log in.

A file pipeline that starts at the right moment. Asset Uploaded and Ready tells your other tools a file is uploaded and usable, which is the cue for anything that works on the file itself. Create File goes the other way and brings a file in from a public link.

Projects staffed without admin work. Create Project opens a project with a name, and Invite User to Project sends an invitation to an email address on a project you point to.

What Zapier does not do here: there is no search, so a Zap cannot find an existing project by name to get its ID. There is no action to update or delete either. And nothing that already exists in MediaSilo Legacy is replayed when you switch a Zap on. To weigh Zapier against other tools, see our n8n vs Zapier comparison.

Vocabulary

Zapier words, in one minute

Seven words come back all over this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap, such as a new comment in MediaSilo Legacy. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or moves something, like inviting a user to a project.
Task
The unit Zapier bills. One action that your Zap completes successfully is one task, and your plan counts those.
Instant vs polling
An instant trigger is reported by the app the moment it happens; a polling one is checked on a timer. All 10 triggers here are instant.
Filter
A step that lets the Zap go on only when what arrived meets a condition you set, and stops it there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
Cost

What a MediaSilo Legacy Zap really costs

MediaSilo Legacy is not one of the apps Zapier keeps for paid plans: it works on the free plan.

  • Free plan100 tasks a month, unlimited two-step Zaps
  • TriggerNever billed
  • Failed actionNot counted against the plan
  • MediaSilo Legacy triggersAll 10 instant, on every plan

The trigger never costs a task. Each action that succeeds counts once, and one that fails is not billed. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below is how often Zapier checks a polling trigger on each plan; it does not apply here, since the 10 MediaSilo Legacy triggers are all instant.

Connect

Connect your MediaSilo Legacy account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a MediaSilo Legacy account, plus read or write access on anything you do not own yourself but want the Zap to touch.

  2. 02

    Pick MediaSilo Legacy

    Type MediaSilo Legacy in the search box of the dialog, select it, then click Add connection at the bottom of it. A new browser tab opens on the MediaSilo side.

  3. 03

    Sign in and grant access

    Sign in to MediaSilo Legacy in that tab and allow Zapier to use the account. The connection is saved once, and from then on every step of every Zap that uses the app reuses it.

First Zap

Your first Zap: send each new MediaSilo Legacy comment to your team chat

GoalEvery comment left on an asset becomes a message in your team chat, but only when it meets the condition you set.

  1. 01

    Build: start with the comment

    Create a Zap, pick MediaSilo Legacy as the app and New Comment as the event, then choose the connection you have just added.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent comments of the account, so you map the next steps on a real one, not on a guess.

  3. 03

    Add a filter

    Click the plus icon, add Filter, then fill the three boxes: the field to look at, the rule, the value. Use a text rule on text. The Zap is now multi-step.

  4. 04

    Add the chat step

    Add your chat tool as the action and map what the trigger returned into the message. Check at the test which comment details actually come through.

  5. 05

    Test, then publish

    Run each step once and read what came back. Then click Publish. Only comments posted after that point will reach the chat.

Triggers

MediaSilo Legacy triggers

10 events start a Zap when something happens in MediaSilo Legacy, and 10 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Asset Is Deleted

Instant trigger

In Zapier“Triggers when an asset is deleted by a MediaSilo user.”

Fires when a MediaSilo user removes an asset, so any trace of that file in another tool can be flagged or cleaned up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you keep an inventory of assets in a spreadsheet and the matching row should be marked as removed.
Watch out
there is no search on this app, so check at the test what the trigger still carries about the deleted file.
2

Asset Uploaded and Ready

Instant trigger

In Zapier“A new asset is uploaded and is ready.”

Starts your Zap once a new file has been uploaded and is ready to use, the safe moment for any step that works on the file.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a reviewer should get the file the moment it can actually be opened.
Watch out
prefer it to New Asset whenever a later step needs the file itself rather than the news of an upload.
3

Asset Updated

Instant trigger

In Zapier“Triggers when an asset is changed by a MediaSilo user.”

Reacts each time a MediaSilo user changes an existing asset, which keeps a copy of its details elsewhere in step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a tracking board outside MediaSilo should reflect each edit made to a file.
Watch out
every run that reaches an action costs a task, so a filter keeps you from paying for changes you do not care about.
4

Changed Project

Instant trigger

In Zapier“Triggers when a project is changed in MediaSilo.”

Picks up edits made to an existing MediaSilo project, so a project sheet held in another tool does not go stale.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your planning tool shows project details that should follow every change made in MediaSilo Legacy.
Watch out
Zapier does not list which project details come through; check them at the test before mapping.
5

Deleted Project

Instant trigger

In Zapier“Triggers when a new project is deleted in MediaSilo.”

Lets your Zap know that a project has been removed in MediaSilo Legacy, the signal to close its trace elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a project that disappears from MediaSilo should be archived in your task board too.
Watch out
projects deleted before the Zap is published are not replayed: your board only follows the deletions that come after.
6

New Asset

Instant trigger

In Zapier“A new asset is uploaded. This event gets triggered before an actual asset exists and should not be used to trigger File actions.”

Goes off on a new upload, at a point where the asset itself does not exist yet in MediaSilo Legacy.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you only want to know that an upload is coming, for a log or a heads-up message.
Watch out
MediaSilo says plainly that it should not start file actions, since the asset is not there yet. Use Asset Uploaded and Ready for those.
7

New Comment

Instant trigger

In Zapier“Triggers when someone comments on an asset in MediaSilo.”

Fires when someone comments on an asset in MediaSilo Legacy, handing the comment to the next steps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
feedback on a file should reach the person who acts on it in their chat or task list.
Watch out
a busy review can bring many comments, and each one that reaches an action costs a task; a filter narrows them down.
8

New Project

Instant trigger

In Zapier“Triggers when a new project is created in MediaSilo.”

Kicks off when a project is created in MediaSilo Legacy, the cue that a new piece of work has begun.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
each new project should get a matching card in your task board, or an automatic invitation for a fixed teammate.
Watch out
a Zap that also runs Create Project could set itself off again, so keep the two apart.
Actions

MediaSilo Legacy actions

MediaSilo Legacy gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create File

Action

In Zapier“Creates a new asset based on a publicly accessible URL.”

Brings a file into a MediaSilo Legacy project from a link anyone can open.

When to use it
files that arrive as links in another tool should land in the right project without a manual upload.
Watch out
the Project ID and the source link are required, and the link must be publicly accessible.
2

Invite User to Project

Action

In Zapier“Invites an user (by email) to a project.”

Sends an invitation to an email address for a given project, so the person can join it.

When to use it
every new project should automatically include the same teammate.
Watch out
both the Project ID and the email are required; map the ID from the trigger if it carries one, and check that at the test.
3

Create Project

Action

In Zapier“Creates a new project with a name and description.”

Opens a new project in MediaSilo Legacy with a name, and a description if you give one.

When to use it
a job that starts in another tool should get its MediaSilo project at the same time.
Watch out
only the name is required. Check at the test whether the step hands on a project ID for later steps.
4

Create User

Action

In Zapier“Creates a user.”

Opens a MediaSilo Legacy account with a user name, a password, a first name, a last name and an email, and can email the person their account details.

When to use it
a newcomer recorded in another tool should get access straight away.
Watch out
the user name must be unique, and the password needs at least 8 characters with a number, an upper case letter, a lower case letter and a special character.
When it breaks

When a MediaSilo Legacy Zap breaks

Zapier attaches no help article to MediaSilo Legacy, and no limit specific to the app is documented. Beyond the New Asset trap, what breaks is what breaks on any Zap.

Four cases are worth knowing. When a run looks wrong, rerun the step test and read what came back, then see our Zapier troubleshooting guide.

  • A file step started too early

    New Asset fires before the asset exists, and MediaSilo warns it should not start file actions. Switch the trigger to Asset Uploaded and Ready.

  • Nothing from before the Zap shows up

    A Zap only reacts to what happens after you publish it. Existing assets, comments and projects are not replayed; moving them is a separate job.

  • The Zap keeps restarting itself

    A Zap that writes into the very place its own trigger watches can set itself off again and again, and burn through your task count fast.

  • A bulk change goes quiet

    When a trigger suddenly sends a huge batch, after an import or a migration, Zapier's flood protection can hold it back.
Need help

Need help automating MediaSilo Legacy with Zapier?

A person reads every message.

FAQ

MediaSilo Legacy and Zapier: your questions

01Is the MediaSilo Legacy Zapier integration free?
Yes. MediaSilo Legacy is not one of the apps Zapier keeps for paid plans, so it runs on the free plan. That plan gives you 100 tasks a month and as many Zaps as you like, each limited to two steps: one trigger and one action. Asset Uploaded and Ready followed by a chat message fits. A filter, or a second action such as Create Project followed by Invite User to Project, makes the Zap multi-step, and that needs a paid plan.
02How many tasks does a MediaSilo Legacy Zap use?
One task per action that succeeds, and nothing else. Whichever of the 10 triggers you pick, it costs nothing. A Zap that forwards each New Comment to your chat uses one task per comment. A Zap that creates a project and then invites a teammate uses two each time it runs through. An action that fails is not counted. On lively triggers such as New Comment or Asset Updated, a filter keeps the count down.
03Does MediaSilo Legacy send events to Zapier in real time?
Yes. All 10 triggers are instant: MediaSilo Legacy tells Zapier when the event happens, and the Zap starts right away. The plan intervals, 15 minutes on Free down to 1 minute on Team and Enterprise, only concern polling triggers, and this app has none. In the editor, a Zap built on an instant trigger shows a lightning bolt. Your plan changes how many tasks you get, not how fast these triggers fire.
04What does it take to connect MediaSilo Legacy to Zapier?
A MediaSilo Legacy account, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection takes three moves: open the Apps page and click + Add connection, search for MediaSilo Legacy and click Add connection, then sign in in the new tab and grant access. For Create File and Invite User to Project, also have the target project and its ID ready.
05Why should New Asset not start a file action?
Because it fires on a new upload before the asset actually exists in MediaSilo Legacy, and MediaSilo itself says it should not be used to trigger file actions. At that point, the file a later step would work on is not there yet. Use Asset Uploaded and Ready instead: it fires once the file is uploaded and ready. Keep New Asset for a log or a heads-up that an upload is on its way.
06What if the MediaSilo Legacy operation you need is not there?
The editor offers 14 operations for this app: 10 triggers and 4 actions, which create files, projects and users or invite people. Updating or deleting something, or looking up an existing project to get its ID, is not part of it. Before giving up, check whether one of the triggers already carries the value you wanted, the test shows it. If it does not, the gap is real and the job needs another route.
07Zapier, Make or n8n for MediaSilo Legacy?
Choose by criteria, not by a ranking. On Zapier, MediaSilo Legacy brings 10 instant triggers and 4 create or invite actions, with no search: good for reacting to events, limited for editing what exists. The second criterion is how many steps your scenario takes, since anything beyond a trigger and one action needs a paid plan on Zapier. Check Make and n8n on those same two points with your own scenario before you decide.
Same platform

Other docs you might need on this stack.

Browse all integrations