MongoDB

Source + Destination — Vendo imports MongoDB collections into your data warehouse for analytics, and can export modeled data back to MongoDB. Each collection syncs as a full refresh or via incremental change-data-capture.

What Vendo Imports

Vendo connects to a single database in your MongoDB deployment and imports the collections you select, preserving document structure for analysis.

Supported Data

Data	Description
Collections	Any collection in the connected database
Document Fields	Nested document structure is preserved for analysis

Sync Behavior

Behavior	Description
Collection Discovery	Vendo lists collections in your database automatically
Per-Collection Selection	Choose exactly which collections to sync
Per-Collection Sync Mode	Full refresh or incremental (CDC), set individually per collection
Batch Delivery	Data syncs in scheduled batch jobs

Platform Details

Setting	Value
Auth Method	Connection string (`mongodb://` or `mongodb+srv://`)
Connection Type	Batch sync (recurring or one-time)
Direction	Bi-directional (source and destination)
Sync Modes	Full refresh or incremental change-data-capture, per collection

Setup

1. Allow-list Vendo’s egress IP

All of Vendo’s outbound traffic presents a single static egress IP. Before connecting, add this IP to your MongoDB network access rules (in Atlas: Network Access > IP Access List). The setup screen in Vendo shows the exact IP to allow-list — for the production app it is 5.78.218.138.

2. Connect the app

In Vendo, add MongoDB as a new source
Enter your Connection String (mongodb:// or mongodb+srv://), for example mongodb+srv://user:pass@cluster0.mongodb.net/
Enter the Database to read collections from (and write to, when used as a destination)

3. Choose collections and sync modes

Once connected, Vendo discovers the collections in your database:

Each collection shows its document volume, and you can expand a row to preview its field schema. These come from cheap metadata — Vendo never scans your data to show them.
Toggle on the collections you want to sync
For each enabled collection, pick a sync mode:

Sync Mode	Behavior
Full refresh	Re-imports the entire collection on every sync
Incremental (CDC)	Imports only documents that changed since the last sync

4. Schedule the sync

Choose a Recurring sync (runs on a schedule) or a One-time sync, then save. Data is delivered in batches on that cadence.

Using MongoDB as a Destination

MongoDB can also receive data from Vendo. As a destination it accepts event, user, and custom data — so you can push modeled outputs (for example, enriched user profiles or model results) back into the same database your application reads from.

Troubleshooting

Connection failed — Verify the connection string starts with mongodb:// or mongodb+srv://, and that Vendo’s egress IP (shown during setup) is allow-listed in your network access rules
No collections found — Check that the database name is correct and the connecting user has read access to it
Volumes or schemas look incomplete — Discovery uses collection metadata, not a full scan; the actual sync imports complete documents

BigQuery — Query warehouse tables directly instead of importing
Webhook — Push data into Vendo in real time