Skip to main content
Logic nodes decide whether and where execution continues. Put all required eligibility checks before launch or trading actions.

​
Branch On Conditions

Use If Exists after operations that may not return a value, such as selecting an array item or casting text. Use Switch when one value selects among three or more distinct paths.

​
Compare And Combine Values

For exact author matching, compare the broken event’s normalized handle with the expected handle. Do not use a substring check when similar handles must be rejected.

​
Build A Complete Eligibility Gate

When a launch requires both a specific author and a valid address:
  1. Connect Author Handle from the matching event break node to the left side of Compare.
  2. Set Compare to == and provide the exact expected handle on the right side.
  3. Connect the tweet’s Body Text to Extract Solana Pubkeys.
  4. Connect the comparison Result and extractor Matched? outputs to And.
  5. Use the And > Result value for If Condition or return it as the eligibility output of a pure function.
  6. Keep the launch execution path behind that combined result and unwrap the selected address with If Exists before required address inputs.
Every distinguishing test field must reach the final gate. A function input that is never connected does not enforce a rule, even when the function’s other checks pass.

​
Repeat Work

Loop exposes a repeated path and an exit path. Use Continue to start the next iteration and Break to leave the nearest active loop. Prefer array selection or a focused function when the workflow only needs one item. Use a loop when every item genuinely needs work, and include a clear exit condition.
A loop containing launch, trade, AI, or trace-notification effects can multiply cost and side effects. Test empty, one-item, and maximum-size inputs, and enforce limits before activation.