Discourse ships an n8n-style visual automation builder and gates it to Business and Enterprise plans
In September 2026, Discourse launched Workflows, a visual automation builder in the Zapier or n8n mold, bundled into the platform’s core. It replaces hand-rolled webhook chains, but only activates on Business and Enterprise plans — not the self-hosted open-source edition.
September 2026. Discourse, one of the most widely deployed self-hosted forum platforms, launched Workflows: a visual automation builder built into the product’s core. The language will feel familiar to anyone who has used Zapier or n8n — nodes you connect on a canvas. Why it matters: moderation and community management still run, on most instances, on brittle webhook chains maintained by a single admin. Discourse is finally offering a maintainable replacement — but with a condition that divides the community: it only activates on Business and Enterprise plans.
The timing is telling. Automation has become table stakes for community platforms, and Discourse is responding to years of admins patching the gap with Zapier, n8n, and home-grown scripts. Workflows is the acknowledgment that this patchwork was never sustainable.
Four node types, one canvas
Workflows rests on four families of blocks: triggers, conditions, actions, and utilities. A trigger starts the flow — a topic is created, a user joins a group, a schedule fires, a webhook arrives, or you launch it by hand. Conditions route the logic — yes or no, this branch or that one. Actions make things happen: post a reply, send a private message, grant a badge, call an external API, run an AI agent. Utilities manage the flow itself — delays, loops, variable assignments.
Data passes between nodes as JSON that you can inspect and reference. A node field accepts a fixed value or a dynamic expression drawing on the current item, an earlier node’s output, workflow variables, site settings, or execution context. The expression picker lets you insert those references without memorizing the syntax.
The net effect is that one tool can handle a three-node welcome flow and a ten-node moderation pipeline, without switching to a scripting language for the harder case.
What makes the automation maintainable
The canvas is the visible part, but Discourse emphasizes the surrounding infrastructure, and that is where the tool stands apart from a webhook bodge. Variables are defined once and referenced everywhere. Credentials store API keys encrypted at rest, so you never paste a secret into a node field again. Data tables are persistent internal tables that let a workflow accumulate knowledge instead of starting from zero on every run.
Execution logs record every run in full — which nodes ran, what data they received and produced, where it failed. Error workflows define what happens when another workflow fails, so a failure triggers a notification rather than going unnoticed. Version history saves every iteration, and Templates provide pre-annotated starting points. A workflow exports as JSON and can be shared.
The practical consequence is a lower bar for who can build automation. The expression picker means an admin who can write a sentence can assemble a flow, while the JSON output means an engineer can still reason about and version the result. That middle ground — visual on the surface, inspectable underneath — is what n8n got right and what hand-rolled webhooks never offered.
The internal usage says a lot
Discourse did not wait to use its own tool. On Meta, its official community, Workflows automates three weekly reports — moderation, site settings, and trust levels — compiled by a scheduled trigger and published directly into the staff category. The moderation report, the most detailed, gathers into one place the count of every action, who handled flags and who reported them, the flagged posts with their metadata, any warnings issued, and any notes added. The JSON for all three reports is shared so you can import them as-is.
That detail matters: it proves the tool holds up under a real workload, not just a demo. It is also a signal of where Discourse is heading — the value is shifting from publishing toward operations.
Sharing the JSON is more than a gesture of transparency. It materializes an implicit promise: a library of reusable workflows is forming, and it will grow on the paid-plan side. It is the same mechanism as Templates — the value of an automation tool comes less from the canvas than from the catalog of ready-to-import flows. By publishing its own, Discourse seeds that catalog and signals where it plans to concentrate investment.
What an admin automates first
The most immediate use cases are the ones that used to eat whole evenings of configuration. Welcoming a new user: on account creation, send a private welcome message, add them to the right group, and grant a first-post badge. Watching unanswered topics: a scheduled trigger finds topics that have had no reaction for 24 hours and notifies moderators. Managing spikes: when a topic passes a certain number of flags within an hour, a workflow alerts the team and applies a conditional action.
What used to be a chain of Zapier webhooks, cron scripts, and brittle API calls becomes a readable, versioned, replayable graph. For a mid-size community, that is the difference between automation the admin maintains and automation the whole team can audit. The fact that Discourse uses it on Meta for weekly reports suggests the tool is built to last, not to demo.
The open-core tension, once again
The announcement lands inside a sequence the self-hosted community is watching closely. In recent weeks, Stirling PDF removed its SSO paywall from the community edition, while Planka and Grist pulled SSO out of their community editions. Workflows leans toward the second logic: the builder is bundled into the core of Discourse (no separate plugin to install), but activation appears only on Business and Enterprise plans.
For anyone self-hosting the open-source edition, nothing breaks today: the Automations plugin remains available, and there is no rush to migrate what already works. But the writing is on the wall — the most strategic new feature is locked behind a subscription. This is exactly the question selfh.st poses every week: how far can an open-source project pay for its own roadmap by paywalling its most useful features, without losing the community that carried it?
The context makes Discourse’s decision all the more legible. Communities now compete with Slack, Discord, and enterprise forums that ship with native automation. To keep up, Discourse has to provide the equivalent — and like any vendor, it chooses to fund that feature on its paid plans. The question for the self-hoster is therefore not “is this a bad sign?” but “does the value of Workflows justify the subscription?”, knowing that the free alternative (n8n, self-hosted Zapier) remains fully possible, at the cost of an integration you maintain yourself.
Verdict
If you self-host Discourse on the open-source edition, nothing forces you to move: Automations keeps working, and Workflows is not offered to you anyway. The risk is not immediate breakage, it is trajectory — if visual automation becomes the platform’s standard, your instance will be left behind. If you are already on Business or Enterprise, Workflows is worth adopting now: it replaces webhook chains nobody wants to maintain with a tool that has logs, versions, and secret management. The question to ask is budgetary more than technical: is the subscription worth ending your automation debt — and how long can your instance afford to stay on the old plugin?