That's understandable. Hopefully a pipeline user will see this and offer their insight. As for your API question, the short answer is that APIs don't talk with other APIs. You would write a script that bridges the two. For example, you would have a script that makes a call to your SOAP endpoint, parses the XML response, and then uses the parsed XML response to create a new request to Quick Base. You can do this with any combination of APIs regardless of response type since it's the script that does the translating. Pipelines are effectively doing the same thing but abstracting the coding/hosting which is why they're comparatively more limited in what they can do. That's not to say they don't offer value; just that there are tradeoffs for either approach.
------------------------------
Nathan Hawe
------------------------------