새로운 워크플로 기능 미리보기

We’re building a new Workflows feature that is designed to support complex tasks that our existing Automations tool can’t handle. This new visual automation builder lets you create multi-step workflows with time delays, conditional branches, calls to external services, and AI actions directly in your admin area.

:warning: Important notes!

  • Workflows is available on the Business and Enterprise plans, for users on Discourse hosting.
  • For now, this is considered an experimental change! We’re still working on refining and improving this feature, so there may be some rough edges and small tweaks in the coming weeks.

An overview of Workflows

Workflows replaces the scripting-heavy approach of the existing Automations plugin with a node-based visual canvas that you connect to create complex, multi-step logic.

:books: Documentation

Nodes

There are four broad categories of nodes:

  • Triggers initiate a workflow in response to things like events in Discourse (e.g., topic created, user added to group, etc.), a set schedule, a webhook, or a manual action.
  • Conditions create branches in the workflow based on yes/no logic for any data in the workflow.
  • Actions are events triggered by the workflow, such as sending a PM or chat message, posting a reply, calling an HTTP endpoint, running an AI agent, or querying Data Explorer.
  • Utilities control the flow itself by setting delays, looping over items, and setting variables, and can help document the workflow with sticky notes.

Each node’s parameters support literal values and dynamic expressions, so you can reference the output of any previous node, workflow variables, or execution context from an earlier step in a later step.

Variables, data tables, and credentials

Workflows includes a few additional tools for easier creation and management of their output:

  • Variables are stored key/value pairs (e.g., group IDs, category IDs, etc.) that are readily available across all workflows for easier configuration.
  • Credentials are where you can store reusable authentication configuration for HTTP request nodes, so you don’t need to paste API keys into your workflows.
  • Data tables are used for storing and querying runtime data, so you can track executions (e.g., see whether a workflow has already run on a specific topic) and reference the output of a workflow easily.

Execution logs

Every workflow run produces a full log in the Executions tab. You can see which nodes ran, what data they received, what they output, and where a workflow stopped if something went wrong.

Previewing Workflows

For now, this is considered an experimental change! We’re welcoming your feedback, which will help us make improvements and roll this out further.

To try it out, go to Upcoming changes at /admin/config/upcoming-changes, find the Enable Discourse workflows item, and update the Enabled for… field to opt your site in.

Once enabled, you’ll find Workflows under Plugins → Workflows in your admin area.

29개의 좋아요

This looks like n8n. Would be very cool if it functions similarly

3개의 좋아요

Could this function as an alternative to Automations? Or perhaps combined?

1개의 좋아요

We have been building some integrations and automations using this new plugin in the past 4 weeks and all I can say is that it is absolutely fantastic, and a game changer for Discourse. This is truly the best new feature in years (and there are already quite some amazing features :heart_eyes:).

It does :slight_smile:

13개의 좋아요

It will likely replace the Automations plugin entirely at some point, as Workflows are much more flexible

9개의 좋아요

this is a wild concept. i have spent a lot of time making powerful n8n and discourse integrations. incredible initiative this will super charge discourse.

8개의 좋아요

I’m experimenting with this now and I think there should be a new category in this forum for workflows.

I also would like to know how to send a chat message to a user instead of a channel

3개의 좋아요

It’s not possible to send a chat message to a user yet, just channels

Mike Tyson's 'Real Thoon' Meme

6개의 좋아요

I love the new workflows - it’s a total game change, and can be coupled with services like n8n too.

I have found that the rate limit is hit often- how can this be changed?
Also, not sure why, but I have found that at times it’s just stops running, and the only way to get it to run again is to turn the feature off, and back on via the ‘upcoming changes’.

Thoughts?

2개의 좋아요

It feels quite sophisticated. Could someone please list some use cases?。。。。。

1개의 좋아요

Imagine being able to make a flow that based on users trust level you can make dynamic behaviors like if a user is a member of these 2 groups simultaneously, add them to this third group that gives them access to a new category.

Dynamic behaviors like that are difficult to do with vanilla discourse

4개의 좋아요

A better approach is to refactor all group selectors into intersection-union-complement expressions! :smile: (just joking)

You can do anything by calling the Discourse API from within a workflow :grinning_face:

2개의 좋아요

I’d like to know in what situations one should continue using Automations + queries, and when one should actually use Workflows. Taking the following action as an example:

Send private messages to users whose read to post ratio is passing 250:1 (and who would eventually fall into the “delisted” group, also known as ‘lurkers’)

Which tool is more efficient and/or recommended for that particular case? When should I use Automations + queries, and when should I use Workflows?

I understand that Workflows allow for branching decisions and thus enable dynamic diagrams; to start with, I’d like to know what experienced users think about simpler ones.

I recommend using Workflows even for simple processes, for a few reasons:

  • If you ever decide that the simple process needs to grow or change, Workflows is much more flexible and can adjust to your needs
  • If you ever decide that you want to build another process that is influenced by this process, Workflows lets you connect them together
  • Workflows gives you better visibility into the executions of the process, so troubleshooting is easier
7개의 좋아요

What @lindsey said, and also if you have any use case you could do in automation and can’t do in workflows, let us know please

6개의 좋아요

워크플로 공유를 위한 전용 섹션이 있으면 정말 좋을 것 같아요! 이렇게 하면 커뮤니티를 도울 수 있고, 다양한 메커니즘을 더 잘 이해할 수 있으며, 특히 향후 프로젝트에 대한 새로운 아이디어를 얻을 수 있습니다. 그저 아이디어일 뿐이에요 :sweat_smile:

참고로: 워크플로 모듈이 매우 잘 만들어졌고, 강력하며 직관적이라고 생각합니다. :+1:

3개의 좋아요

아래 링크에서 의견을 나눠 주세요:

3개의 좋아요