Website: https://connectedconservation.foundation/
This integration requires assistance from our support team for setup and configuration. Please contact our support team at support@earthranger.com and we’ll guide you through the process to ensure everything is set up correctly.
We are actively working to make this integration self-service in the future. Stay tuned for updates!
Need this documentation before it's ready?
Let us know at support@earthranger.com. We're happy to help.
Prerequisites
Data Source
Data Delivery
Credentials or an authentication token to access the delivery system.
Configuration
Notes for Support (click to expand)
Go to Gundi v1.
Go to the Inbound Integrations and select Add Integration.
Follow the steps below to configure the integration:
Name: Enter any name for this connection.
Owner: Select the integration's owner.
Type:
Provider Key: Leave empty. Gundi will automatically give it a slug value.
Default Device Group: Leave empty. Gundi will automatically create a default group.
Endpoint:
Token:
Login/Password:
State:
{}Click Save.
Configure the Default Device Group to select the destination site.
Data Pull Frequency
Characteristics
Data Delivery
The time it takes for data to appear in your destination system depends on several factors, such as latency introduced by the source, network conditions, and intermediary systems. While these factors may vary, Gundi typically checks for available data at scheduled intervals (approximately every 10 minutes).
If data is not available in your system after this interval, please check the source of the data for its availability. If the issue persists, contact our Support team for assistance.
Tags: Data Provider, IoT Systems, Device Management, Movement Data, Gundi v1, Pull Integration
Last Update: June 17, 2025