Integrations / MongoDB
MongoDB
Document-oriented NoSQL database
Custom
Indexes
Actions
What Telara does
Capability matrix
Before you connect
Prerequisites
A MongoDB deployment Telara can reach.
A database user that can read the collections Telara should see. Prefer that over an Atlas admin.
Vendor setup
Get the credential
1
Create a database user
In Atlas (or your self-hosted deploy), create a read user and copy the connection string.
2
Paste in Telara
Settings → Integrations → MongoDB. Paste the connection string and the database name.
In Telara
Connect in Telara
Custom
MongoDB connection string with embedded credentials, plus target database name
In Telara, open Settings → Integrations, choose this connector, and complete the fields Telara shows.
Fields Telara asks for
- Connection String
- Database
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Collection schema | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Collection schema | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Collection schema.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty
Known limitations
Network path is the usual failure (IP access list, private endpoint, or a string that only works on your laptop).
A user that can authenticate but cannot read catalogs produces an empty view, not an auth error.