- Industry
- IT Company
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Engineering Manager
- Code
- ENG-05
It designs and builds integrations between client systems and the SaaS products or between a client's own systems: field mappings, authentication, idempotent retries, rate limits and error handling. It tests against the client's sandbox first and documents the data flow for the client's data-processing agreement.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the source code repository and CI/CD: existing integration code, API specifications and the sandbox test results..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Engineering Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the source code repository and CI/CD: it opens a pull request with the integration and its data-flow document. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The integration playbook: integration patterns, authentication methods, retry and idempotency rules, data-flow documentation templates and the data-processing agreement requirements.
Reads from
the source code repository and CI/CD: existing integration code, API specifications and the sandbox test results.
Acts in
the source code repository and CI/CD: it opens a pull request with the integration and its data-flow document.
Hands back
An object with mapping (a list of source, target and transform), auth_method, retry_policy, rate_plan, data_flow (a list of system, data and country) and test_results (or null).
Asks a person when
The integration moves personal or client-regulated data, writes to a client production system, or sends data to a new country.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most retries | 5 | Failed calls retry this many times with backoff. |
| Rate limit headroom (%) | 20 | Traffic stays this far below each API limit. |
| Personal data in transit | masked | How personal fields are handled in logs and queues. |
| Test in the sandbox first | On | When on, nothing touches a client production system before a sandbox pass. |
| Alert after dead letters | 10 | This many failed messages raise an alert. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Make every write idempotent and retry at most 5 times with backoff.
- Keep traffic 20 percent under each limit.
- Handle personal fields as masked and document every field crossing a system boundary for the client's data-processing agreement.
- When on is true, nothing reaches a client production system before a sandbox pass.
- Alert after 10 dead letters.
- Integration credentials live in the secrets manager, scoped to least privilege, never in code.
See the API Integration Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.