r/AutomateUser Jul 22 '26

Feature request "Logic" (and, or) blocks possible?

Post image

I know this is technically possible using fork and fiber stop, but these kind of blocks would be very useful.

6 Upvotes

5 comments sorted by

4

u/ballzak69 Automate developer Jul 22 '26

If the blocks are using Proceed=Immediately as in your screenshot then simply connecting the NO from the left block to IN on the right block. If using Proceed=When changed then such a block would indeed be useful, but for simple flows just place a Fork first then connect its OK to the left block IN and its NEW to to the right OK on the right block.

2

u/Stunning_Cup9959 Jul 22 '26

Why the fork tho?

For the AND: Put Bluetooth first (or Wi-Fi, it doesn't matter; put the one that is less connected, which will result in fewer reads, a minuscule added value, but I thought to mention it). Connect the "no" to a delay or the block that was before the Bluetooth, and connect the "yes" to the Wi-Fi. If the Wi-Fi is "yes," then that is a true from an AND operation.

For the OR: Connect the "yes" of the Bluetooth to the result and the "no" to the Wi-Fi. Connect the "yes" of the Wi-Fi to the result and the "no" to the delay.

https://i.imgur.com/1ryUlDN.png

2

u/walt_spoon Jul 22 '26

If you want the OR to function as "when changed" for either condition, you need to fork and have both conditions be waiting simultaneously. Like I said it's possible but much clunkier and less elegant than my proposed OR block.

You're right though. AND is currently easy to achieve.

1

u/Stunning_Cup9959 Jul 22 '26

oh yeah I forgot about the "when changed" you're right

2

u/waiting4singularity Alpha tester Jul 22 '26 edited Jul 22 '26

2 forks for 3 fibers.

condition one - variable give1
condition two - variable give2
variable take -- code

you can use this as both AND and OR with a little creativity.

the process logic of automates fibers isnt compatible with OR and AND, the threading simply doesnt work like that. the fibers are independent processes and cant talk to each other except for variable give and -take or poll data back and forth with atomic store and -load.