Integration approaches
Native, iPaaS, or a custom API.
Pick from the objects you must move, the volume, and the person who will still understand the connection in a year.
Native
Use it when the app already maps the objects you care about, including the fields you will actually filter on. Stop when a required field is missing and the vendor will not add it.
iPaaS
Zapier, Make, and Workato suit two or three systems and steps a person can read. Name an owner for every scenario. A scenario nobody owns is how a silent retry starts.
Custom API
Use code when the map, the volume, or the conflict rule is the work. Budget for rate limits, a log, and a person who can read that log.
| Question | Native | iPaaS | Custom API |
|---|---|---|---|
| Best when | The objects already match | A few systems, light logic | The map is the product |
| You maintain | Settings in the app | Scenarios a person can open | Code, retries, and the rate limit |
| Breaks when | A field the app ignores | A step nobody owns | A silent retry storm |