Zapier lets you create integrations between MediaSilo and other apps without any coding. An event in one app triggers an action in another app, allowing you to automate certain tasks and save time. In this article, we’ll show you how to connect an app to MediaSilo using Zapier, and we’ll review the types of data you can automatically push from MediaSilo to other apps.
For security reasons, Zapier integrations are not available to users who access MediaSilo using SSO. |
- How to Set Up a Zap
- MediaSilo Events as Triggers
- MediaSilo Events as Actions
- Pushing Event Data from MediaSilo to Other Apps
How to Set Up a Zap
In this section, we’ll create a “Zap” (a Zapier automation) from scratch. The steps we cover here can be applied to any number of automations where an event in MediaSilo triggers an event in another app.
In this particular example, our new Zap will add a row to a Google spreadsheet whenever anyone uploads a file to our MediaSilo workspace. As a kind of activity log, each row will list the file name, uploader, the date it was uploaded, and the project where it was uploaded.
To get started, please log in to your Zapier account. If you haven’t signed up yet, you can visit zapier.com to create a free account. |
First, go to your Zapier dashboard and click the orange Create Zap button.
You can give this Zap a name in the top left.
Next, click Trigger to choose an event in MediaSilo that will trigger the automation.
A window will open, where you can search for and select a trigger app; for this example, please choose MediaSilo.
Next, you need to choose the exact event in MediaSilo that will kick off the automation. Let’s choose New Asset from the Event menu, since we want the automation to run each time a file is uploaded.
After you select the trigger event, click Continue.
To finish setting up the trigger, Zapier needs to connect to a specific MediaSilo workspace. Click Choose to connect your MediaSilo account.
If you’re not logged in to MediaSilo, a popup window will ask you to log in, in order to authenticate your account. Once you log in, click Continue.
As a MediaSilo user, you may have access to more than one workspace. In the next step, choose the workspace where you want to use this Zap.
After you select a workspace, click Continue.
You can now test the trigger to make sure Zapier is connected to your MediaSilo workspace.
A message confirms if Zapier was able to connect to MediaSilo by loading a test record. This record contains test content that does not reflect any files in your actual account. You’ll also see a checkmark over the MediaSilo icon on the left side of the page. To finish setting up the trigger, click Continue with selected record.
Now it’s time to set up the end result– the action that will take place each time a file is uploaded to MediaSilo. Search for the app where you want the resulting action to take place. In this example, we’ll select Google Sheets.
Next, choose an event from the Event menu. Since we want the automation to add a new row to a spreadsheet after a file is uploaded, we’ll select Create Spreadsheet Row.
After you select the event, click Continue.
In the same way you connected your MediaSilo account, you’ll need to connect your Google Sheets account. A window will pop up, so you can sign in to your account.
Once Zapier is connected to Google Sheets, click Continue.
Next, choose the spreadsheet you want to use for this Zap and the Google Drive where the spreadsheet is located.
Since a single spreadsheet can contain multiple tabs/worksheets, choose the exact worksheet you want to use. After this step, you’ll see text fields matching the column headers in your sheet.
These fields correspond to the naming conventions used in your spreadsheet. For reference, below is the spreadsheet we are using for this example.
Now we’ll tell Zapier what data to add to each column. When you click into a text field, a list of available data fields appears. For the first column (“File Name”), select “Entity Asset File Name.”
Select the corresponding data fields for the three remaining columns, as pictured below. To learn more about available data fields, please see Pushing Event Data from MediaSilo to Other Apps.
After you’ve configured each of your spreadsheet columns, click Continue.
Just like you tested the trigger in MediaSilo, you can now test the action in Google Sheets. Click Test step.
Following a successful test, a new row with test content (e.g., “Great-Movie.mp4”) is added to your spreadsheet.
Note that the date in the “Date Uploaded” column appears in Unix time. You can convert this Unix timestamp to standard time using an online conversion tool, or, if your Zapier plan supports multi-step automations, you can add a step that does this for you. |
A checkmark now appears next to the Google Sheets icon on the left side of the page. The time has come to publish your Zap.
Moving forward, a new row will be added to your spreadsheet following each upload to your MediaSilo workspace. (Feel free to delete the test record (“Great-Movie.mp4”) in the first row.)
Back on the main Zaps page, you’ll see your new Zap listed. You can easily turn Zaps on and off by clicking the toggles on this page.
MediaSilo Events as Triggers
In the example above, we used the “new asset” event in MediaSilo to trigger a new row in a spreadsheet. This is just one of the MediaSilo events that can trigger an action in another app. Below is a list of additional triggers, such as “new project” and “new share” (i.e., a new Review Link).
- Deleted Asset
- Deleted Project
- New Asset
- New Project
- New Share
- New User Added to a Workspace
- Updated Asset
- Updated Project
- User Invited to a Project*
*Applies to both new and existing users invited to a project.
Whenever one of these trigger events takes place, you can automatically capture information about the event, such as the title of a new project, the name of a deleted file, or the URL of a new Review Link. To learn more, please see Pushing Event Data from MediaSilo to Other Apps.
MediaSilo Events as Actions
In addition to triggers, MediaSilo events can be the actions performed by a Zap. When setting up a Zap, the following events in MediaSilo can be triggered by other apps:
- Create Asset
- Create Project
- Create User
For example, you could format a Google spreadsheet to add a new user to your MediaSilo workspace whenever a new row is created. The Google spreadsheet below has been formatted with three columns for entering a user’s email address, first name, and last name.
In Zapier, the trigger event would be the creation of a new row in this particular spreadsheet. When setting up the action, you would configure MediaSilo to pull data from the three columns in the spreadsheet.
Once the Zap is published, populating the spreadsheet with email addresses and names will create users in MediaSilo.
For a Zap to perform an action in MediaSilo, Zapier needs certain pieces of information. The table below shows the required and optional fields for each action in MediaSilo.
Action | Required Fields | Optional Fields |
Create Asset |
Workspace, Source URL, File Name, Project ID |
Title, Description, Tags |
Create Project |
Workspace, Name, Description |
None |
Create User |
Workspace, Email Address |
First Name, Last Name |
Note that when you access MediaSilo via Zapier, MediaSilo’s permission system is still enforced. For example, if you do not have the ability to add users in the MediaSilo app, you cannot add users via Zapier. When setting up such a Zap, the test would fail. If you skip the test and publish it anyway, the Zap will not work.
Pushing Event Data from MediaSilo to Other Apps
You can configure a Zap to record key pieces of information following an event in MediaSilo. For example, a Zap can send you a Slack message each time a Review Link is created. The information contained in the Slack message is determined entirely by you. Let’s say you want the message to contain the link URL and the email address of the link creator. In Zapier, you would configure the Slack message to pull the following data:
- Entity Quick Link URL (the Review Link URL)
- User Email (the email address of the link creator)
These are just two of the many data fields available to you. The lists below show you all the information you can capture about assets, projects, links, and users.
Asset Data
Entity Asset Title | Entity Asset External | User Tag |
Entity Asset File Name | Entity Asset Private | Account Id |
Entity Asset Source Filename | Entity Asset Watermarked | Entity Asset Account Id |
Entity Project Name | Entity Project Is Watermarked | Entity Asset Approval Status |
Hostname | Created | Entity Asset Description |
User First Name | Entity Asset Created | Entity Asset Id |
User Last Name | Entity Asset Date Created | Entity Asset Owner Id |
User User Name | Entity Asset Date Modified | Entity Asset Poster Frame |
Entity Asset Derivatives Url | Entity Asset Progress | Entity Asset Project Id |
Entity Asset Derivatives Duration | Entity Asset Versions | Entity Asset Source File Extension |
Entity Asset Derivatives File Size | Entity Project Aggregates Average Duration | Entity Asset Transcript Status |
Entity Asset Derivatives Height | Entity Project Aggregates Average File Size | Entity Asset Type |
Entity Asset Derivatives Poster Frame | Entity Project Aggregates Total Assets | Entity Asset Uploaded By |
Entity Asset Derivatives Progress | Entity Project Aggregates Total Duration | Entity Project Description |
Entity Asset Derivatives Thumbnail | Entity Project Aggregates Total File Size | Entity Project Id |
Entity Asset Derivatives Type | Entity Project Aggregates Total Folders | Entity Project Owner Id |
Entity Asset Derivatives Watermarked | Entity Project Aggregates Total Users | Entity Project Type |
Entity Asset Derivatives Width | Entity Project Created | User Id |
Entity Asset File Url | Entity Project Date Created | |
Entity Asset Derivatives | Entity Asset Tags |
Project Data
Entity Project Name | Entity Project Aggregates Average File Size | User Tags |
Event Name | Entity Project Aggregates Total Assets | Account Id |
Hostname | Entity Project Aggregates Total Duration | Entity Project Description |
User First Name | Entity Project Aggregates Total File Size | Entity Project Id |
User Last Name | Entity Project Aggregates Total Folders | Entity Project Owner Id |
Entity Project Is Watermarked | Entity Project Aggregates Total Users | Entity Project Type |
Created | Entity Project Created | User Email |
Entity Project Account Id | Entity Project Date Created | User Id |
Entity Project Aggregates Average Duration | Entity Project Numeric Id |
Review Link Data
Entity Quick Link Title | Entity Quick Link Url | Entity Quick Link Authorized User Ids |
Entity Quick Link Shares Shared By First Name | Event Name | Entity Quick Link Project Ids |
Entity Quick Link Shares Email Share Audience First Name | Hostname | User Tags |
Entity Quick Link Shares Email Share Audience Last Name | Entity Quick Link Expires | Entity Quick Link Configuration Settings Key |
Entity Quick Link Shares Email Share Message | Entity Quick Link Configuration Settings | Entity Quick Link Configuration Settings Value |
Entity Quick Link Shares Shared By Last Name | Entity Quick Link Shares | Account Id |
Entity Quick Link Shares Created | Entity Quick Link Password | Entity Quick Link Account Id |
Entity Quick Link Shares Email Share Audience Email | Entity Quick Link Private | Entity Quick Link Configuration Id |
Entity Quick Link Shares Email Share Subject | Entity Quick Link Public | Entity Quick Link Description |
Entity Quick Link Shares ID | Entity Quick Link Signed | Entity Quick Link Id |
Entity Quick Link Shares Notify By Email | Entity Quick Link Watermarked | Entity Quick Link Owner Id |
Entity Quick Link Shares Shared By | Created | Entity Quick Link Thumbnail |
Entity Quick Link Shares Shared By Email | Entity Quick Link Created | User Email |
Entity Quick Link Shares Target Object Id | Entity Quick Link Modified | User Id |
User First Name | Entity Project Ids | |
User Last Name | Entity Quick Link Asset Ids |
User Data
Entity User Roles Display Name | Entity User Last Name | Entity User Account Id |
Entity User Roles Permission Groups Display Name | Event Name | Entity User Default Role Template Id |
Entity User Roles Context | Hostname | Entity User Email |
Entity User Roles Default | User First Name | Entity User Id |
Entity User Roles Description | User Last Name | Entity User Status |
Entity User Roles ID | Entity User Roles | Entity User Type |
Entity User Roles Level | Created | User Email |
Entity User Roles Permission Groups Group Identifier | Entity User Date Created | User Id |
Entity User Roles Permission Groups Permissions | Entity User Projects | |
Entity User First Name | Account Id |
Note that some of these data fields look similar but correspond to different data. For example, when creating a new user, “Entity User Email” refers to the new user’s email address while “User Email” refers to the user who created the new user.
Comments
0 comments
Please sign in to leave a comment.