Configure an integration and verify the handoff

Define the integration before connecting it

1. Name the handoff

   Write one concrete operation, such as importing a qualified website inquiry, sending a paid order to fulfillment or receiving a delivery update. Specify the initiating event and what success means.

2. Map authoritative records

   Define which system owns customer identity, product code, price, stock and order state. Map LeadID, AccountID, BasketID and external/import keys explicitly. Distinguish a record copy from a reference to the authoritative record.

3. Specify the contract

   Document required fields, types, identifier rules, validation, authentication and the response/error shape. Use the deployed generated API/harness or existing typed service contract to confirm operation names and parameters; do not infer an API from a screen label.

4. Define retries and reconciliation

   Agree how an operation is identified, how duplicates are rejected/reused and how an unknown external result is resolved. Payments and subscription creation require an explicit reconciliation path before a new operation is issued.

5. Configure in a test environment

   Use the intended provider/environment and approved test data. Test a valid operation, invalid required data, duplicate submission, provider rejection and interrupted response. Check the actual destination record or provider result.

6. Verify end to end

   Trace one record through source, transport, destination and operator UI. Confirm failure remains visible and recoverable. Record routes, IDs and evidence for the runbook.

7. Release with an owner

   Approve the release, rollback/recovery procedure and monitoring owner. Update the relevant operational guide with the actual deployment-specific controls and responsibility.