I spent a good bit of time trying the Zapier integration and considering what might be good capabilities for import capabilities.
Regarding Zapier integration, it works well but it is only able to import one row at a time. So that works well for importing new items as they arise, but it is not really useful for importing an existing set of data. Also even if it were possible to import multiple rows, the Zapier cost structure is on the order of about 1-2 cents per record imported. That would not be ideal if my goal is to regularly import data sets with 1,000 or more records. My work involves commentary/annotation of academic citations in medicine, where such datasets are common and freely accessible to the public, such as for example the National Library of Medicine Pubmed database; it would be terrific to be able to include such data in a Coda project.
That said, I think I can suggest a plan for data import which is simpler than my original suggestion and which would generalize to use cases of many other Coda users. May I suggest that in addition to “Import CSV” to a table, adding “Import XML” and “Import JSON” would be a tremendous help. While importing from a local file would be workable, even better would be the ability to also enter the URL of a file containing XML or JSON data and to save “Favorite” URL locations for such data. This would make it easy to regularly update data from all sorts of public databases which contain information in these formats. I believe this would be of very wide interest for all sorts of users of Coda.