Integrations and source ownership

• Weather stations and services. Readings come from your station network or weather service. Agree which reading counts for each station and how it becomes a draft observation.

• Sprayer and application logs. Application records from sprayer controllers or field apps are the external reference that completed work is checked against.

• Agronomy and scouting tools. Trap counts, soil moisture and scouting notes can arrive as evidence lines with their source reference.

• Identity provider. Map team members to user accounts. Disabling a person’s sign-in must also remove their access here.

• Accounting. Advisory fees and invoices stay in your accounting system.

Each connection needs an agreed source of truth, field mapping, event identifier and retry policy. Keep credentials in the approved secret store and grant the smallest permitted scope. A repeated reading must not create a second observation, and a repeated completion must not complete work twice. Queue rejected records with their source identifier and a visible reason.

Reconcile source totals to accepted, rejected and pending events. Review a provider timeout, a duplicate delivery, a changed source record and a revoked credential before enabling schedules. Availability depends on each provider’s API, commercial access and configuration.

Use the implementation plan to agree integration acceptance criteria.