Action nodes are nodes that will perform an operation on or with the data that was passed to it.
The channel filter action node will filter channels based on criteria you provide. It's a general good practice to give these nodes a meaningful name by double clicking on "Channel Filter" once you dragged them onto the workflow canvas. If you have a time trigger then all channels will exit that time trigger, if you link this time trigger node with the channel filter node then you can filter out channels. Only the channels that are not filtered out will continue further down to the next node. You can just chain as many of these filter nodes in sequence so no need to create very complex filters into 1.
With the channel policy node you can modify the channel policy data. If you only want to modify Maximum HTLC then leave the other values empty (so do not set them to zero). These policy changes will apply to all channels that were coming into this node. So when you link a time trigger with the channel policy node directly you will be modifying ALL your channels. So use a channel filter if you only want to update a subset of channels.
This rebalance node has a lot of hidden complexities. We have a separate article for that one. Know that it uses a set of channels as source and a different set for destinations. The option to specify the amount and costs are also required.
At ln.capital we believe that tagging is an essential part of node running. It's for that reason that that is part of our first iteration of our automations. This node will add a tag on the list of channels that come out of it's parent node. You can chose between tagging a channel or tagging the node of that channel.
This does the opposite from the add tag node. This node will remove a tag.