Connect Brick FTP and Frame.io (Legacy) to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
How Zapier works
Zapier makes it easy to integrate Brick FTP with Frame.io (Legacy) - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "New File Uploaded" from Brick FTP.
Add your action
An action happens after the trigger—such as "Create Asset" in Frame.io (Legacy).
You’re connected!
Zapier seamlessly connects Brick FTP and Frame.io (Legacy), automating your workflow.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- Parent Folder Path
Try ItTriggerPolling- New User
Triggers when a new user is created.
Try ItTriggerPolling - PermissionRequired
- Username
- Path
- User ID
- Group ID
ActionWrite- FileRequired
- Upload Folder
- File Name
ActionWrite
- New Group
Triggers when a new group is created.
Try ItTriggerPolling - NameRequired
- Notes
- User IDs
ActionWrite- UsernameRequired
- PasswordRequired
- Name
- Email
- Group IDs
- FTP Permission
- Web Permission
- Sharing Tab Permission
- Password Change Permission
- Require Password Change on Login
- Allowed IPs
- FTP Root Folder
- Grant Permissions on Root Folder
ActionWrite- TeamRequired
Try ItTriggerInstant
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023




93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Frequently Asked Questions about Brick FTP + Frame.io (Legacy) integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Brick FTP and Frame.io (Legacy)
How do I set up an integration between Brick FTP and Frame.io?
To set up an integration between Brick FTP and Frame.io, you'll need to use our platform to create a Zap. Start by selecting Brick FTP as your trigger app and choose a trigger event, such as 'New File Uploaded'. Then select Frame.io as your action app and configure the action, like 'Upload File'. This will automate the process of transferring files from Brick FTP to Frame.io.
What are the available triggers for Brick FTP in this integration?
For Brick FTP, you can use triggers like 'New File Uploaded' or 'File Updated'. These triggers initiate workflows where files in your Brick FTP account prompt actions in connected apps like Frame.io.
Can I automatically upload files from Brick FTP to Frame.io?
Yes, by setting up a Zap with Brick FTP as the trigger app with the trigger event 'New File Uploaded', you can automate uploads of those files to Frame.io by configuring it as the action app.
Are there any specific conditions that need to be met for file transfer from Brick FTP to Frame.io?
During setup, you'll specify conditions such as file type or size when configuring your trigger on Brick FTP. Ensure these meet any requirements you may have set for handling within Frame.io as well.
Can we use this integration for video projects managed in Frame.io?
Absolutely, integrating these two platforms allows us to automatically move media assets from Brick FTP into video projects managed in Frame.io. Just ensure the asset formats are compatible with what you're using within Frame.io.
How does this integration handle file updates?
When a file is updated on Brick FTP, if you’ve selected ‘File Updated’ as your trigger event, our system can automatically reflect those changes in Frame.io by triggering an update action there.
Is it possible to track file transfers between these applications?
Yes, once configured, you can monitor file transfers through your Zapier dashboard. You'll see logs of triggered events and actions that help track each step of your workflow execution between the platforms.