Skip to main content

Rule Conditions

Written by Ari Schlacht
Updated over 4 months ago

So you know that Triggers define when an automation starts, and Actions define what happens.

But what if you only want those Actions to run sometimes, not every time the Trigger fires?

That’s where Conditions come in.


What is a Condition?

A Condition is a simple check Sequence makes before running your rule.

Think of it as an extra layer of logic:

  • Trigger says “Run now”

  • Condition asks “Should we really run?”

  • Action happens only if the answer is yes

Example

Let’s say your paycheck hits your Income Account (Trigger).

You have a rule that moves 15% to Taxes (Action).

But you also add a Condition: only run this if my Income Account balance is above $500.

  • If your balance is above $500 → the action runs

  • If not → the rule is skipped


What to Do If the First Condition Isn’t Met

Sometimes you don’t just want a single yes-or-no check.

You may want to say:

  • “If this happens, do X.”

  • “If that happens instead, do Y.”

  • “And if neither of those happen, do Z.”

That’s where Else-If and Else come in.

  • Else-If Clause

    • Lets you add another condition to check after the first one.

    • Example: “If my balance is over $2,000, save 20%. Else if it’s between $1,000 and $2,000, save 10%.”

  • Else Clause

    • Think of this as your backup plan.

    • If none of the conditions above are true, the Else is what runs.

    • Example: “If my balance is under $1,000, don’t move any money.”

You can add these additional conditional checks by clicking the + button in the bottom left of the rule panel


Full Example

Your paycheck hits your Income Account (Trigger):

  • Condition: If your balance is over $2,000 → save 20%

  • Else-If: If your balance is between $1,000 and $2,000 → save 10%

  • Else: If your balance is under $1,000 → do nothing

This gives your rule a clear next-step, no matter the situation.


Why use Conditions?

Conditions are more advanced than what most Sequence users need day-to-day - but if you want your automations to adapt based on what’s happening in your accounts, this is where they shine.

Conditions let you run automations dynamically based on things like:

  • Account balances

  • Dates or time windows

  • Whether something has (or hasn’t) happened yet

Instead of automations that run the same way every time, Conditions let your system respond to real-world changes.

If you’re building more nuanced, self-adjusting money flows, Conditions are your bread and butter.


The 3 Types of Conditions

You can choose from three types of conditions:

  1. Transfer Amount (incoming-funds triggers only)

    • Compares the amount received to a value.

    • Example: Only move 15% to Taxes if the deposit is greater than $1,000.

  2. Balance

    • Compares the balance of any connected account to a value.

    • Example: Only send money to Savings if my Income Account has more than $500.

  3. Day of the Month

    • Compares the current day to a date you choose.

    • Example: Only transfer extra funds if today is before the 20th.


How to Add and Delete Conditions

To add your first Condition:

  • After setting a Trigger, look for the Condition section in the rule panel

  • Click the + button

  • Choose the condition type and fill in the comparisons

  • Any Actions placed directly below that condition run only if it’s true

To add an Else-If:

  • Scroll to the Condition section

  • Click the + button again

  • This creates a second condition to check if the first fails

To add an Else:

  • Scroll below the Actions tied to your Else-If

  • Click the blue + Else button

  • Define the fallback Action(s)

To delete any condition:
Click the trash-can icon next to it.


Key takeaway

  • Trigger = when your rule starts

  • Action = what your rule does

  • Condition = whether the rule should actually run

Conditions are optional — but they make your automations far more flexible, safe, and intelligent.


Did this answer your question?