How to Automate Trello

The board is how a team sees its own work

Trello is a board of lists and cards, and its whole appeal is that you can understand somebody else's work in about four seconds of looking at it.

That visibility is why it spreads through the parts of a company that never adopted a project tool. A small agency runs client work on it. A landlord runs maintenance requests. A workshop runs repairs, one card per machine, moving left to right as the job progresses.

The unit that matters is the card. A card is one real thing: a job, a fault, an application, an order. The board is honest only for as long as the cards match the things that actually exist in the world.

Which puts all the weight on how cards get made.

Cards get made by whoever remembers

The work arrives somewhere else first. It arrives as an email, a form submission, a phone call, an order in a system, a fault logged on a portal.

Then a person reads it and makes a card. They type a title, paste an address into the description, set a due date and drop it in the right list. It takes ninety seconds and it happens forty times a week.

Two things go wrong, and both are quiet. Cards that never got made, because it was busy on Thursday and nobody wrote it down, so a job simply does not exist as far as the board is concerned. And cards that were made but never updated, sitting in Doing for a fortnight after the customer cancelled.

A board people have stopped trusting gets checked less, which means it drifts further, which is how a team ends up back on a group chat.

Trello

Cards that create themselves A new order, application or fault becomes a card in the right list, without anyone transcribing it first.

Boards that match reality A job cancelled in the source system stops sitting on the board looking like work somebody still has to do.

Detail already on the card The reference, the address and the contact filled in, so nobody opens another system to start the job.

Butler acts on cards that already exist

Trello's automation is Butler, and it is genuinely capable for something included in the free plan.

Rules fire when a card is created, moved, labelled or has its due date arrive. Card buttons and board buttons run a set of actions on demand. Calendar commands run on a schedule, so every Monday you can sort, archive or move a batch of cards. Actions cover moving, copying, assigning, commenting, setting dates and posting to other lists.

Every one of those starts from something happening on the board. Butler is very good at what happens to a card once it exists.

It has no way to know that an order arrived in your ordering system, that a form was submitted on a site it cannot see, or that the job on that card was cancelled by a phone call this morning. The board can only react to itself.

The right card can appear on its own

The board reflects whatever was last typed into it, and nothing else. Everything missing from it was already recorded somewhere behind a login.

The overnight orders, each one a card in the intake list, with the reference and the delivery address already in the description. The faults logged on a customer's own portal, which is a site your team has a login for and no integration with. The applications submitted through a recruiting system, each becoming a card in the first column.

The updates matter as much. A job marked complete in the source system moves to Done rather than aging on the board. A cancelled visit gets archived instead of sending somebody out. A date that moved shows the date it moved to.

Worth deciding up front: let one system be the truth. If the board and the source system can both change a job's state, they will eventually disagree, and the disagreement will show up as an engineer standing outside a locked building.

Nobody has to transcribe the work first

Work arrives as an email, a form or a line in another system, and it becomes a card only when a person retypes it. That is not skilled work, but skipping it is how jobs get lost.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens the ordering system, the customer portal or the inbox where work arrives, reads what is there, and creates or updates the cards on your board to match.

It runs on your schedule in your own private environment, and you can watch a run and stop it. Anything that would contact a customer drafts and waits for a person.

The workflows below are already built, and each one shows the steps it takes.