Skip to main content

Action Types

Actions tell Sequence what to do with your money. Use fixed transfers, percentage splits, round down, or top up. For liabilities, use dynamic payments, Snowball, or Avalanche. Add limits or “transfer up to” rules to control how funds move.

Written by Ari Schlacht
Updated over 5 months ago

Actions are the instructions that tell Sequence what to do with your money. In other words, the automation itself.

There are four core action types, plus additional ones that apply specifically to liabilities.


Core Action Types

1. Transfer Fixed Amount

Send a set dollar amount from one account to another.

Example: Send $2,000 from my Business Account to my Personal Checking.


2. Transfer Percentage of Available Funds

Send a percentage of whatever balance is available in the account.

Example: Send 15% of incoming funds to my Taxes pod.

Add account

To divide percentages across multiple destinations, click the blue “Add account” button below the last account.

Remove account

To remove an account from the division, click the blue “-” button to the right of that account.

Important: Unlike the list of actions (which run in order), percentage-based transfers happen simultaneously.

This means the visual order on screen doesn’t matter — every percentage transfer executes at the same time.


3. Round Down

Set a desired balance for an account, and Sequence will move any extra above that balance to another destination.

Example: Keep $1,000 in Checking, and send everything above that balance to Savings.


4. Top Up

Bring an account up to a desired balance.

If the source account doesn’t have enough funds to cover it, Sequence will move all available funds.

Example: If my Groceries pod already has $50 in it, and a rule is set to top it up to $300 every week, the next time this rule runs it will send $250 to the Groceries pod.


Liability-Specific Actions

Some actions are tailored for paying off debts or liabilities.


1. Pay Dynamic Liability Balance

(Liability destinations only)

Automatically make payments toward a liability. Options include:

  • Minimum amount due

  • Last statement balance

  • A percentage of the current balance

  • The full current balance

If the balances shown for a specific liability are ever inaccurate or unavailable, you can click directly on the data and enter the value manually.

For example, you might type in the minimum payment due yourself.

That value will stay in place until you update or delete it.


2. Snowball Method

The Snowball Method is about building momentum.

Here’s how it works:

  1. Sequence first makes the minimum payments on all your liabilities.

  2. Any extra money you’ve allocated goes toward the smallest balance first, regardless of the interest rate.

  3. Once that smallest debt is paid off, the money you were using there “snowballs” into the next smallest balance, and so on.

Why use this method?

  • You see quick wins as smaller debts disappear faster

  • It’s motivating to close out entire accounts sooner

Example:

  • You owe $500 on Card A, $2,000 on Card B, and $5,000 on Card C

  • Minimums go to all three cards

  • Extra funds pay off Card A first, then roll into Card B, then Card C


3. Avalanche Method

The Avalanche Method is about saving the most money over time.

Here’s how it works:

  1. Sequence first makes the minimum payments on all your liabilities.

  2. Any extra money you’ve allocated goes toward the highest interest rate debt first, regardless of its size.

  3. Once that high-interest debt is paid off, extra funds move to the next highest interest, and so on.

Why use this method?

  • You’ll pay less interest overall

  • It’s the most cost-effective in the long run

Example:

  • You owe $500 on Card A (10% APR), $2,000 on Card B (20% APR), and $5,000 on Card C (15% APR)

  • Minimums go to all three cards

  • Extra funds pay down Card B first (20%), then Card C (15%), then Card A (10%)


Allocating an Amount to Snowball or Avalanche

When setting up either repayment strategy:

  • Choose how you want to allocate:

    • A percentage of the account’s balance (or incoming funds)

    • A fixed dollar amount

  • Add liabilities by clicking “Add account” and selecting the debt you want to include.

  • Adjust APR if needed:

    • Sequence usually pulls APR automatically.

    • If the number is wrong or missing, you can edit it or enter it manually.

    • Manually entered APR stays in place until you update it.


Limiting Rules

Sometimes it helps to have a safety net.

Limiting Rules let you set a cap on how much money a rule can transfer — no matter what the rule is configured to do.

You can apply a limit to:

  • A single transfer

  • A week

  • A month

  • A year

These timeframes follow calendar periods:

  • A week runs Monday–Sunday

  • A year runs January 1–December 31

Example:

Let’s say you have a rule that sends 20% of incoming funds to Investments.

If a large one-time deposit shows up, the limit prevents over-transferring.

Set a monthly limit of $5,000 — once that cap is reached, no more funds move that month.

This keeps automations smart and safe.


Transfer Up To

What if the full amount isn’t available in the source account?

By default, the transfer won’t run unless the entire amount is present.

But if you check “Transfer up to [your-amount]”, Sequence will move as much as it can up to the defined amount.

  • If enough funds exist → full amount transfers

  • If funds are low → whatever is available transfers instead

This ensures something always moves, rather than the rule failing entirely.


Now you know the different types of actions you can create in Sequence — from simple transfers to advanced debt repayment strategies.

But actions don’t always need to run every time a trigger fires. Sometimes you want more control, like “only do this if my balance is above $500” or “skip this transfer if it’s after the 20th.”

That’s where Conditions come in.

On the next page, we’ll show you how to add conditions to your rules, and how Else and Else-If options let you build smart backup plans.


Did this answer your question?