How to Build the Perfect Video Review Workflow: Notion + Frame.io Automation Guide

The Short Answer: To create the perfect video review workflow, connect Notion (project management) to Frame.io (video review) using an automation platform like Make.com. This setup automatically creates Frame.io folders when a Notion project starts, syncs editor uploads to Notion task statuses, and instantly notifies project managers when a client marks a video as "Approved."

The Probem: The "Admin Gap"

If you run a video editing agency, you know the "Admin Gap." It’s the time wasted manually creating folders, copying links from Frame.io to Notion, and refreshing email to see if a client has left feedback.

By automating the API connection between Notion and Frame.io, you can eliminate 90% of this admin work.

The Tech Stack & Pricing

To build this, you need three tools. We recommend Make (formerly Integromat) over Zapier for this specific workflow because it handles complex logic (like mapping team members) much better.

1. Notion (Central Hub)

   • Plan: Plus Plan ($8/user/mo) recommended for team features.

2. Frame.io (Asset & Review Hub)

   • Plan: Pro ($15/user/mo) or Team ($25/user/mo).

3. Make.com (The Connector)

   • Plan: Core Plan ($9/mo). You need the paid plan to use Webhooks, which are essential for instant updates.

The Step-by-Step Automated Workflow

Here is the exact logic real-world video editing agencies use to automate their pipeline.

Phase 1: The Project Kickoff (Notion → Frame.io)

Goal: Never manually create a folder structure again.

The Trigger:

• You create a new card in your Notion "Projects" database.

• You change the Status property to "Active."

The Automation (via Make):

1. Watch Database Item: Make detects the status change.

2. Create Project (Frame.io API): Make takes the "Project Name" from Notion and creates a new Project inside your Frame.io Team account.

3. Add Collaborator: The automation looks at the "Assigned Editor" in Notion and adds their email to the Frame.io project.

4. The Secret Sauce: Make takes the Project ID generated by Frame.io and pastes it back into a hidden text property in your Notion card. This ID is the bridge for all future steps.

Phase 2: The Upload Sync (Frame.io → Notion)

Goal: PMs know a draft is ready without the editor sending a Slack message.

The Trigger:

• Editor uploads a file to Frame.io containing "V1" or "Cut" in the filename.

The Automation:

1. Webhook (Asset Created): Frame.io instantly pings Make.

2. Search Objects (Notion): Make searches your Notion database for the entry containing the matching Project ID.

3. Update Database Item:

   • Change Status to "Internal Review."

   • Post a comment in Notion: "New V1 Uploaded. [Link to Video]"

Phase 3: The Client Feedback Loop (The Holy Grail)

Goal: Statuses update themselves based on client behavior.

Scenario A: The Client Requests Changes

• Trigger: Client leaves a comment on the video in Frame.io.

• Action: Notion status automatically flips to "Feedback Received."

• Bonus: The automation grabs the text of the comment and appends it to the Notion page body, so the PM sees the feedback context immediately.

Scenario B: The Client Approves the Video

• Trigger: The "Status Label" on the video file changes to Approved (Green).

• Action: Notion status flips to "Approved" or "Ready for Delivery."

  
  

Technical Deep Dive: The APIs You Will Need

This section is for the agency owners and developers who want to know exactly how to build this in Make.

While Make has "native" modules, pros often use the "Make an API Call" module for more control. Here are the specific endpoints agencies use:

1. Syncing Projects (Notion → Frame.io)

• API Endpoint: POST /v4/accounts/{account_id}/projects

• Why use this? The native module sometimes misses specific settings like "Private" or "Public."

• The Logic: You must store the id from the response into your Notion database property Frameio_Project_ID.

2. Creating "Review Links" (The Pro Move)

Most agencies don't invite clients to the full project folder. Instead, they generate a specific Review Link (presentation page).

• API Endpoint: POST /v2/review_links

• Make Module: Use "Make an API Call" (Frame.io).

  
  

  JSON Body Example:

  
  

  {
    "project_id": "YOUR_PROJECT_ID",
    "name": "Client Review - V1",
    "enable_downloading": false,
    "enable_comments": true,
    "items": [
      { "id": "ASSET_ID", "type": "file" }
    ]
  }

• Result: The API returns a short_url. You can then update your Notion card with this clean link for the client.

3. Mapping Users (Notion Users → Frame.io Emails)

Notion uses internal IDs (e.g., @u-1234), but Frame.io needs emails.

• The Workflow: Create a "Data Store" in Make or a separate Notion database called "Team Directory."

• Columns: Notion Name | Frame.io Email

• Logic: When automation runs, it looks up the Notion User → finds the matching Email in the directory → sends that email to Frame.io's Add Collaborator endpoint.

Implementation Checklist

Before you start building in Make, ensure you have the following ready:

• [ ] Notion: A dedicated "Projects" database with a "Status" property (Select) and a "Frame.io Project ID" property (Text).

• [ ] Frame.io: Developer Token generated (in Frame.io Developer settings).

• [ ] Make: A registered account.

  
  

Pro Tip: The "Review Link" Automation

Do not send clients the raw Project link; they might see messy internal files.

Instead, add an automation step: When the Notion status moves to "Client Review" → The API triggers "Create Review Link" in Frame.io for the latest asset. It then pastes that clean, branded presentation link back into Notion for the PM to email to the client.

Frequently Asked Questions (FAQs)

Q: Why use Make instead of Zapier for this?

A: Frame.io's API requires specific "Webhooks" to be instant. Zapier often relies on "polling" (checking for updates every 15 minutes). Make is also cheaper for multi-step workflows involving logic (e.g., "If file name contains V1, do X").

Q: Can I sync comments from Frame.io directly into Notion?

A: Yes. You can set up a comment.created webhook. However, be careful—if a client leaves 20 comments in 1 minute, you will get 20 notifications in Notion. It is often better to just update the Status or post a summary.

Q: Is this possible with the Free version of Frame.io?

A: You can use the API with the free version, but you are limited to 2 active projects. For a functioning agency workflow, you will hit the storage and project limits almost immediately. The Pro plan is the baseline for this workflow.

Q: Do I need to know how to code?

A: No. Make.com is a "No-Code" visual builder. However, you need to understand the logic of "Triggers" and "Actions" and how to map data (like IDs) between fields.