Teams planning work in Asana who have reached the point of exporting projects to a spreadsheet every month, because the question they need answering spans projects and Asana answers it one board at a time.
Pull Asana 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 Asana 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 Asana, 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 Asana and RowFold, this page is the authority: it is generated from the connector's own code.
Each project you pick becomes its own table, one row per top-level task, with the same eleven columns every time. That last part is what makes bringing several across worth doing: the tables arrive the same shape, so they can be compared, combined or linked afterwards without any tidying up.
You'll know it worked: Open one of the new tables and compare the row count against the same project in Asana with subtasks hidden. Those two numbers should match. If yours is lower, the difference is nested subtasks, not a failed import.
This is the thing Asana structurally cannot do and the reason most people arrive here. Once the projects are tables, the question is an ordinary filter — but only if the tasks from different projects can be told apart, which takes one column.
You'll know it worked: Filter to incomplete tasks with a Due date in the past and check the count against what you would have got by opening each board and counting. The first time, do it for two projects by hand: if they agree, the rest will.
The step wants the project's numeric ID rather than its name, which is the one thing that catches people out. Asana puts that ID in the URL of the project, and it never changes.
You'll know it worked: Trigger it once with a test record and check the task appears in the right project rather than merely reporting success. A green run with nothing in Asana almost always means the project ID was a name, or a number from the wrong project.
A project is a silo. Any single board is perfectly legible, and the question people actually ask — what is late across all forty, who is carrying too much, which client absorbs the most hours — needs all of them at once, which is exactly the shape Asana is not.
Imported projects are ordinary tables. Ask across them, group by assignee or section, total whatever you total, and keep the answer as a saved report rather than a spreadsheet somebody rebuilds each month.
The work is not attached to the thing the work is for. A project called “Harborline rollout” knows nothing about the Harborline contract, the invoice, the kit on site or the renewal date, so every cross-reference happens in somebody's head.
Link the imported tasks to your client, deal or asset records. Delivery and commercial finally sit in one place, which is the reason to do this at all rather than admiring a copy of your board.
Custom fields are per project and mostly per paid tier, so the field you need on every project either does not exist on half of them or is spelled differently on each.
Add the field once, to your own table, and it applies to everything in it. Nothing about it depends on which Asana plan the project was created under.
Reporting across projects means a monthly export, a pivot table, and a set of assumptions nobody wrote down. The number is stale the day it is produced and unreproducible the month after.
The report reads the tables directly and is current whenever it is opened. The assumptions live in the report's own filters, where somebody else can read and argue with them.
No, and the import tells you so in its warnings rather than leaving you to work it out. Only the project's top-level tasks become rows. A team that nests work heavily will see a smaller table than they expected, which is why the warning exists: a silently flattened hierarchy reads exactly like an import that dropped records, and the two want very different responses.
Almost always because it is archived. The list deliberately offers non-archived projects only, across every Asana workspace your account belongs to. If the project you want is genuinely active and still missing, check which workspace it lives in and that the account you connected is a member of that workspace rather than a guest on the project.
It can, one way. Importing the project again updates its table, matched on each task's Asana ID, and Keep in sync does that hourly or daily; nothing is ever written back to Asana. An edit made here to a column the import fills goes back to Asana's value on the next run, so the intended shape is that Asana keeps planning the work and RowFold holds everything the work connects to, in columns and tables of its own.
The assignee arrives as their name in a text column, not as a link to a person in your workspace. That is deliberate: an Asana account and a RowFold member are different things, and matching them automatically on a name would be wrong exactly when two people share one. Converting the column to a People field afterwards is a normal thing to do once you have checked the names line up.
The import paces itself for the free-plan limit of 150 requests a minute, because your plan is not knowable up front and being throttled mid-import is worse than being slightly slower. On a paid Asana plan the ceiling is ten times higher and the import simply finishes sooner. Either way it runs in the background, so a slow one does not hold a page open.
Probably not, and the page is not arguing for it. Asana is good at planning work and at the daily rhythm of a team working a board. What it cannot do is answer a question spanning forty projects, or connect a task to the contract, invoice and equipment it exists because of. That second half is the part worth moving.
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.