Overview

Integration agents validate service-to-service contracts, message queues, webhooks, and third-party dependencies. They focus on boundary failures that unit tests miss.

Enable agents per organization in Automation → AI Agents. Human review applies to generated output before release-critical use.

Who should read this

QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.

Prerequisites

Organization administrator approval to enable agent category
Staging or approved test environment reachable from execution plane
Requirement linkage for audit-oriented teams (recommended)

When to use this workflow

Microservice deploy verification
Payment provider sandbox regression
Event-driven workflow validation after schema change

Step-by-step procedure

Map dependencies

Platform → Topology → confirm dependency edges for target services.

Document sandbox credentials per integration.

Enable integration agents

Automation → AI Agents → Integration → Enable for affected services.

Run boundary suite

Trigger run scoped to integration category after dependent service deploy.

Key concepts

integration validation scope: Service handshake and retry behavior; Queue consumer processing under backlog; Webhook delivery and signature validation; Third-party sandbox API connectivity.
Check 1: Service handshake and retry behavior
Check 2: Queue consumer processing under backlog
Check 3: Webhook delivery and signature validation

Best practices

Use vendor sandboxes, not production third-party APIs
Isolate integration failures in Test Health by dependency label
Maintain fixture data synchronized with partner test environments