Feature Request - Split Automations into Triggers and Actions

Feature
1

Hey!

I often find myself wanting to use Automation, but feeling limited by how they currently work. I often find one script has something I need, while I need that part to work within the context of another script.

It seems this is largely related to the way Automations currently work and are set up. I’d love to see things split into Triggers and Actions.

  • Example triggers:
    • When a topic is created/updated
    • When a post is created/updated
    • When a site setting changes
    • When a topic is closed
    • When a user earns a badge
    • etc.
  • Example actions:
    • Make a banner topic
    • Close a topic
    • Reply to a topic
    • Create a topic
    • Tag a topic
    • Run LLM call
    • Send a Slack message
    • etc.

This setup would allow for a few things:

  • Multiple actions to be assigned following a trigger (e.g. When topic is created> Run LLM Call> Tag post> Reply to the topic)
  • Allow for trigger payload data (and subsequent data made available from actions - e.g. LLM call response) to be used dynamically within actions

Ultimately, I feel Automation has a lot of potential, but each Script is siloed in a way that makes it very hard to customize to individual needs. Each currently assumes that the actions available will work for everyone.

1 Like