Integrations without rip-and-replace.

Most automation pitches come with a hidden line item: replace your systems first. We take the opposite position. The tools your company already runs are where the truth lives, and an agent's job is to work inside them, not to move you off them.

Four ways in

1. An API, when there is one. Modern CRMs and ticketing systems expose almost everything. This is the clean path and we take it whenever we can.
2. The database, read-only. Older systems often have no API but a perfectly good database. Reading from it directly is safe; writing to it is not, so writes go through the application.
3. Files and email. A surprising amount of enterprise integration is a CSV in a folder or a PDF in an inbox. Agents are good at these.
4. The screen itself. For the system that has none of the above, the agent operates the interface the way a person would. Slower, more fragile, and sometimes the only honest option.

The integration layer is separate from the agent

Agents change. Models improve, prompts get rewritten, workflows get extended. Integrations should not have to change with them. So every system connection lives in its own small service with a stable contract: get this record, update these fields, list what changed since. The agent talks to that contract, never to the raw system.

This is also what makes replacement painless if you ever do decide to change a tool. Swap the connector, keep the agent. It is also the layer an MCP server sits on when you want AI assistants to reach the same systems.

Things that go wrong, and what we do about them

• Rate limits. Every connector queues and retries. Nothing calls a system in a tight loop.
• Duplicate writes. Every action carries an idempotency key, so a retry cannot create the same record twice.
• Field drift. Someone renames a field in the CRM. The connector notices on its next check and raises it before an agent writes garbage.
• Permissions. Each connector runs as a named service account with the minimum access the workflow needs, and nothing more. Anything that moves money still waits for a human approval.

If the integration is invisible, we did it right. Your team should notice the work getting done, not the plumbing.