I've been building a no-code tool for authoring and running API integration tests called 1Baton. I work with APIs on a daily basis, building and testing them. In the services I work on, a single API endpoint often represents only a small action in a larger process, so testing a complete flow usually means calling several endpoints in sequence. When I started testing these flows, I found myself spending too much time setting up and reusing the same multi-step processes across different tests. I wanted to define a flow once, reuse it as a building block, and avoid having to manually maintain the connections and data passed between requests. This is what led me to build 1Baton. The basic idea is to define HTTP requests once, compose them into reusable sequences, and then use those sequenc