Each integration adds authentication, data shape, rate limits, version drift, and a new failure boundary. Limiting the first setup to three standard integrations keeps the acceptance test understandable and the rollback practical. Choose the source that starts the job, the tool that performs the essential action, and the destination that makes the result useful. Additional systems should wait until real runs show a repeated need. This boundary keeps the price predictable and avoids unnecessary custom code.