Pilot watches for something happening on your board, checks an optional condition, then runs one or more actions for you, so the busywork of moving cards, assigning people, and setting due dates happens on its own.
01
Every automation in Pilot, no matter which sidebar section it was built from, follows the same three-step pipeline. Open Pilot from the lightning-bolt icon in a board's toolbar to build one.
What starts it: a card being created or moved, a due date, a schedule, or someone clicking a button.
A gate the triggering card has to pass, e.g. only run if a due date is set.
One or more things Pilot does for you: chain up to 10 in a single automation.
Whenever an automation actually runs, a line is written to the card's own Activity feed explaining exactly what happened and why. Automations never change something silently.
02
The general-purpose builder: pick a trigger, an optional condition, and chain as many actions as you need. This is where most automations get built.
Triggers
Actions
A Filter and a Libraries panel help you find existing rules and start from a ready-made template instead of building from scratch.
03
Runs on a recurring schedule you set, instead of waiting on something to happen to a card. There's no single triggering card, so it runs its actions against every card in a list you choose (or the whole board).
04
Fires relative to a card's own due date, rather than a fixed clock time, useful for reminders that should shift automatically whenever a due date changes.
Unlike Scheduled, Due date automations are shared board-wide, like Rules: every board member sees the same list.
07
Pilot watches this board's own activity for a pattern worth automating. Today it looks for one thing: cards getting moved to the same list over and over by hand. Once that's happened a couple of times, a ready-to-add Card button shows up here.
Creates the Card button immediately, pre-filled from the pattern Pilot noticed. No need to open the builder.
Not interested in this one. It's remembered per board, so the same suggestion won't come back.
08
Every board member can open Pilot, see the board's Rules, Due date, and button automations, and click a Card or Board button. Using a button someone else configured isn't a configuration change. Creating, editing, toggling, and deleting automations is Admin-only.
Scheduled is the one exception: it's private end to end. Only the admin who created a scheduled automation can see, edit, toggle, or delete it. Even another admin on the same board can't.
09
Pilot's sidebar mirrors the familiar shape of board automation tools for a reason: some sections are visible today as a preview of where it's headed, but aren't wired up to anything yet: