Skip to main content

πŸ“‹ Lesson 5.2: Card & Board Buttons

Rules fire on their own; buttons wait for you. A Butler button is a one-click control that runs a whole sequence of actions the moment you decide β€” the perfect tool for multi-step setups you want on demand, not automatically. And here's the quiet superpower: personal button runs are effectively unlimited, so buttons let you automate freely without touching your metered command budget.

πŸ“š What You'll Learn

By the end of this lesson, you will be able to:

  • Explain the difference between a card button and a board button
  • Understand why buttons are "on-demand" automation and how that differs from a Rule
  • Build a multi-action button from Butler's plain-English builder
  • Create genuinely useful buttons: a "start work" setup, a date-stamped move, and a board-wide archive
  • Decide when a button beats a Rule β€” and use buttons to save your metered command runs

⏱️ Estimated Time: 40 minutes

🎯 Project: Build one board button ("πŸ“₯ Archive everything in Done") and one card button ("▢️ Start" β€” move to Doing, add yourself, set a due date), then use them for real.

In This Lesson

On-Demand Automation: What a Button Is

Last lesson, your Rules did things the instant a trigger fired β€” you moved a card, Butler pounced. But not every routine should be automatic. Sometimes you want to run a sequence when you say so: set up a fresh card exactly the way you like it, or sweep a whole list clean once you're ready. That's a button.

A Butler button is a labeled control that runs a saved list of actions in one click. Think of it as a Rule with the trigger removed and replaced by "when I press this." The "Do…" half is identical to a Rule β€” move, label, assign, set dates, archive, comment β€” but nothing happens until you tap it.

πŸ“– Definition

A button is an on-demand Butler command. It has a name, an emoji/icon, and a stack of actions. A card button appears on the back of every card and acts on that card. A board button sits at the top of the board and acts on the board as a whole (often a whole list of cards at once).

Because a button waits for your click, it's the natural home for the setups that are too situational to automate blindly β€” the "I want to start working on this now, so get it ready" moment, or the "it's Friday, clear the finished pile" moment.

βœ… Pro Tip: buttons protect your command budget

Remember the command-run meter from Lesson 5.1? Personal button runs are effectively unlimited β€” they don't eat into the Workspace command-run allowance the way automatic Rules and scheduled commands do. So if a routine can reasonably be a button you click rather than a Rule that fires on its own, making it a button is both more controllable and easier on your Free allowance.

Card Buttons vs Board Buttons

Both live under βš™οΈ Automation, in the Card Button and Board Button sections. They look almost identical to build β€” the difference is entirely about where the button appears and what it acts on.

Card buttons β€” act on one card

A card button appears when you open a card (on the card back, among the buttons and add-ons). Click it, and its actions run on that card. Card buttons are your "do this to the card I'm looking at" tools: start work, mark blocked, snooze to next week, escalate.

πŸ”˜ Card Button
Domove the card to list "Doing"
Dojoin the card (add me as a member)
Doset the due date in 2 working days

Notice there's no "When" row β€” a button's trigger is your click. Everything is a "Do."

Board buttons β€” act on the whole board

A board button sits in the board's top bar. It doesn't have "a card" to act on, so it works differently: it usually loops over a list of cards. That's what makes board buttons perfect for bulk chores β€” archive everything in Done, sort a list, or move a batch of cards.

πŸ”˜ Board Button
Doarchive all the cards in list "Done"
Dosort list "To Do" by due date (ascending)

⚠️ Watch Out: a card button needs a card

Because a card button acts on "the card," its actions assume there is one β€” so it lives on the card back, not the board bar. A board button, by contrast, has no single card in context, which is exactly why board-button actions are phrased as "the cards in list ___." If an action you want isn't offered, you're probably building the wrong button type for it. Match the button to what it acts on.

Building a Multi-Action Button

The builder is the same friendly dropdown flow as Rules β€” minus the trigger step. Here's the flow for a card button that gets a task ready to work on:

  1. Open βš™οΈ Automation β†’ Card Button β†’ Create Button.
  2. Give it a name ("Start") and pick an icon/emoji (▢️). This is what you'll click, so make it obvious at a glance.
  3. Click Add Action β†’ Move, choose "move the card to list β–’," pick Doing.
  4. Click Add Action β†’ Add/Remove (members), choose "join the card."
  5. Click Add Action β†’ Dates, choose "set due in 2 working days."
  6. Save. The button now appears on every card's back, ready to click.

Actions run top to bottom, so order can matter. If a button both moves a card and then sorts the destination list, the move needs to happen first. When something surprises you, re-read the action list in order β€” Butler does exactly what the sequence says.

graph LR A["πŸ‘† You click
the ▢️ Start button"] --> B["➑️ Move card
to Doing"] B --> C["πŸ‘€ Add you
as a member"] C --> D["πŸ“… Set due date
in 2 working days"] D --> E["πŸš€ Card is set up β€”
one click, three steps"]

πŸ’‘ "Working days" and other niceties

Butler's date actions are smarter than they look. You can set a due date "in 2 working days" (it skips weekends), "next Monday at 9am," or "the day after the current due date." You can also use variables in comments and card names β€” like the card's own name, the current date, or the member who clicked β€” but you can build a great button library without ever touching variables, so don't let them intimidate you.

Buttons Worth Building

A handful of buttons will cover most of what you do by hand. Steal these β€” adjust list and label names to match your board.

1. ▢️ "Start" β€” get a task ready to work on (card button)

The single most-used personal card button. One click turns a passive card into "I'm on it."

πŸ”˜ Card Button
Domove the card to list "Doing"
Dojoin the card and set the due date in 2 working days
Doadd the blue "in progress" label

2. ⏸️ "Blocked" β€” flag and date-stamp a stuck card (card button)

When work stalls, capture why and when without typing it every time.

πŸ”˜ Card Button
Domove the card to list "Blocked"
Doadd the red "blocked" label
Dopost the comment "Blocked as of today β€” waiting on someone."

3. πŸ“₯ "Archive Done" β€” clear the finished pile (board button)

The classic weekly cleanup, on demand. Your Done list stays a rolling record during the week, then one click clears the deck when you're ready β€” and because it's a button, it doesn't cost you a metered run.

πŸ”˜ Board Button
Doarchive all the cards in list "Done"

4. πŸ”€ "Sort & Tidy" β€” organize a list (board button)

Bring order to a messy backlog before a planning session.

πŸ”˜ Board Button
Dosort list "To Do" by due date (soonest first)
Domove all cards with the red "priority" label to the top

Here's a board mid-workflow, where the ▢️ Start button has just set up a card in Doing and the Done pile is waiting for a πŸ“₯ Archive Done click:

To Do 2
Fix the checkout bug
Write release notes
+ Add a card
Doing 1
Redesign the settings page
πŸ“… in 2 daysπŸ‘€ Me
+ Add a card
Done 3
Ship the newsletter
βœ“ done
Approve the mockups
Update the changelog
+ Add a card

Buttons vs Rules: When to Use Which

You now have two tools that run the same kinds of actions. The choice is entirely about who decides when it happens.

Ask yourself…Use a RuleUse a Button
Should this always happen when X occurs?βœ… Yes β€” automaticβ€”
Do I decide the right moment?β€”βœ… Yes β€” on click
Is it a bulk action on a whole list?Possibleβœ… Board button shines
Do I want to conserve metered runs?Runs countβœ… Personal runs ~unlimited
Setting up a card exactly how I like it?β€”βœ… Card button
Cleaning up the moment a card hits "Done"?βœ… Rule (auto)Possible

A good instinct: if forgetting to do it would be a problem, make it a Rule so it can't be forgotten. If choosing when is the whole point, make it a button. Many boards use both β€” a Rule to auto-clean Done as cards arrive, and a board button to archive the pile when it's time.

🧠 Mindset

Don't agonize over the choice β€” you can always convert one into the other later by rebuilding the same actions under the other type. The actions are the valuable part; the trigger (a click, or an event) is just a wrapper. Build the routine first, then decide how it should start.

🎯 Project: One Board Button + One Card Button

You'll build one of each β€” the two most useful buttons most people keep forever β€” and actually click them on real cards.

πŸ‹οΈ Build & use a Start button and an Archive-Done button

Objective: Create both button types, understand the difference by building it, and put each to work on your board.

Instructions (about 15 minutes):

  1. (4 min) Card button β€” ▢️ Start. Automation β†’ Card Button β†’ Create Button. Name it "Start," pick ▢️. Actions: move the card to Doing; join the card; set due in 2 working days. Save.
  2. (2 min) Open any To-Do card, click ▢️ Start on the card back, and watch it move, gain you as a member, and get a due date.
  3. (4 min) Board button β€” πŸ“₯ Archive Done. Automation β†’ Board Button β†’ Create Button. Name it "Archive Done," pick πŸ“₯. Action: archive all cards in list Done. Save.
  4. (2 min) Put a couple of test cards in Done, then click πŸ“₯ Archive Done in the board's top bar and watch the list clear.
  5. (3 min) Recover a card: open the board menu β†’ Archived Items β†’ send one back to the board, so you know archiving is safe and reversible.
πŸ’‘ Hint β€” the exact actions to aim for
Card button "▢️ Start":
  move the card to list "Doing",
  join the card,
  set due in 2 working days.

Board button "πŸ“₯ Archive Done":
  archive all the cards in list "Done".

If the Start button isn't on your card, confirm you built it under Card Button (not Board Button) and saved it. If Archive Done isn't in the top bar, it needs to be a Board Button.

βœ… Project Completion Checklist

  • You built a card button with 2+ actions and clicked it on a real card
  • You built a board button that archives a whole list
  • You clicked the board button and watched the list clear
  • You recovered an archived card, so you trust the "archive" action
  • You can explain why one is a card button and the other a board button

🎯 Quick Quiz

Question 1: What triggers a Butler button to run its actions?

Question 2: You want a one-click way to archive every card in your Done list. Which should you build?

Best Practices for Buttons

βœ… Do's

  • Name and icon for glance-ability. ▢️ Start, ⏸️ Blocked, πŸ“₯ Archive β€” you should know what a button does without reading it.
  • Prefer buttons for routines you time yourself. They keep control in your hands and spare your metered command runs.
  • Mind the action order. Actions run top to bottom β€” move before you sort, set before you stamp.
  • Test on a throwaway card. Click once and confirm the whole sequence did what you meant.

❌ Don'ts

  • Don't make a button for something that should always happen. If forgetting would hurt, that's a Rule, not a button.
  • Don't build a card button that needs a whole list. Bulk actions belong on a board button.
  • Don't hoard buttons. A card back crowded with rarely-used buttons is clutter β€” keep the few you actually press.
  • Don't fear "archive." Archiving hides, it doesn't delete β€” archived cards are always recoverable.

πŸ““ Learning Journal

Add a comment to your "Course Journal" card after this lesson. After each one, jot down:

  • Key concepts you learned
  • Techniques that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try on your own boards
  • Your progress and feelings about the way you work

✍️ This lesson's prompt: Think about a multi-step ritual you do by hand β€” the exact clicks when you start a task, or your Friday cleanup. Write it out as a button: name, icon, and the ordered "Do…" steps. Then note: should this stay a button you click, or become a Rule that fires on its own? Explain your choice in one sentence.

πŸ“ Lesson Summary

πŸŽ“ Key Takeaways

  • A button is on-demand automation β€” a saved stack of actions that runs when you click it, with no trigger.
  • A card button acts on the card you're viewing; a board button sits in the board bar and can act on a whole list at once.
  • Use a Rule when something should always happen; a button when you decide the moment. Same actions, different trigger.
  • Personal button runs are effectively unlimited, so buttons are a smart way to automate without spending your metered Free command allowance.

πŸŽ‰ What You've Accomplished

You now command both halves of everyday Butler: automatic Rules and on-demand buttons. Two clicks you built yourself now replace a dozen manual ones, and you understand the one decision that tells you which tool to reach for. Your board is genuinely faster to drive than it was an hour ago.

❓ Common Questions at This Stage

Does clicking a button cost me a command run?

Personal button runs are effectively unlimited β€” they don't draw down the Workspace command-run allowance the way automatic Rules and scheduled commands do. That's exactly why buttons are the frugal choice for routines you can happily click yourself. (Full budgeting math is in Lesson 5.3.)

Is "archive" the same as "delete"? Can I undo it?

No β€” archiving hides a card from the board but keeps it. Open the board menu β†’ Archived Items to find and restore anything. Deleting is separate and permanent. Your "Archive Done" button is completely safe: nothing is lost, just tucked away.

Can everyone on my board use a button I made?

Buttons you create as board or card buttons are available on that board to its members, so a team shares the same one-click tools β€” a great way to standardize how everyone starts, hands off, or cleans up work. Personal command buttons run under whoever clicks them.

πŸ”­ Looking Ahead

Next we add the final trigger type: time. Scheduled commands run on a clock (every Monday morning, the first of the month) and due-date commands fire around a card's due date (the day before it's due). We'll also do the honest run-budgeting math so your automations never quietly hit the monthly wall.

βœ… Before the Next Lesson

  • Keep your Start and Archive-Done buttons and use them for a few days
  • Notice one routine that would be better on a timer than a click β€” that's next lesson's fuel
  • Write your Learning Journal entry β€” your button-or-rule decision

πŸ“š Additional Resources

🌟 Encouragement for the Journey

Every button you build is a little lever you pull instead of a chore you slog through. You've turned two rituals into single clicks β€” and you did it without a line of code. One trigger type left to master: the clock. Let's make your board do things while you sleep. ⏰