InfluxDB integration.

Define the row/document key, external application identity, required types, and relationship model. Decide how nested values, nulls, schema changes, and deleted parents appear in the other system. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Write-back support is not established for this connection. Review the InfluxDB records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

Define a time-series point by its measurement, timestamp precision, and tag dimensions. A timestamp alone may identify several distinct readings.

Agree on units, time zones, late-arriving corrections, and retention before comparing source points with destination aggregates.

Test two readings at the same time with different dimensions, a late correction, and a source point outside the retained history window. Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure.

Start with one workflow and a sample record from Buckets / databases, Measurements and Points. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.