To follow up on Daniel's answer, here's a demo video showing how powerful link-parsing + link connections are https://www.youtube.com/watch?v=fEo6jsPD524 https:

To follow up on Daniel's answer, here's a demo video showing how powerful link-parsing + link connections are https://www.youtube.com/watch?v=fEo6jsPD524 https://www.youtube.com/watch?v=fEo6jsPD524 Hopefully it's also a bit of an answer to #2, showing how easy it is to explore and iterate an API, even without a library, so that should help speed up the initial one-time effort, and then we handle things like rate-limiting, inter-service dependency, and per-service optimization (like automatically switching between Salesforce's REST api and their Batch API, both of which have radically different implementations that would require an entire re-arch if you build on them directly).