Teams whose delivery lives on monday.com boards and whose monthly reporting is a person exporting several boards into a spreadsheet and reconciling them by hand.
Pull monday.com 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 monday.com 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 monday.com, 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 monday.com and RowFold, this page is the authority: it is generated from the connector's own code.
Each board becomes its own table with its columns mapped to real field types. Bringing several across is the point rather than a side effect: once they are tables, the question that spans them becomes an ordinary filter instead of an export.
You'll know it worked: Compare a new table's row count against the board in monday with subitems collapsed. Those should match. A lower count here is nested subitems, not a failed import.
The step wants the board id, and the board id is simply the number in the board's URL. That is the one thing that turns a correct-looking automation into a green run with nothing on the board.
You'll know it worked: Run it once with a test record and check the item appears on the intended board, not merely that the run went green. Nothing in the run log can tell the difference between the right board id and a plausible wrong one.
The board is the unit of everything. One board is clear, and a question spanning twelve of them — what is late, who is overloaded, which client costs most to serve — has no home, because monday answers per board.
Imported boards are tables. Group, filter and total across all of them at once, and save the answer as a report rather than rebuilding it monthly.
Columns are per board, so the same idea is spelled three ways across three boards and no rollup can span them. Standardising means editing every board and hoping nobody adds a fourth.
Add the field once, to your own table, and every row in it has that field. Nothing about it depends on which board the work started life on.
The work is not attached to the thing it is for. A board of installs knows nothing about the contract, the invoice or the equipment, so the cross-reference happens in somebody's head or not at all.
Link imported items to your customer, deal or asset records, and the operational story and the commercial one finally sit in the same place.
Anything captured outside monday has to be retyped into it, so it arrives late or never. A form submission becomes an item when somebody gets round to it.
An automation files the item as part of the thing that already happened, so the board stays current without anybody copying between tabs.
No. Only the board's top-level items become rows, and the import reports that in its warnings rather than leaving you to work it out. A team that nests heavily will see a smaller table than they expected. The warning exists because a silently flattened hierarchy looks exactly like an import that lost records, and those two want very different responses from you.
It can. Importing a board again updates its table, matched on monday's item IDs, and Keep in sync runs that hourly or daily; nothing is ever written back to monday. On the Free, Basic and Standard plans monday allows 1,000 API calls a day across the whole account, so a large board there is better synced daily than hourly. The intended shape is still that monday runs the day-to-day work while RowFold holds everything the work connects to and answers the questions spanning boards.
In the board's URL. Open the board in monday and the long number in the address bar is the id. It does not change, so you can paste it into the automation and leave it. This is worth being careful with, because an id from the wrong board produces a successful run and an item nobody finds until somebody asks where it went.
Mostly, yes. Columns are mapped to real field types rather than arriving as text, so a date behaves like a date and a number totals. Where a monday column has no clean equivalent it lands as text, which is honest rather than clever: a wrong type that looks right is probably worse than a plain one you can convert deliberately afterwards.
Connecting requires that the app can be installed on the monday account, and installing is an admin action. If you are not an admin you will get as far as the install screen and no further. Ask an admin to connect it once; after that the connection belongs to the workspace and other members use it without repeating the step.
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.