Depth 14.3 · Web and product engineering · Level 3
Integrations
An integration is a connection that moves data between two systems automatically, for example from a website form into a CRM or from a billing tool into accounting. Integrations fail quietly: a changed field or an expired key can stop data flowing for days before anyone notices, so the work includes knowing when they fail.
Specification
- Input
- The systems to connect, admin access or API keys for each, and a description of which records must move and when.
- Method
- We map each field between the systems, build the connection with retries for temporary failures, log every transfer and send an alert when records stop arriving or start failing.
- Deliverable
- Running integrations with a field mapping document, logs and alerting, plus steps to rotate keys.
- Measured by
- Transfers that succeeded, failed or were retried, read from the integration logs, and time from failure to alert.
Most often bought inPayments and fintech, Logistics and supply chain, Ecommerce
The artefact, before and after
Running integrations with a field mapping document, logs and alerting, plus steps to rotate keys.
Inside it
- 01Field mapping between systems
- 02API and webhook connections
- 03Retries and duplicate protection
- 04Transfer logs
- 05Failure alerts and key rotation steps
Typical first engagement
The usual order of a first piece of work. Timing and price are set at scoping, once we have seen the stack.
- 01Data flow mapYou get: Which systems exchange which records, how often and who owns each side.
- 02First integrationYou get: One flow built with validation, retries and logging.
- 03AlertsYou get: A notice to a named person when the flow stops or rejects records.
Web and product engineering
Next in this line
Ask about this part of the stack
Write one question about integrations in your own systems. We answer it in writing and name what we would need to see to answer it properly.
A written reply, no call needed.