Integrations and source ownership

• Flight information source. Configure an airline or airport feed if the team wants scheduled arrivals from an external source. Agree how the flight number, scheduled arrival and passenger count map to the trip being supported. The source owner decides which update takes precedence when arrival information changes.
• Accounting platform. Set up an export or other agreed connection for reviewed trip charges and confirmed document amounts. Finance Officer owns the reconciliation and correction procedure. Check source references before accepting repeated deliveries of the same financial event.
• Staff identity source. If the team uses a separate staff directory, agree how its accounts map to people in the app. Admin checks the active staff identity before the associated person submits dispatch or service work.

Each connection is a setup decision with a named owner, a field mapping and an agreed source of truth. Keep credentials in the approved secret store. Decide how repeated, changed and rejected source records are handled before enabling scheduled exchange.

Rehearse a changed flight arrival, a repeated financial event and a disabled staff account. Compare the accepted result with the source and retain the explanation for rejected updates. A connection needs the provider’s access and configuration as well as a successful pilot.

Use implementation to agree the first connection and its acceptance case.