Frame.io (legacy) Make integrationAutomate Frame.io (legacy) with Make.

Brings every project of a Frame.io team into the scenario, one bundle per project, so the modules after it can work on each of them in turn.

Reads one project you already know and hands its details to the next module. Handy when an earlier step gave you a project reference and you want the rest of the record.

Opens a new Frame.io project from your scenario, so a job exists in the review tool from the moment it is confirmed elsewhere, without anyone setting it up by hand.

Changes an existing project from outside Frame.io, which keeps the project in line with the record your team treats as the reference, such as a job sheet or a client file.

Returns the files and folders it finds as separate bundles, which gives your scenario an inventory it can loop over without anyone browsing Frame.io.

Fetches a single folder so the following modules know exactly where they are working. It is the precise lookup, where List files and folders is the broad sweep.

Adds a folder in Frame.io straight from the scenario, which lets every job start with the same structure instead of whatever each editor improvises.

Edits a folder that already exists, so its naming stays consistent with the rest of your process when a job changes status or title somewhere else.

Removes a folder from Frame.io on the scenario's order. It closes the loop on housekeeping that people tend to postpone, but it acts for real on your account.

Pulls the details of one file into your scenario, so later modules can mention it, route it or record it without anyone opening Frame.io to look it up.

Sends a file into Frame.io from another source in the scenario, so material that arrives elsewhere ends up in the review tool without a manual upload.

Erases a file from Frame.io when the scenario tells it to. Use it with intent: it is the module that turns a clean-up rule into an actual removal.

Collects all the comments on one asset, one bundle per comment. That gives you the full review thread in a form other tools can store or summarize.

Reads a single comment when you already know which one you want, rather than pulling the whole thread with List Comments. Precise, and lighter on operations.

Posts a comment in Frame.io from your scenario, so an answer written in another tool shows up where the client reviews the video, next to the footage.

Rewrites an existing comment in Frame.io. The thread stays clean: a correction replaces the old wording instead of piling a second note under the first.

Takes one comment off an asset for good. Mostly useful to clean up what automations wrote, rather than what people wrote by hand.

Returns the share links it finds, each as a separate bundle, which gives you an overview of what has been sent out to clients and partners.

Fetches one share link and its details, so you can pass the right information along to whoever is waiting for the delivery.

Opens a new share link in Frame.io, the address you send outside the team so someone can view work without digging through your project.

Puts a file or a whole folder into an existing share link, so the person on the other side sees the new material without receiving a fresh address.

Takes an item out of a share link while the link itself stays alive, so the client keeps the same address but stops seeing outdated material.

Changes the settings of a share link that is already out there, without sending a new address to the people who have it.

Shuts a share link down. Anyone holding the address loses access through it, which makes this the cleanest way to close a delivery from a scenario.

Reaches any endpoint of the Frame.io API with the connection you already have, which covers what the listed modules leave out.

Creates a new asset in Frame.io from your scenario. Assets are the items reviewers comment on, so this is how content from another tool enters the review cycle.

Removes one asset, identified by its reference, from Frame.io. It is the final step of a clean-up rule, the one that actually frees the project of old material.

Reads a single asset by its reference and passes its details on. This is the module that turns a bare notification into something a person can act on.

Changes an existing asset without touching the others. Your scenario keeps assets in step with decisions taken in other tools, with no one editing them one by one.

Lists every asset inside one folder, each as its own bundle, so a scenario can process a whole delivery in a single pass instead of item by item.