19 Mar 2026 · 8 min read
Integration patterns for agentic systems
Agents create value only when they can read and write the systems teams already live in — securely and with audit trails.
Treat integrations as product surface, not plumbing. The agent’s tools are the API of your automation programme.
Prefer read-first designs. Let the agent gather context and propose actions before granting write access to systems of record.
Make writes idempotent. Retries happen. Duplicate side effects destroy trust faster than a slow response.
Use events where possible: webhooks and queues keep agents responsive without brittle polling loops.
Document failure modes. When a connector times out, operators need a clear path — retry, escalate, or pause — not a silent stall.
Security and privacy are part of the pattern: short-lived credentials, scoped permissions, data minimisation, and audit logs for every consequential action.