👂 Feedback needed: scripts in automations that shouldn't be scripts

[YvetteLans]

Awesome if automations can be improved

High prio for us

@interr0bangr

Formulas within automation filters! Would unlock so much more power and minimize many complex workarounds for things.

@interr0bangr

• There’s no way to do multiple/splitting paths (IF statements) in automations without a script.

@interr0bangr

There’s no way to do auto-links with any other condition besides EQUALS, which means we often need to rely on scripts to link related entities for CONTAINS/IS ONE OF scenarios.

@interr0bangr

“Union” function (essentially the existing “Join” function, only with references to entities instead of just a text field)

@interr0bangr

“ToNumber” function** (the opposite of the existing “ToText” function)

@interr0bangr

When using the “Link entity” action in automations, you can use a formula, but when you use the “Unlink entity” action, you cannot use formulas.

@interr0bangr

There is a “User Input” option for button automations, but not for rule automations.

@helloitse

Automatically set State or Select Fields

Automations: Support entity references like "[Step 1 linked item]" in markdown-template Actions

Unlike formulas, automation markdown-template Actions (e.g. “Append to Document”) do not currently support Rule-entity references like [Step 1 linked item].

@Matt_Blais

Transcluding fields from other entities (i.e., JOINs)

Awesome, but lower prio
Since we already found a solution. But would be great if we can simplify our (quite complex) workspace.

@sereganabokar

Sending notifications in Telegram.

Recurring tasks

@njyo

Would be nice if the whole thing can just be compiled with Markdown. Also, the formatting of dates and date ranges is still very unclear.

@njyo

Setting icon, states and emojis if formula:

@helloitse

Call a webhook/URL