Teams using Jotform for real operational intake: registrations, claims, service requests, site inspections. The form is doing its job and the queue behind it is an inbox.
Pull Jotform 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 Jotform. It has no say in what a booking page offers. An import only reads: nothing is written back to Jotform, 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 Jotform and RowFold, this page is the authority: it is generated from the connector's own code.
The import maps questions to columns, so the table you get depends on how the form is built. Ten minutes tidying question titles in Jotform first will save renaming a dozen columns afterwards, because a question titled “Untitled” becomes a column called that.
You'll know it worked: Compare the row count against the submission count Jotform shows for that form. If a column is full of blanks, check whether that question was added after most submissions were collected — which is accurate rather than a fault.
Importing gives you every submission at once, so the first job is finding the few that can't wait. A saved view does that, and an owner on each one keeps it from slipping back into the pile.
You'll know it worked: Check the view against Jotform's own results filtered the same way. Assign one submission to yourself and confirm it leaves the view and appears in your My Work.
Submissions arrive as email and live in an inbox. There is no assignee, no status and no way to see what is outstanding, so the queue is whatever each person remembers to deal with.
Submissions become rows with a status and an owner. What is outstanding is a filter, and nothing sits unhandled without somebody being able to see it.
Every question about volume means exporting. How many this month, from where, how long they take to clear: each one is a CSV download and a pivot table built from scratch.
The report reads the table and is current when opened, with its filters written down where a colleague can check them.
A submission is disconnected from everything it concerns. A claim arrives about a job that already exists somewhere, and nothing joins the two, so every one starts with working out what it relates to.
Link submissions to the jobs, sites or customers they are about, and each arrives attached to its own history.
The submission comes across with the answer as Jotform records it, which for an upload is a link rather than the file itself. That means the file stays where Jotform keeps it and stays subject to Jotform's own retention. If those documents are the point of the form, it is worth deciding early whether they should be pulled into RowFold's own attachments rather than left as links.
Probably because the account is EU or HIPAA hosted. Jotform runs those on separate hosts from its main API, and nothing in the key itself says which one it belongs to, so a connection pointed at the default host is refused even though the key is fine. The region is a setting on the connection rather than a guess. Check which Jotform address you sign in at first.
No. The connector reads submissions rather than listening for them, though Keep in sync can re-read the form hourly, and an automation on the table then fires for each new submission as that run lands. For intake that needs acting on the moment it arrives, such as claims or urgent requests, collect it with a RowFold form instead, where each submission is a record at once.
Importing again updates the same table, and a question you add arrives as a new column, empty on submissions from before it existed, which is accurate rather than broken. Questions are matched on Jotform's question ID, so a retitled question keeps its column and a removed one keeps its answers. If you have restructured a form substantially, cloning it in Jotform and importing the clone gives a clean table, since a new form is a new source.
A RowFold form writes straight into a table you own, with no import step and no second copy of the data. This connector is for teams already committed to Jotform — often for its payment fields, conditional logic or compliance options — who want the submissions somewhere they can be assigned and counted. If you have not chosen yet, the built-in forms are the shorter path.
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.