Teams whose good form has become a queue: applications to sift, briefs to assign, enquiries to chase, all currently handled by scrolling a results page and copying into a spreadsheet.
Pull Typeform 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.
What it doesn't do: There are no automation steps that write back to Typeform. It has no say in what a booking page offers. An import only reads: nothing is written back to Typeform, 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 Typeform and RowFold, this page is the authority: it is generated from the connector's own code.
The import turns each response into a row with a column per question. The part worth planning is what you add afterwards, because a status and an owner are what turn a list of answers into a queue that cannot lose anybody.
You'll know it worked: Compare the row count against the response count Typeform shows for that form. They should match. Responses are read newest first with a cursor, so a form that receives a submission while the import runs still arrives complete.
An import brings in every response at once, so the job is sorting the handful that matter from the rest. A filtered view finds them, and giving each an owner makes sure somebody answers.
You'll know it worked: Filter Typeform's own results the same way and compare the counts. Then take one response from the view and check it disappears from the view and shows in your My Work.
Typeform's results are built for reading, not for working. Nothing there marks one as handled, assigns it to somebody, or shows only the ones nobody has dealt with, so the real queue usually ends up in an exported spreadsheet.
Responses become rows. Add a status and an owner, filter to what is outstanding, and the queue is the table rather than a copy of it.
The response is disconnected from everything it is about. A brief arrives from a client who already exists somewhere, and nothing joins the two, so every submission starts by working out who this is.
Link responses to your client, deal or project records, and each one arrives attached to its own history.
Reporting means exporting. Every question about volumes, sources or trends is answered by downloading a CSV and building the same pivot table again, and the answer is stale the day it is made.
The report reads the table directly and is current whenever it is opened, with its filters written down where somebody else can read them.
Not the instant. Keep in sync re-reads the form hourly, and each new response becomes a record in the same table, so an automation watching that table fires on the next sync rather than within seconds. Typeform can push a webhook on every submission and the consent screen already asks for the permission that would need, so the day live triggers are built nobody has to reconnect. Until then, a RowFold form is the way to act on responses the moment they arrive.
Typeform hosts EU accounts on a separate API address, and nothing in the sign-in flow reveals which region an account belongs to, so the connection defaults to the main one and finds nothing. That is why the region is a setting on the connection rather than a guess. An empty form list on an account you know has forms is almost always this.
The first table is updated. Responses are matched on Typeform's own response ID, so a second import adds the ones submitted since and leaves the rest where they are, along with the statuses and owners your team added, because those are columns the import never writes. Within one import, responses are read newest first with a cursor, so a form that receives a submission while the import runs still comes across whole, without gaps or duplicates.
No. The connection reads and never writes, so nothing you do in RowFold alters a form or its responses, and no automation can. Your form remains the record of what people actually submitted, which is the right way round: the working copy is the one you should be adding statuses and owners to.
Importing again updates the same table. A question you add arrives as a new column, empty on responses collected before it existed, which is accurate rather than a fault. Questions are matched on Typeform's ID rather than their wording, so a reworded question keeps its column and a deleted one keeps the answers already given. The import never renames a column, so rename one here yourself if its old wording now misleads.
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.