Resources · Zapier integration

MediaSilo Zapier integrationAutomate MediaSilo with Zapier.

MediaSilo Zapier integration: 12 triggers and 3 actions to react the moment an asset, a project, a share or a team member changes in MediaSilo, and to create assets, projects and users from your other tools without copying anything by hand.

See the 15 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MediaSilo Zapier integration does for you

The MediaSilo Zapier integration lets Zapier, an automation service, follow what happens in your MediaSilo workspace and act on it. Every one of its 12 triggers is reported by MediaSilo itself, so nothing waits for a timer. On the way back, Zapier can create assets, projects and users for you.

A heads-up for every new file. New Asset tells your chat, your task list or your spreadsheet the moment an asset is created in MediaSilo. Updated Asset and Deleted Asset close the loop when it changes or goes away.

Access that follows the project. User Added to a Project, User Removed From Project and User Invited to a Project let you keep a list of who sees what, outside MediaSilo, without anyone updating it by hand.

Projects and files created from elsewhere. Create Project opens a project when work starts in another tool, and Create Asset pulls a file into it from a public link.

What Zapier does not do here: there is no search, so a Zap cannot look up an existing project or asset by name before acting. There is no action to update or delete either, only to create. And nothing that already exists in MediaSilo is replayed when you switch a Zap on. If you are comparing tools for this kind of job, see our Make 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 asset or a new share in MediaSilo. 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 creating a MediaSilo 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 MediaSilo triggers 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 Zap really costs

MediaSilo 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 triggersAll 12 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 to MediaSilo, whose 12 triggers are all instant.

Connect

Connect your MediaSilo account

  1. 01

    Open the Apps page

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

  2. 02

    Pick MediaSilo

    Type MediaSilo 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 in that tab and allow Zapier to use the account. The connection is saved once, and from then on every MediaSilo step of every Zap reuses it.

First Zap

Your first Zap: email the right person when a MediaSilo share is created

GoalEach new share in MediaSilo sends an email from your mail tool, but only for the shares that meet your condition.

  1. 01

    Build: start with MediaSilo

    Create a Zap, pick MediaSilo and the New Share event, choose your connection, then the Workspace where you are an Admin.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent shares 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 for text. The Zap is now multi-step.

  4. 04

    Add the email step

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

  5. 05

    Test, then publish

    Run each step once and read what came back. Then click Publish. Only shares created after that point will send an email.

Triggers

MediaSilo triggers

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

1

New Asset

Instant trigger

In Zapier“Triggers when a asset is created.”

Starts your Zap as soon as an asset is created in the chosen MediaSilo workspace, and hands what MediaSilo sends about it 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
your team should hear about a fresh upload in their chat without opening MediaSilo.
Watch out
files already in the workspace when you publish are not replayed; only new ones count.
2

Deleted Asset

Instant trigger

In Zapier“Triggers when a asset is deleted.”

Fires when a file disappears from your MediaSilo workspace, so whatever tracks it elsewhere can be cleaned up or flagged.

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 log every asset in a spreadsheet and want the matching row marked as gone.
Watch out
MediaSilo has no search on Zapier, so the Zap cannot look the file up again afterwards; check at the test what the trigger still carries.
3

Updated Asset

Instant trigger

In Zapier“Triggers when a asset is updated.”

Reacts each time an existing asset changes in the workspace, which lets another tool stay in step with MediaSilo instead of drifting apart.

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 review board elsewhere should reflect each change made to a file in MediaSilo.
Watch out
each run that reaches an action costs a task, so a filter keeps out the changes you do not care about.
4

New Project

Instant trigger

In Zapier“Triggers when a project is created.”

Goes off when someone opens a project in your MediaSilo workspace, giving the rest of your tools a 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
every new MediaSilo project should get a matching card in your task board.
Watch out
a Zap that also runs Create Project in the same workspace could start itself again, so keep the two apart.
5

Deleted Project

Instant trigger

In Zapier“Triggers when a project is deleted.”

Lets your Zap know that a project has been removed from the workspace, the signal you need to archive its trace somewhere else.

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 closed project in MediaSilo should also be closed in your planning sheet.
Watch out
the Workspace field is required, and only a workspace where you are an Admin will do.
6

Updated Project

Instant trigger

In Zapier“Triggers when a project is updated.”

Picks up changes made to an existing project, so a copy kept outside MediaSilo 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
project details shown in another tool should follow every edit made in MediaSilo.
Watch out
which project details come through is not listed anywhere on Zapier's side; check them at the test before mapping.
7

User Invited to a Project

Instant trigger

In Zapier“Triggers when a user is invited to a project.”

Starts the Zap when someone is invited to one of your MediaSilo projects, the step before they are added to it.

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 want a follow-up email sent to each invited person from your own mail tool.
Watch out
an invitation is not the same event as User Added to a Project; pick the one that matches the moment you care about.
8

User Added to a Project

Instant trigger

In Zapier“Triggers when a user is added to a project.”

Fires once a person actually becomes a member of a MediaSilo project, which makes it the right signal for an access log.

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 shared sheet should list who has access to which project, updated without manual edits.
Watch out
people added before the Zap is published never show up: the sheet only lists the additions that follow.
9

User Removed From Project

Instant trigger

In Zapier“Triggers when a user is removed from a project.”

Tells Zapier that a member has lost access to a project, the mirror of User Added to a Project.

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 access log should drop a name as soon as MediaSilo does, so nobody relies on an outdated list.
Watch out
pairing it with the added trigger means two Zaps on a free plan, since each Zap stops at two steps.
10

New Share

Instant trigger

In Zapier“Triggers when a share is created.”

Fires at the creation of a share in MediaSilo, the moment content leaves the team for someone outside it.

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 share should be logged, or announced to the person who has to review it, without anyone copying the link.
Watch out
check at the test which share details arrive before you build a message around them.
11

Share Expired

Instant trigger

In Zapier“Triggers when a share is expired.”

Reacts when a MediaSilo share expires, so the end of a share becomes an event your other tools can act on.

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 follow-up task should open for your team, or your share log should mark the share as expired.
Watch out
shares that expired before the Zap went live are not sent again.
12

New User Added to a Workspace

Instant trigger

In Zapier“Triggers when a new user is added to a workspace.”

Kicks off when a new person joins your MediaSilo workspace as a whole, not just one project inside it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every newcomer should receive a welcome message or appear in your team directory.
Watch out
a large batch of accounts added at once can be held back by Zapier's flood protection.
Actions

MediaSilo actions

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

1

Create Asset

Action

In Zapier“Creates a new asset.”

Pulls a file into a MediaSilo project from a link, under the filename you set, extension included.

When to use it
files that arrive as links in another tool should land in the right MediaSilo project.
Watch out
the source link must be publicly reachable, and the Workspace, filename and Project ID are all required.
2

Create Project

Action

In Zapier“Creates a new project.”

Opens a new project in the MediaSilo workspace you pick, ready to receive files and members.

When to use it
a job that starts in another tool should get its MediaSilo project at the same time.
Watch out
the Workspace is the required choice here. Create Asset later needs a Project ID, so check at the test whether this step hands one on.
3

Create User

Action

In Zapier“Creates a new user.”

Adds a person to your MediaSilo workspace from their email address, without anyone filling in the admin screens.

When to use it
a newcomer recorded in another tool should get their MediaSilo account right away.
Watch out
the Workspace and the email are both required, so map the email from a step that always has one.
When it breaks

When a MediaSilo Zap breaks

Zapier attaches no help article to MediaSilo, and no limit specific to the app is documented. What breaks is what breaks on any Zap.

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

  • Nothing from before the Zap shows up

    A Zap only reacts to what happens after you publish it. Assets, projects and users that already existed are not replayed, and 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 with Zapier?

A person reads every message.

FAQ

MediaSilo and Zapier: your questions

01Is the MediaSilo Zapier integration free?
Yes. MediaSilo is not one of the apps Zapier keeps for paid plans, so it works on the free plan. That plan gives you 100 tasks a month and as many Zaps as you want, with one limit: each Zap has two steps, one trigger and one action. New Asset followed by a chat message fits. As soon as you add a filter or a second action, for instance Create Project then Create Asset, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a MediaSilo Zap use?
One task for each action that succeeds, nothing for the rest. The MediaSilo trigger itself costs nothing, whichever of the 12 you pick. A Zap that posts a message for every New Share uses one task per share. A Zap that runs Create Project and then Create Asset uses two each time it goes through. If an action fails, it is not counted. Busy triggers such as Updated Asset can still add up, which is where a filter helps.
03Does MediaSilo send events to Zapier in real time?
Yes. All 12 MediaSilo triggers are instant: MediaSilo itself tells Zapier when the event happens, so the Zap starts right away. The interval grid of Zapier's plans, 15 minutes on Free down to 1 minute on Team and Enterprise, only concerns polling triggers, and MediaSilo has none. A Zap built on an instant trigger shows a lightning bolt in the editor. Your plan changes how many tasks you get, not how fast these triggers fire.
04What does it take to connect MediaSilo to Zapier?
A MediaSilo 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 and click Add connection, then sign in to MediaSilo in the new tab and grant access. Each trigger then asks for a Workspace, and it must be one where you are an Admin.
05Why does the Workspace list not show the workspace you expected?
Because every MediaSilo trigger asks for a Workspace where the connected account is an Admin. If you connected with a member account, the workspace you had in mind may not be one you administer. Connecting the account of an Admin of that workspace is the way around it. The actions also ask for a Workspace each time: Create Asset, Create Project and Create User all need one before anything else.
06What if the MediaSilo operation you need is not available?
The editor offers 15 MediaSilo operations: 12 triggers and 3 actions, all of the create kind. If what you need is to update or delete something, or to find an existing project before acting, MediaSilo on Zapier does not offer it as such. Look first at whether a trigger already carries the value you were going to search for, and check that at the test. Otherwise, the gap is real and the job needs another route.
07Zapier, Make or n8n for MediaSilo?
Pick by criteria, not by a ranking. On Zapier, MediaSilo comes with 12 instant triggers and 3 create actions, and no search: strong for reacting to events, thin for editing what exists. The other criterion is the length of your scenario, since any Zap beyond a trigger and one action needs a paid plan. Check what Make and n8n offer for MediaSilo on those same two points before deciding. Your own scenario is the test.
Same platform

Other docs you might need on this stack.

Browse all integrations