Flows
Flows define are how actors interact with your product.
Overview
Flows are how you control the actions simulating actors perform. Flows are graphs made of up nodes connected by noodles (aka graph edges).
The purpose of flows are to define different types of activitiyes actors are able to perform on your product, and what interactions are required in order to perform those actions. Rather than controlling your frontend directly, actors interact with your product through API calls to your backend.
It’s helpful to think of flows as a mixture of a user behaviors and programming control. Start by thinking of different types of user flows (like “creators” and “consumers” of a social app, or “drivers” and “riders” in a taxi app) and break them down into conceptual branches on the flow using control nodes like split and if/else. As you expand each of the branches, introduce interactions the with your product using API nodes in the same way your frontend interacts with your backend.
Execution
All flows begin execution at the entry node and pass control to the node attached to its output handle. As control passes from one node to the next, the return value of the first node is passed to the next node in the input variable.
Some nodes pass the input through unchanged while others manipulate or overwrite the value. Refer to the documentation for each node type to learn how they each work.
Publishing changes
Flows are compiled and published whenever you hit save, which will update the version of the flow assigned actors will execute. Publishing a new version usually takes about 15 seconds. You can leave the page while it rebuilds, but you must wait for the build to finish before running a manual test run.
Flows are not collaborative at the moment but we’re actively working on improving this. Note that if multiple users are editing the same flow concurrently, whoever saves last will overwrite with their version.
Testing
Flows can be manually tested by hitting the Run button to immediately force an actor to execute a single run of the flow. Head to the run page and open the ongoing run to observe the activity.
Outbound traffic
All outbound traffic generated by flows routes through either of the following IP addresses.
3.13.118.663.15.118.162These IP addresses are also listed on the Resources section of the team settings.