Teams who run on Trello boards and have started keeping a spreadsheet alongside them, because the board shows what is happening and the spreadsheet is where anybody works out how much of it there is.
Pull Trello into RowFold tables you own — filter them, report on them, link them to everything else in the workspace.
And it stays current: importing again updates the same tables, adding new records and updating changed ones, so links from your other tables hold. Keep in sync does that for you hourly or daily.
Automation steps that act on Trello when something happens in RowFold:
What it doesn't do: It has no say in what a booking page offers. An import only reads: nothing is written back to Trello, a record deleted there stays here, and a sync runs hourly at most rather than the moment something changes. Anything else you have read about Trello and RowFold, this page is the authority: it is generated from the connector's own code.
Trello is the easiest migration of the set, partly because it connects with your own credentials rather than an approval flow, and partly because a board maps onto a table almost exactly: the lists become the status options rather than becoming eleven mystery columns.
You'll know it worked: Group the new table by List and compare each group's count against the board. Those should match card for card. If a list is missing entirely, it had no cards, which is worth knowing before you conclude the import skipped it.
The step adds a card to the end of a list, which is the behaviour most people want and worth knowing if your board is sorted rather than prioritised by hand. It needs to know which list, not just which board.
You'll know it worked: Fire it once with a test record and confirm the card is on the right list and its link is on the record, not merely that the run went green. Then re-run the same record: a second card means the guard is not doing its job.
A card carries almost nothing you can count: a due date, a label, a list. Everything else people actually need probably lives in the description, typed differently by everyone, which is why the reporting spreadsheet exists.
Add the fields the work really has, with types that hold. A number is a number on every card, so totals are arithmetic rather than a person reading descriptions.
Power-Ups solve one board at a time and cost per board. The one you need for reporting is the one you have to add, configure and pay for on each board separately, then keep in step.
The fields, the views and the reports belong to the table. Nothing has to be repeated per board, and nothing depends on which board the work started on.
Nobody can ask one question of every board. What is overdue across all of them, who is carrying the most, which client's work is slipping — each of those means opening boards and counting.
Imported boards are tables. Filter, group and total across all of them at once, and save the answer instead of rebuilding it.
No. Card fields only, and the import reports that in its warnings rather than leaving you to discover it. Plenty of teams keep the real substance of a card in its checklist, so this is worth knowing before you move several boards. If a checklist is genuinely the data, it usually wants to become its own table of rows linked back to the card.
Trello splits them: the key identifies the application and the token authorises your account. Both come from your own Trello developer page and both go in. The commonest mistake is probably pasting the token into the key field, which connects without complaint and then fails on the first read, so it looks rather like a problem with the board than a swapped pair of values.
They become the options of a Select field, in the order they sit on the board. That is the mapping that makes a Trello import feel immediately right: you can group by List and get the same columns you were already looking at, except that now you can also filter, total and report across several boards at once, which the board itself will never do.
It can. Importing the board again updates its table, matched on each card's Trello ID, so a card moved to another list changes list here and new cards are added; Keep in sync does that hourly or daily. Nothing is written back to Trello. A card archived on the board stops updating but stays in the table, which is worth knowing before you count it. Most teams settle on Trello for the daily card-moving and RowFold for the questions that span boards.
Right now. Trello is one of the connectors where you supply your own credentials rather than relying on an application we registered with the vendor, so there is nothing to wait for and nothing that can be pending at our end. Paste the key and token and the board list appears.
There is no template to wait for. Type a sentence about what you run and RowFold assembles the tables, links, views and dashboard around it — then you change whatever does not fit.