thanks for the report @andresfromsonar 
hopefully this will make it clearer that the “ai agent” node requires using an enabled “agent/bot”
2 Likes
Hi, me again 
Looking for a way to have a trigger that triggers when a new user registered and confirmed their account, possible?
there’s the user first logged in node which might be even better for you?
1 Like
Thanks, will look at that.
Hi, I resolved to use the “new user seen” node which seems to do the trick.
workflow-nodes-new user seen.json (1.6 KB)
2 Likes
Can you confirm that privileged tags are able to be added?
In our Ideas (feature request) category, we want to auto-tag all new topics with new—but it’s greyed out in the topic tag node.
I understand wanting to limit where the tag applies, but my upstream node for the topic I created is only triggering for Ideas categories. It’s odd that it’s trying to force this restriction but doesn’t have the ability to see where it’s being applied.
For reference, only select groups can apply this tag (I.e., admins and product management).
But even when I select that this action be performed by an admin (me), it’s still not letting me select new.
Side note, I would expect the system user to be able to apply this regardless.
thank you guys for this incredible polish to this plugin past few months. it has done wonders to our forum. managing has become a brzee
still tunning few of our workflows but will get a hang of it in next few months.
1 Like
Can you turn off a workflow (i.e., unpublish it)? I don’t want to delete it, but merely disable it for now.
Looking to add a Topic Admin Button trigger for my moderators and category moderators (who all have topic admin wrench icons on topics), but it seems it is literal admin only. Is there any plans to expand this in the future to all staff members? Maybe make it where groups can be selected to have this button that triggers the workflow?
1 Like
Others have asked for that (or something similar) before, but we aren’t sure it makes sense to do that. Or at least, if it does, we need to dig deeper into the request first.
Many of the functions that a workflow can execute require admin privileges, so granting a less privileged group access to workflows would effectively give them admin anyway.
If you want to dive deeper, please create a new topic in Feature tagged workflows to discuss.
2 Likes
I think it is some kind related to Queries. Some of them are strictly for admins but other can be moderators-scoped.
It would add specs, work and testing, for sure, but can improve the overall Workflows usage in many communities. We all already know it: more usage → more feedback → better solutions.
I am always open to test and share my experiences, if they can be helpful. I like the idea about empowering moderators and softening the admin requirements on those activities or tasks that can be properly delegated.
2 Likes
Could you use the post button trigger instead?
I have a similar need and was about to submit a feature request, but I feel this might suffice since it’s only visible to your groups. Don’t get me wrong, I would still advocate for Topic admin button at least including staff.
The only difference is the location (admin wrench vs under the post)
Would it be possible to add a category filter for the post button? Otherwise I’ll just hide it via CSS 
Amazing plugin.
One thing I’m struggling with: I can’t find a topic properties node that allows setting a topic to wiki (Either on create, or as a downstream node that wiki’s it).
Right now I’m using a hack of defaulting all topics in the category to wiki, but it would be nice if the workflow could handle this part.
1 Like