Forward data to MongoDB

MongoDB forwarding writes newly reported point records to an external database. The connection URI must include a database name, and the account needs write and required index permissions.

Configure the connection

A Manager or Owner can create a MongoDB profile under Organization → Data → Data Forwarding.

Field	Value
MongoDB URI	Connection string including the database name and required authentication parameters
Collection	The configured collection name; also check the organization collection rules below

Example URI:

mongodb://USER:PASSWORD@HOST:27017/DATABASE

Replace the example values and encode special characters in credentials as required by the URI format. Saved credentials are not displayed in plain text; follow the edit hint to retain or replace them.

Find the records

By default, the collection is named after the organization slug. If a platform administrator has configured a fixed collection for the connection, that collection is used instead. Check the database in the URI and the organization-slug collection rather than looking only for the name entered in the form.

Documents contain the point identifier, timestamp, value, and other reported fields. Additional fields can differ by source. Inspect newly written documents before building queries.

Verify writes

1. Enable the profile and have a device report new data.
2. Find new documents in the target organization's collection.
3. Check agri_id, time, and value, and verify increasing sent counts.
4. Test a read using the time range needed by your reports.

No new documents

Check that the URI includes a database, the database is reachable from the cloud, and the account has write and index permissions. For authentication failures, check the authentication database and password encoding.

Use data export to download existing historical records. Adding a forwarding profile does not automatically import previous records into MongoDB.