Integration Health Check (QA)

Integration Health Check (QA)

1. 01

   Inventory every active integration and its data flow direction

   List each connector, the source and target systems, and the sync frequency. Confirm the list matches the client's current tech stack, not the one from the original statement of work.

2. 02

   Verify connector versions against vendor deprecation notices

   Check the iPaaS vendor's changelog for any connectors that are deprecated or scheduled for retirement. A deprecated connector can break a workflow without any code change on your side.

3. 03

   Test error handling on a sample of failed syncs

   Pull the last 50 failed runs and categorize the root causes: schema mismatches, authentication expiry, rate limits, or payload size. Confirm each failure triggered the correct alert and retry logic.

4. 04

   Review field mapping against the client's current data model

   Compare the mapped fields in each integration to the client's CRM and database schemas. Flag any fields that have been renamed or removed since the integration was built.

5. 05

   Measure sync latency against the service-level agreement

   Calculate the average time from source update to target update for each workflow. If any workflow exceeds the agreed SLA, document the variance and investigate the bottleneck.

6. 06

   Confirm monitoring alerts reach the right inbox or channel

   Send a test alert for each integration and verify it lands in the client's designated Slack channel or email. Stale alert routing is a common cause of silent data drift.

7. 07

   Document the health check results in a shared client log

   Record the date, findings, and any remediation actions in a shared document. This log becomes the evidence base for the next retainer renewal conversation.