By default, most Frame.io Zaps watch your entire workspace. A filter step scopes the automation to a specific project or folder so it only fires when the right assets and the right locations are involved.
Why use a filter
Without a filter, a Zap triggered by a file upload or Action will run for every asset across your entire workspace. For small teams with one active project this may be fine. For larger teams or accounts with high upload volumes, an unfiltered Zap will generate excessive tasks, notifications, or records and become difficult to manage.
Three ways to filter
Hardcoded static value
You type a fixed value directly into the filter field. If the value ever changes in Frame.io, the filter breaks silently.
Name-based value
You type a name. Readable but if the object is renamed in Frame.io, the filter immediately stops matching. Exact match is also case sensitive, so "For Review" and "for_review" are treated as different values.
ID-based value
You paste a project ID or folder ID from the Frame.io URL. IDs never change even if the project or folder is renamed. This is the most reliable approach and the one we recommend when appropriate. The only tradeoff is that an ID is not human-readable, so adding a note in your Zap description helps your team know what it refers to.
Filter types
Text filters
Use these for any field that contains text including file names, project names, folder names, metadata values, uploader names, and more. All text filters are case-insensitive.
Condition | How it works |
Contains | Field includes the value anywhere |
Does not contain | Field does not include the value |
Exactly matches | Field equals the value exactly |
Does not exactly match | Field does not equal the value |
Is in | Field matches one of multiple comma-separated values |
Is not in | Field does not match any value in a comma-separated list |
Starts with | Field begins with the value |
Does not start with | Field does not begin with the value |
Ends with | Field ends with the value |
Does not end with | Field does not end with the value |
Number filters
Use these for numeric fields like file size or count values.
Condition | How it works |
Greater than | Field is larger than the value |
Less than | Field is smaller than the value |
Boolean filters
Use these for true/false fields.
Condition | How it works |
Is true | Field value is true |
Is false | Field value is false |
Generic filters
Use these for any field type when you want to check whether a value exists at all.
Condition | How it works |
Exists | Field contains any value |
Does not exist | Field is empty |
Combining multiple rules
When you add more than one rule to a filter, you must choose how they relate:
AND logic: all rules must be true for the Zap to continue. Use this to narrow results.
Example: project name contains “campaign” AND file type is video
OR logic: at least one rule must be true for the Zap to continue. Use this to broaden results.
Example: uploader is “Jane” OR uploader is “John”
Common Frame.io filter patterns
What you want to filter | Field | Condition | Value |
Specific project | Project Id | Exactly matches | your project ID |
Specific folder | Parent Id | Exactly matches | your folder ID |
Files only (not folders) | Resource Type | Exactly matches | file |
Approved assets only | New Value | Exactly matches | Approved (text filter) |
Video files only | Media Type | Contains | video |
Specific uploader | Creator Name | Exactly matches | uploader name |
File name pattern | Name | Contains | your search term |
Find your project or folder ID in Frame.io
Frame.io project and folder IDs live in the browser URL bar.
Project ID:
Open your project in Frame.io
Copy the string of characters after /project/ in the URL
Folder ID:
Open your project in Frame.io
Navigate into the folder you want to scope the Zap to
Copy the string of characters that appears after the project ID in the URL
Add a folder or project filter step in Zapier
Open your Zap in Zapier
Click the + button to add a step after the trigger
Search for and select Filter by Zapier
Set the filter condition:
Field: select Project Id or Folder Id (also referred to as Parent Id) from the available fields
Condition: select exactly matches
Value: paste your project ID or folder ID
Click Save
The filter will now check every trigger event against the ID you entered. If the asset does not belong to that project or folder, the Zap stops and no further steps run.
Remove or skip the filter
To remove the filter entirely, click the filter step in Zapier and select Delete. The Zap will then fire for all assets across your entire workspace.
Troubleshooting
Filter step is stopping the Zap unexpectedly
Confirm the project or folder ID is copied exactly from the URL with no extra spaces or characters. IDs are case sensitive.
The field I want to filter on is not available
Fields only appear as options after the trigger or Show File step has received a payload. Fire a test trigger first, then return to configure the filter. If the field still does not appear, confirm it is included in the data returned by the previous step.
The filter works but fires for the wrong assets
Confirm you are using the correct ID. A project ID scopes to the whole project. A folder ID scopes to one specific folder. Navigate to the correct level in Frame.io and copy the ID from the URL again.
I cannot find the Project Id or Folder Id field in the filter
These fields are only available after the trigger or Show File step has received a payload. Fire a test trigger first, then return to configure the filter.