When are Daemons' Actions triggered
While a script has always 1 action, it is not that strict with conditions, as you can pick from 0 to all of them for each script you create.
Remember: scripts will become executable only when all conditions are triggered at the same time! For example, if you want your script to run when you have a balance > 1 ETH AND the price of ETH > 3K USDT, you'll have to wait until both conditions are satisfied.


This is a staple condition and will be triggered anytime the amount in your wallet, of a token you specified, goes higher or below a set threshold.
This condition could be used to trigger DCAs or to create LPs anytime some funds are received. The sky is the limit here.


Another simple action, used to send tokens from your address to any other address. Just like that.


The Frequency condition is useful to set the "when" and the "how often" a script should be run. We've added some messages that will specify when the first 2 executions will be triggered (but it won't stop there!).


This condition allows you to specify a maximum number of times the script will be executed. After this threshold has been reached, the script will be marked as "broken" and our daemonic bots will get rid of it without you having to worry about a thing.

Health Factor

Money Markets will liquidate our positions if our health factor is too low. Daemons is here to help you to avoid this unlucky event, and the Health Factor Condition is your best friend to prevent it.
Checking for the health factor to go below a certain threshold is helpful to repay loans and not get liquidated, while checking for it being higher than a threshold is useful when we want to borrow more funds (you scoundrel!).


You won't find the Follow condition in the list of available conditions, as it is created automatically whenever you chain two scripts together.
This condition is quite powerful and allows you to go wild. It's analogous to the connecting part of LEGO pieces, as it let you create more complex scripts from the union of simpler ones.
In these examples, the script #2, #3 and #4 will be executable only when the previous has been executed. Same for the script #1: once it has been executed, it will wait until the last of the chain has been run before of enabling itself again.