Typeform
Turn each Typeform's responses into a RowFold table you can filter, sort and automate, and bring in new responses as they arrive.
Teams collecting enquiries, applications, orders or feedback in Typeform, Jotform or Tally, who need each response owned by somebody, followed up and counted instead of left in the form tool's results screen.
Turn each Typeform's responses into a RowFold table you can filter, sort and automate, and bring in new responses as they arrive.
Pull a Jotform's submissions into a RowFold table, questions as columns, and bring in new ones as they arrive.
Import a Tally form's submissions as a table you can filter, assign and automate, and bring in new ones as they arrive.
Import the form, then add the two fields a form tool doesn't have: who owns each response and how far it has got. Those two turn a list of answers into a queue nobody can lose track of.
You'll know it worked: Compare the table's row count with the number of responses the form tool shows. Then make yourself the Owner of one response and check it appears in your My Work.
An import runs at most hourly, even kept in sync, so it can't do this. A RowFold form can: each answer becomes a record in your table as it is sent, and owners, statuses and automations apply from the start.
You'll know it worked: Submit the RowFold form yourself. A record should appear in the table at once, and the automation's run history should show that it ran.
A form tool's results screen is a list to read, not a queue to work. Nobody can see which responses have been answered, who picked each one up, or which have been sitting for a week.
Import a form and each response becomes a row with a column per question. Add a status and an owner, and the list becomes a queue: everybody sees their own responses in My Work, and a view shows what is still waiting.
People answer in whatever shape they like. A company name typed three ways, a budget written in words, a date in two formats: none of it groups or adds up.
Imported columns are ordinary fields, so you can retype and tidy them. A column of company names can become real links to your Companies table with Convert to Relation…, which matches by name and leaves anything it can't match as typed.
An import runs when it is asked to, even on a schedule, and it is easy to build a process that assumes each response arrives the moment it is sent.
The first import brings a form's responses in as a table, up to 10,000 of them, and each import after that adds new responses to the same table; Keep in sync runs it hourly or daily. For intake that has to arrive the moment somebody submits, build the form in RowFold, where every answer is a record the instant it is sent.
On a schedule, yes. Importing again adds the responses sent since to the same table, and Keep in sync does that hourly or daily, so an automation on the table picks each one up when the run lands. That suits a backlog, reporting, or intake that can wait an hour. When new submissions must become records the moment they are sent, build the form in RowFold instead, where each one is a record as it arrives.
Typeform signs in with your Typeform account, so there is nothing to copy. Jotform and Tally each take an API key made in their settings, and a read-only key is enough for Jotform. Typeform and Jotform accounts hosted in the EU, and Jotform's HIPAA accounts, need their region set on the connection.
They come across as links to the copy the form tool keeps, not as files in RowFold. The file stays where it is and follows the form tool's retention rules. When the documents are the point of the form, such as CVs or signed consent, plan early how to keep them, because a link stops working when the form tool deletes the file.
No. The connections only read, so nothing you do in RowFold changes a form or its responses, and no automation can. The form tool keeps the record of what people actually submitted, and the RowFold table is the working copy where owners, statuses and notes go.
When the answers are the start of a process. A RowFold form writes straight into your table, so an automation can assign, notify or reply the moment somebody submits, and its questions are the table's own fields. Stay with Typeform, Jotform or Tally when you rely on something only they do, such as payment fields or a particular conversational layout.
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.