Discourse

· #237 most-used

Your open-source community forum, run by AI agents

CommunicationSocialProductivitySupportDeveloper

Discourse is the open-source forum platform that powers thousands of developer communities, customer support hubs, and public discussion boards — built for long-form conversation at scale. Connect Discourse to Actionist and your agents can triage incoming topics, create and manage categories, provision new user accounts, update posts with resolution notes, and react to webhook events like a new post or a suspended user — all in plain language without an admin panel in sight. Whether you're running a SaaS customer community or an internal engineering knowledge base, the agent handles the repetitive moderation and publishing work so your team focuses on the conversations that matter.

Try Discourse with Actionist Visit Discourse

Average time saved

10 hours

per person · per month

≈ 1 workdays back

Eliminates manual work. Agents eliminate the daily manual work of routing new topics to the right category, onboarding new Discourse members one by one, and writing repetitive release announcement posts.

Schedule

What your Discourse agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs

7Agents at work

24/7Always on

Agents

Wed–Fri

Wed

Thu

Fri

10a

11a

12p

Multi-app workflows

Discourse × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows

9Apps spanned

~35 hrsSaved / week

6Personas served

For customer success

Featured4 apps

Support ticket lands on Discourse instantly

When a customer emails your support inbox, the agent reads the message, finds the closest matching Discourse category, and creates a structured topic in under 60 seconds — complete with product version, account tier, and a formatted reproduction checklist. The original sender gets a reply linking them to the live Discourse thread where your team is already engaged, cutting average first-response time from hours to minutes.

~17 hrs

Time saved for your team — every week, on autopilot

The flow

Trigger·When a new email arrives in the support inbox

Trigger

Step 1

Gmail

Detect new support email

read

Step 2

Discourse

Get all categories to find best match

write

Step 3

Discourse

Create a post in the matched support category

write

Step 4

Slack

Notify #support-team with topic link

write

Step 5

Google Calendar

Schedule 24-hour follow-up reminder

Result

Create a post in the matched support categoryNotify #support-team with topic linkSchedule 24-hour follow-up reminder

The win

Saved per run

25 min

Runs / week

~40×

Every support email becomes a searchable community thread

Driven byCustomer Support Agent

ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

Sales
18 min / week
Forum prospect triage
Sales rep manually scans Discourse threads to spot mentions of open deals or competitor comparisons, missing most signals.
Sales Agent
0 min
Agent surfaces buying intent
Agent monitors new Discourse posts for prospect usernames and deal-related keywords, dropping a quote and context into the rep's Slack before they open their laptop.
Marketing
13 min / week
Weekly community digest
A marketer reads through the past week's top Discourse threads and manually writes a community highlights post, taking 45–60 minutes every Monday.
Marketing Agent
0 min
Agent authors the digest
Agent fetches posts by likes, writes a ranked summary, and publishes the digest to Discourse and the content pipeline automatically.
Customer Support
18 min / week
Topic-to-ticket routing
Support reps scan Discourse for unrouted questions, manually copy details into the helpdesk, and post acknowledgement replies — 3–5 minutes per ticket.
Customer Support Agent
0 min
Agent routes instantly
Agent detects new support-tagged topics, creates the helpdesk ticket with full context, and posts a holding reply in under 60 seconds.
Human Resources
7 min / week
Internal forum onboarding
HR manually creates Discourse accounts for new hires, adds them to department groups, and posts a welcome message to the staff community.
Human Resources Agent
0 min
Agent handles day-one provisioning
Agent creates the Discourse account, adds the hire to the correct department group, and posts a personalised welcome the moment HR confirms the start date.
Finance
13 min / week
Access revocation on churn
Finance flags a lapsed subscription then manually alerts ops to remove the customer from premium Discourse groups, sometimes days after billing lapsed.
Finance Agent
0 min
Agent revokes access at billing boundary
Agent removes the user from gated Discourse groups within minutes of the subscription event, with an audit row logged automatically.
Operations
25 min / week
New member onboarding flow
Ops manually creates Discourse accounts, assigns groups, and sends welcome messages for each new community member — 10 minutes per person at scale.
Operations Agent
0 min
Agent runs the full onboarding
Agent creates the account, assigns the right group by plan tier, and posts a welcome thread end-to-end without a single manual step.
Legal
6 min / week
Moderation audit logging
Legal manually exports Discourse moderation actions into a spreadsheet for compliance review after each policy-violation incident.
Legal Agent
0 min
Agent logs every moderation event
Agent captures every topic destruction, user suspension, and post edit into the compliance sheet in real time, with no manual export required.

+ 100s of other Discourse automations

Average monthly

10 hrs / person / month

Average monthly

10 hrs / person / month

Calculator

Calculate what your team saves

Team size

10 people

Hourly rate

$20 / hr

Hours saved / week

Hours saved / year

1,250

Annual ROI

$25,000

Based on Discourse's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug Discourse into Actionist

Pick the connection method that suits your environment.

The fastest path: install Discourse's MCP server and the agent reaches your forum through a direct, permissioned channel — no API keys to rotate, no admin panel juggling.

Open the Apps tab

Find Discourse in the Apps library and click Connect. MCP is selected by default as the recommended method.

Enter your Discourse instance URL

Provide the base URL of your Discourse forum (e.g. https://community.yourcompany.com) so the MCP server knows which instance to talk to.

Authorise with an API key

In your Discourse admin panel, navigate to Admin → API Keys and generate a system-user API key. Paste it into the Actionist connection dialog.

Test the connection

Actionist runs a read-only call to confirm the MCP server can reach your forum. A green tick means you're ready.

Actions

16 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

7 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with Discourse

Reusable agent skills that work well alongside this app.

Faster Whisper

Transcribes Discourse voice messages or recorded community calls to text locally using faster-whisper, enabling the agent to search and summarise spoken content.

Graphic Design

Generates on-brand cover images for Discourse category headers and announcement posts when a new release or event category is created.

X(Twitter) Post Automation

Cross-posts top Discourse community threads and announcements to X automatically, amplifying community content to a wider audience without manual copying.

MCP servers

MCP servers that work with Discourse

Connect Actionist to MCP servers built for or around this app.

discourse/discourse-mcp

Official Discourse MCP server for forum integration — search topics, read posts, manage categories and tags, and interact with community members via structured tool calls.

mcp

Official

Discourse MCP CLI server exposing the Discourse REST API as typed MCP tools over stdio for direct agent integration.

FAQs

Questions about Discourse + Actionist

How do I connect my Discourse forum to Actionist?

Open the Apps tab, find Discourse, and click Connect. You'll need the base URL of your forum (e.g. https://community.yourcompany.com) and an API key generated from Admin → API → API Keys. Create a dedicated system-user key — not a personal account key — so you can scope permissions cleanly and revoke without disruption.

What API key permissions does the agent need?

For full read and write access across categories, groups, posts, and users, create a Global API key scoped to a dedicated system user account. If you prefer least-privilege, Discourse lets you scope keys to specific endpoint groups — create separate keys for read-only reporting agents and write-capable action agents and use the right one per workflow.

Can the agent combine Discourse with my CRM or helpdesk?

Yes — that's exactly where Discourse automation pays off. A typical pattern: new Discourse post triggers a Zendesk ticket, agent posts an acknowledgement reply in the forum thread, and logs the conversation link on the HubSpot contact record. The agent coordinates all three systems in one workflow; you define the routing logic in plain language.

What are the most common Discourse automation patterns?

The four highest-leverage patterns are: (1) routing new topics to the right category and notifying the right team; (2) provisioning Discourse accounts and group memberships when users sign up or upgrade; (3) publishing release notes and weekly digests automatically; and (4) reacting to webhook events — suspended user, post edited, topic recovered — to keep downstream records in sync.

Does the pricing model affect how I run Discourse workflows?

Actionist is not — there's no per-operation charge. You connect Discourse directly via the MCP server or API key and the agent executes as many reads and writes as your workflow needs. High-volume patterns like nightly user audits or per-post digest builders run without incremental cost per Discourse API call.

How do I avoid trigger loops when the agent posts to Discourse?

Two safeguards: first, use a dedicated system-user API key for agent-created posts — most Discourse webhook consumers let you filter by author so events from the system account don't re-fire the trigger. Second, add a condition step that checks whether the topic or post was created by the system user before the agent acts, short-circuiting the loop at the workflow level.

Which Discourse objects can the agent read and write?

The agent covers four resource types: Categories (create, list, update), Groups (create, read, list, update, add member, remove member), Posts (create, read, list, update), and Users (create, read, list). For actions beyond these — such as tagging, badges, or bulk moderation — use a direct API call via the HTTP action with the same credentials.

What happens if I disconnect Discourse from Actionist?

Active trigger listeners are removed immediately and no new events are processed. Workflows that include Discourse actions will fail at the Discourse step and surface an error — no silent data loss. Reconnecting restores functionality; any events that fired during the disconnection window are not replayed, so time-sensitive triggers may miss events that occurred in the gap.