yeah, sure, but now you are adding cost to the transactions (especially with the inefficiency of MCP!)
I hear you on the cost, but I think it has to be weighed against the “human cost” of current manual gardening and the potential frustration of context-blind nudges. Traditional workflows often result in “notification fatigue” when nudging users who haven’t found a solution yet.
MCP does have some overhead now - but AI efficiency is only getting better over time, and using it to provide meaningful, accurate indicators of solutions is likely more scalable than asking staff to manually triage every aging topic.
We already have support for extremely sophisticated agents in discourse ai
I wonder how we can expose it so sophisticated workflows like this are easy to configure ![]()
Would love to have a chat
Would be happy to chat! I know this topic is slightly of track from the original post. But to answer the question about the ease of setting up workflows like this - it largely comes down to the way automations work in Discourse - rather than allowing admins to setup the steps, the out of the box options heavily rely on pre-defined flows. Splitting into triggers and actions, and allowing admins to configure things as they need for their community would help greatly. Here’s a feature request I started for it - Feature Request - Split Automations into Triggers and Actions