Setup guide · MongoDB
MongoDB in Dataki: a CSV export, or a copy in BigQuery
Dataki has no MongoDB connector, and MongoDB's own SQL interfaces are not ones Dataki can use. Two routes work today: a CSV export you upload, which takes minutes, or a copy in BigQuery made by Google's Dataflow template, which Dataki then queries like any dataset.
- MongoDB
- CSV or BigQuery
- Dataki
- Setup
- Five minutes for a CSV export. About 20 for a BigQuery copy.
- Cost
- An upload is free. A Dataflow job is billed by Google for the time it runs.
- Freshness
- As fresh as your last export or job run.
- Best for
- A CSV for one question now. BigQuery for dashboards that should keep working.
01Before you start
-
mongoexport, from the MongoDB Database Tools, for the CSV route. - A Google Cloud project with billing, for the BigQuery route.
02Set it up
3 steps, about 5 minutes
- 01
Route one: export a collection to CSV
CSV needs the fields named. Dot notation reaches into embedded documents:
Terminal mongoexport --uri="mongodb+srv://user:password@cluster.example.net/shop" \ --collection=orders --type=csv \ --fields=_id,status,total,createdAt,customer.country \ --out=orders.csv- Upload
orders.csvat app.dataki.ai/connect, under files. Dataki loads it into a table and queries it with full SQL. - Dataki loads every CSV column as text and casts in SQL, so name the number and date columns in your first question and check the casts in the SQL it shows.
- Upload
- 02
Route two: copy it into BigQuery
In the Google Cloud console, open
Dataflow›Create job from templateand pickMongoDB to BigQuery. Give it the connection URI, the database, the collection and an output table such asyour-project:mongo.orders.Set the
userOptionparameter toFLATTEN, which makes each top-level field a column. Left atNONE, each document lands as one JSON string in asource_datacolumn.Each run appends to the table, so a second run doubles every document. To refresh the copy, empty the table first with
TRUNCATE TABLE mongo.orders, then run the job again. - 03
Connect the dataset in Dataki
Open app.dataki.ai/connect and, under
Linked Google Cloud Projects, chooseLink New Google Project. Sign in with a Google account that can manage IAM in the project holding the data, and pick that project. Dataki creates a service account namedDatakiin it with two roles, BigQuery Data Viewer and BigQuery Job User: it can read tables and run queries.The project's datasets then appear among your sources. Pick
mongo. Each dataset is one source in Dataki, and the free plan includes one.
03Ask it
Your first questions
Once the data is in, it is a table like any other. For example:
How many orders did each country place last month?
What is the average order value by status?
04Worth knowing
What you will run into
- Both templates are in beta
- Google marks the MongoDB to BigQuery templates as beta. For a continuous copy, Google's Datastream also replicates MongoDB 5.0 and later into BigQuery and is generally available, but Google does not yet document how the documents are laid out there.
- Dataflow has to reach your database
- The job runs on Google's Dataflow workers, which connect to MongoDB themselves. On Atlas, that means allowing the workers' addresses in the IP access list, or giving the job a fixed address through Cloud NAT.
- Arrays do not fit in a CSV
- An array field exports as its JSON text. Export array elements as a separate collection, or use the BigQuery route, when you need to count them.
Checked against
Last checked 15 September 2026.
Free while we are in beta
Connect MongoDB. Ask it something.
Once the data is where Dataki can read it, the first answer is a question away, and anything worth keeping becomes a dashboard with a link that stays live.
- One data source
- Free tier. Connect a second on any paid plan.
- Read-only
- Every query runs read-only. Dataki cannot change your data.
- No card
- There is nothing to cancel if you stop.