Skip to main content

Build Workflows with Make

Build custom workflows and connect Frame.io to other apps with Make.

A
Written by Aaron Burns

The Frame.io app in Make lets you build custom workflows that connect Frame.io with other apps. These workflows are called scenarios. Each one is a series of steps, called modules, that Make runs in order.

Scenarios follow an if this, then that idea. When this happens, do that thing. Every scenario starts with a trigger, followed by actions. The trigger waits for something to happen.

For example, you can build a scenario that starts when a file becomes ready in Frame.io and then adds a row to an Airtable base. You could add more steps, like sending a message to your team. Scenarios can also work the other way. An action in Frame.io can follow a trigger from another app, such as creating a project when a client submits a form.

Frame.io has one trigger in Make: Watch Events. It is an instant trigger, so it starts your scenario right away when an event you choose happens in the Frame.io account and Workspace you select. One Watch Events module can watch for one event or many, including projects, folders, files, comments, share links, and metadata. Make saves your choices in a webhook, so you never copy or paste a URL.

Every other Frame.io module is an action. Actions let a scenario work with projects, folders, files, comments, and share links, and Make an API Call sends your own request for anything the modules don't cover. For endpoints, request formats, and webhook events, see the Frame.io developer documentation.

Events only include the ID of the item involved, not its name or other details. Add an action, such as Get a file, to retrieve them.

Here's how you get started with Frame.io in Make.

What you'll need

  • An active Make account. A free account is available.

  • A Frame.io account. If you haven't already, link your Frame.io ID and Adobe ID. See Connecting to Adobe authentication.

  • Account Owner or Content Admin permissions.

Getting started

  1. In Make, select Create a new scenario. Select the + button, search for Frame.io, and select Watch Events.

  2. Next to Webhook, select Add. This opens Create a webhook, where Make saves your Watch Events settings.

  3. Next to Connection, select Add, sign in with your Adobe ID, and select Allow access. Optional: In Connection name, enter a name for the connection so you can recognize it later.

Frame.io and Make are now connected.

Build your first scenario

This example adds a row to Airtable each time a file becomes ready. Before you start, create an Airtable base with a table that has these fields:

File Name, File ID, and Workspace ID.

  1. Select Frame.io app and in Webhook name, enter a name that describes the workflow, such as File ready to Airtable. Select your Account and Workspace, choose File ready as the event, and select Save.

  2. Select Run once. Make now waits for an event.In Frame.io, upload a file to the Workspace you chose. When it's ready, Make receives the event and shows a bubble above the module. Select the bubble to see the data.

  3. Select the + next to the module, search for Frame.io, and select Get a file. Map the file ID from Watch Events.

  4. Select the + again, search for Airtable, and select Create a Record. Connect your Airtable account, then select your base and table.

  5. Map the data from the earlier modules to your Airtable fields. Click into each field and select the matching item.

  6. Select Run once and upload another file. A new row should appear in Airtable.

  7. When you're ready, turn on the Active toggle. Because Watch Events is an instant trigger, the scenario runs as soon as a file is ready.

Troubleshooting

My scenario fails to run and can't access my Frame.io account

Make sure your Frame.io ID and Adobe ID are linked. See Connecting to Adobe authentication. If your connection has expired, select Connections in the left sidebar, then Reauthorize.

I can't find my account in the account list

Confirm you're signed in with the correct Adobe Profile. An Adobe ID can have access to several profiles, and the profile determines which Frame.io accounts you can see. To change profiles, select Add next to Connection and sign in again with the right profile.

Why can't I see my actual data when testing?

Watch Events only receives new events. After you select Run once, perform the action in Frame.io, such as uploading a file. To test with an event Make already received, select the dropdown next to Run once and choose to rerun earlier data.

My scenario runs more often than I expect

Check the Events list in your webhook. Verify correct events are selected. You can also add filters to scope your scenario to a specific project or folder.

Can I use experimental endpoints with Make an API Call?

Yes, but they're still in development. Routes and responses can change before an official release, so avoid experimental endpoints in workflows your team depends on. For the current list see Frame.io developer documentation.

Did this answer your question?