Skip to main content

Filter automations by number fields

Let an automation continue only when a number, calculation, or unique ID is in the range you need. See the options for each field type and an example.

Written by Leo

You can filter number fields to let an automation continue only when an amount, a quantity, or a counter is in the range you need. Number filters compare the field's current value with the value you set.

You can use number filters for many things, including:

  • Sending an approval request only when an expense is over 5,000 EUR.

  • Creating a purchase task only when the stock of a solar component drops below 20.

The example automation in Expenses: When a record is created, the filter Where Amount > 5000, and the action Add a comment to the current record with Needs approval: @Expense / Vendor

This page covers these field types: number, calculation, and unique ID.

Note:

  • Calculation fields can hold text or dates too. The options you see depend on what the calculation returns.

  • Unique IDs have no change check. Has changed isn't available for them.

Who can use filters on number fields?

  • Automations are available on all plans: Free, Plus, and Premium. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.

  • To create, edit, pause, or delete automations, you need to be a Workspace admin of the workspace the app is in and have Full access to every app the automation uses. App permissions alone aren't enough.

Add a filter on a number field

To filter a number field:

  1. Open the database app on desktop or web, click the automations icon in the top bar (tooltip Create and view automations), then open an automation.

  2. Under And if the following conditions are met, select Add filter.

  3. In the new row, select the field and choose the number, calculation, or unique ID field.

  4. Select the option and choose how to compare (listed under Options for number fields).

  5. Enter the number. You can also insert a value from another field.

  6. Select Save changes.

In a new automation for Expenses, selecting Add filter, choosing the Amount field and the option >, and entering 5000

Options for number fields

For number fields, you can choose from these options:

  • = (equal to) and ≠ (not equal to) check whether the number equals the value.

  • > (greater than) and < (less than) check against the value, without the value itself.

  • ≥ (greater than or equal to) and ≤ (less than or equal to) check against the value, including the value itself.

  • Is empty and Is not empty check whether a number is set. A 0 counts as a number, so Is empty isn't met.

  • Has changed checks whether the number was edited in this update. It's only offered with the trigger When a record is updated. Learn more →

A filter row on the number field Amount in a new automation for Expenses, with the options open: =, ≠, &lt;, &gt;, ≤, ≥, Is empty, and Is not empty

For calculation fields, the options depend on what the calculation returns:

  • For a number: =, ≠, <, >, ≤, ≥, Is empty, and Is not empty.

  • For text: Is, Is not, Contains, Does not contain, Starts with, Ends with, Is empty, and Is not empty.

  • For a date: Is, Is not, Is before, Is after, Is empty, and Is not empty.

  • With the trigger When a record is updated, each of them also offers Has changed.

For unique ID fields, you can choose =, ≠, <, >, ≤, ≥, Is empty, and Is not empty. Use = for one ID, or ≥ to include every record from a number onward.

Let's look at an example

Let's say a finance team wants a second look at big expenses. Here's how:

  1. Set the trigger to When a record is created in Expenses.

  2. Add the filter Where Amount > 5000.

  3. Select Add action → Add comment. The step appears as Add a comment to the current record. Enter "Needs approval: " and insert the Vendor field.

  4. Select Create automation.

The next time someone books an expense above 5,000, you should see the comment on the record!

Number filter errors

  • If a filter row is incomplete, or uses a field that no longer exists, the editor marks it in red and the status below the automation's name shows Broken. Complete or remove the row, then select Save changes.

  • If a filter matches every record, check the value. A number that comes from a field and is empty at run time can match every record. See My filter doesn't match →.

  • Use Is empty to find records with no number in the field. An empty number field acts like 0 for <, >, ≤, and ≥, but not for =. Add Is not empty to leave out empty fields.

Test, pause, edit, or delete a filter

  • To test a filter, change a test record so it matches the condition, then click ▷ next to Manual run at the top right of the editor (tooltip View all runs) to open Runs. In a Manual run, no field has changed, so Has changed doesn't match.

  • To edit a filter, open the database app, click the automations icon in the top bar, then select the automation. Change the field, option, or value, then select Save changes.

  • To delete a filter, click ••• at the end of the row or group, then select Remove. Select Save changes.

Learn more

FAQs

How do I check that a number is between two values?

Add two filters in the same list: ≥ the lower value and ≤ the upper value. Both have to be met.

Can I compare a number with another field?

Yes! Insert the other field as the value. If that field is empty on a record, the condition can match every record, so check for Is not empty first. Learn more →

Why can't I filter a calculation field with the options I expect?

The options follow what the calculation returns. A number offers =, <, >, and the other number options. Text offers Contains, Starts with, and more. A date offers Is before and Is after. Learn more →

Can I filter on a unique ID?

Yes! Use = for one ID, or ≥ to include every record from a number onward.

Where can I find all automation filter options?

In Automation filters →. It explains how to combine rows and groups and links to the options for each field type.

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: Filters in the developer docs →

Still have questions? Find answers and get help from community experts in the Tape community →

Did this answer your question?