Skip to main content

​
Why filter records

By default, a processor tool processes every record in the source table. Filters let you limit that to a specific subset: by Airtable view, by field conditions, or both. Use filters to:
  • Process only records in a particular pipeline stage
  • Skip records that have already been processed
  • Run a tool on a test set before applying to the full table
  • Process records that meet a specific business condition

​
Filter options

​
Source view

Select an Airtable Source view to limit processing to records that appear in that view. This is the simplest way to filter. Create a view in Airtable with the right filter, sort, and conditions, and point the tool at it. Example: Create an Airtable view called “Needs geocoding” that filters for records where the Latitude field is empty. Point the Geocoder tool at that view.

​
Filter records (additional conditions)

Use the Filter records condition builder to add filter logic directly in the tool configuration. This uses the same filter builder as conditional logic in forms. You can combine a source view with additional filter conditions for more precision.

​
Combining view and condition filters

When both a source view and filter conditions are set, only records that are in the view AND match the conditions are processed. They are combined with AND logic.

​
Common filter patterns

Process only records where output is empty: Use a filter: Output field is empty. This skips records that already have a value in the output field, making the tool safe to re-run. Many tools also have a built-in “Skip already processed records” or “Skip empty fields” toggle that handles this automatically. Process only records from the last 30 days: Use a filter: Created time is within last 30 days. Process only records with a specific status: Use a filter: Status is Pending.

​
Common questions

Yes. Formula fields can be used in filter conditions. The tool evaluates the formula’s current value when deciding whether to include a record.
Views are managed in Airtable and can include sorts, groupings, and conditional field visibility. Tool filter conditions are managed in Filla and apply additional logic on top of whatever the view returns. Use views when the filter logic is useful across multiple tools or use cases; use tool conditions for one-off processing needs.
Yes. The tool reads the view’s current record set each time it runs. Changes to the view’s filters in Airtable are reflected immediately.