If you want to upload files to Frame.io from existing cloud-based apps or a URL serving assets, Zapier is generally a good solution, as their product resolves many API design divergences that make interacting with cloud apps a headache. This guide clarifies key attributes of Zapier's upload service so you'll know exactly what's happening in your integration.
Zapier tries to automatically discover the most flexible file upload method for each API it connects to. For example, Zapier will try to convert restricted links that cannot be accessed outside an app's domain to publicly-available download links:
Original unreadable link:
Converted link, usable by Frame.io's Uploader API:
Importantly, if Zapier cannot discover a static download URL to pass to Frame.io's API, Zapier's own service will download files on the fly and passes them to Frame.io. Zapier restricts this method to files less than 100MB.
Note that Zapier's UI may warn you about filesize restrictions even when passing a Direct URL (i.e. when there is no restriction.) That's why it's worth understanding how File URL works.
Note: integrations with the Type File Upload are subject to file size limits indicated in Zapier's UI. Direct Links are preferable as they're not subject to size limitations and process faster and more reliably.
|App||Type||Tips and References|
|Gmail||File Upload||Zapier Help Docs|
|Google Drive||Direct Link||You want to paste |
|Dropbox||Direct Link||Automatically Upload Dropbox Files to Frame.io](doc:upload-dropbox-files-to-frameio|
|Box||Direct Link||Use |
|S3||Direct Link||Zapier Guide: Common Problems with S3|