Discourse Workflows

thanks for the report @andresfromsonar :+1:

hopefully this will make it clearer that the “ai agent” node requires using an enabled “agent/bot”

2 likes

Hi, me again :grinning_face:
Looking for a way to have a trigger that triggers when a new user registered and confirmed their account, possible?

Worst case, you can create a webhook that triggers a workflow:

1 like

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.

yes, in the “three dots” menu you’ll find the “unpublish” option

2 likes

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 :sweat_smile:

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.

2 likes

Hi
First, thank you for this feature, it’s actually very powerful. Second, I have a question about the rate limit.

Is it possible to change the ‘rate limit’ so it’s not only 10 executions in a minute? The issue with this limitation is that even if I decided to use the “wait” feature, it doesn’t work because the execution is already counted as an execution:

My current use case is to bulk grant badges when members are added to a group, and I use the API endpoint /user_badges.json because this one allows you to mention ‘reason’ (which is not the case in the bulk grant feature nor the workflow action).

However, this might not be the only use case. I’m working on subscribing members to the newsletter as soon as they sign up so if more than ten members join at the same minute, there might be an execution error.

Both use cases are helpful in automating things so that we won’t have to manually subscribe members or grant badges, and there might be quite a number of other similar bulk tasks that we would like to automate. However, the rate limit seems to be a blocker.

The problem with the rate limit is that when many users are imported into a group, the ‘user added to group’ triggers immediately and the execution limit is reached immediately. It would be nice if we can either change the limit or create a queue stack for each specific workflow and a timer for how long to wait before it executes the follow-up execution.

Please feel free to move this post into its own topic post. Thank you!