Can iDBQuery read XML files?
iDBQuery works natively with tabular and document files (CSV, Excel, Google Sheets, JSON, PDFs), so the reliable route for XML is to convert or export it to CSV or JSON and ingest that, or, for an XML API feed, point the REST connector at the endpoint. Both give you a live queryable model.
iDBQuery's file ingest is built around tabular and document formats, CSV, Excel, Google Sheets, JSON, and PDFs (with OCR). Raw XML is not treated as a first-class table format the way those are, so the honest answer is that XML needs one small step to become queryable, and there are two dependable paths.
- Convert or export to a supported format. Most systems that produce XML can also export CSV or JSON, and simple converters turn an XML file into a flat table. Ingest that CSV or JSON and iDBQuery builds a live, queryable model from it. This is the smoothest route for one-off files and exports.
- Point the REST/API connector at an XML feed. If your XML is served from an HTTP endpoint (many older APIs and RSS-style feeds are), the API connector can fetch it and map the structured response into a table on a schedule.
Once the data is in, you ask questions in plain language and every figure is cited to the source rows, exactly as with any other source. Because iDBQuery builds one model, the converted XML data can be joined to your databases and spreadsheets in a single answer. If your XML is deeply nested, flattening the specific elements you care about into columns during conversion gives the cleanest analysis. The key point: XML is fully usable, it just comes in via conversion or the API connector rather than as a native file type.
Updated 2026-06-22