When a file is ready to view in your Frame.io workspace, this Zap automatically sends a notification to a designated Slack channel with the project name, the uploader's name, and a direct view link to the file.
Note: The view link shared in Slack requires Frame.io workspace or project access to open. This Zap is intended for sharing assets within your team. To share assets with people outside your workspace, use Frame.io's share link feature instead.
What you'll need
A Frame.io V4 account
A Zapier account
A Slack workspace with a channel for review notifications
Set up the Zap
Step 1: Open the template
Click the button below
When the template opens, the guided setup wizard will launch automatically. Before exiting, confirm the Zap has been given a name and saved to the desired folder location. Then click Cancel, then Close setup to exit. Your Zap is saved and you can continue in the Zap editor.
Step 2: Connect your accounts and configure the trigger
Frame.io: Select the account and workspace you want to monitor.
Slack: Select the workspace where notifications should be sent.
Upload a file to the desired workspace and project.
The trigger fires when a file finishes processing and is ready to view. It watches the entire workspace. Frame.io V4 sends data to Zapier in real time. Zapier needs to receive a real event from Frame.io before the fields in later steps are available to configure.
Confirm the trigger step has received the event before moving to the next step.
Step 3: Set the filter
The filter limits notifications to files in a specific Frame.io project and folder. Without it, this Zap will fire for every file that becomes ready across your entire workspace. The filter requires a static value because it is a condition, not a data field.
The filter is configured to match exact project and folder IDs. IDs never change even if the project or folder is renamed in Frame.io. Project and folder IDs are included in the trigger payload once a test event has been received. They are also available in the browser URL bar in Frame.io.
To find your project and folder IDs:
Open your project in Frame.io
Copy the project ID from the browser URL bar. It is the string of characters after
/project/Navigate into the folder you want to monitor
Copy the folder ID from the browser URL bar. It is the string of characters after the project ID
Update the filter with the project and folder IDs you want to monitor. For more information see Adding filters to your Frame.io Zaps.
To remove the filter entirely, delete the filter step. The Zap will then fire for every file that becomes ready across your entire workspace.
Step 5: Confirm the Show File step
The Show File step retrieves the file details needed to build the Slack message, including the creator's name and the view URL. Confirm your Frame.io account is selected. The file ID is mapped dynamically from the trigger and does not need to be changed. Make sure you have uploaded a file to the desired workspace to test the step.
Step 6: Configure the Slack message
Select the Slack channel where notifications should be posted. The message is pre-formatted with the following information pulled dynamically from Frame.io:
Project name
Creator name: the person who uploaded the file
File name: linked directly to the asset in Frame.io
You can edit the message text to match your team's preferred format.
Note: Some Slack workspaces require admin approval before third-party apps can post messages. If you run into issues, contact your Slack workspace admin.
Step 7: Test the Zap
Before publishing, click Test on each step in sequence and confirm the data is flowing correctly from Frame.io through to Slack. Fix any errors before publishing.
Step 8: Publish the Zap
Click Publish.
The Zap is now live. Every time a file is ready to view in the specified folder, your Slack channel will be notified automatically.
Troubleshooting
Zap is not triggering
Confirm the correct Frame.io account and workspace are selected in the trigger step. The File Ready trigger fires only after a file has finished processing, not immediately on upload.
Notifications are coming in for the wrong folder
Check the filter step and confirm the folder ID matches exactly. Copy it carefully from the browser URL bar with no extra spaces or characters.
Slack message is missing the creator name or file link
Confirm the Show File step is receiving the file ID dynamically from the trigger. If the field is empty or hardcoded, the step will not retrieve the correct file details.
Notifications are being sent to the wrong Slack channel
Update the channel selection in the Slack step to the correct channel.
Zapier cannot post to Slack
Your Slack workspace may require admin approval for third-party app integrations. Contact your Slack workspace admin to authorize Zapier.