Deploying Rapidflare
Integrating Rapidflare AI Agent with your Discourse forum
This guide will help you connect Rapidflare to your Discourse community forum, so new topics get an answer automatically. This is an admin flow.
Prerequisites
- Discourse administrator access to your forum
- Access to the Rapidflare Admin Dashboard
- A Discourse account for the agent to post as (see Step 1)
How it works
When someone opens a topic in a category you have chosen, Discourse notifies Rapidflare, the agent answers from your knowledge base, and the reply is posted in that topic. Readers continue the conversation by mentioning the agent, and it remembers the earlier turns in that topic.
Unlike Slack and Discord, there is no app to install. You create an account for the agent on your own forum, issue it an API key, and paste a webhook address into your Discourse settings.
Step 1: Create the agent's account
The agent posts as a normal Discourse user, so it needs an account.
- In your forum, go to Admin → Users and invite a new user (for example,
acme-assistant). - Choose a name your community will recognize as the assistant. This name is what people will type to call it.
- Open the new account in Admin → Users and set Trust Level to 4 (Leader).
Set trust level 4
New accounts start at trust level 0, which limits how often they can post and how many links they can include. An agent that answers regularly will be rate-limited or flagged as spam without trust level 4.
Step 2: Create an API key
- Go to Admin → Advanced → API keys and click New API Key.
- Description — something that names the integration, so a future admin knows what the key is for.
- User level — change this from All users to Single User, then choose the account from Step 1.
- Scope — Global works. If you prefer a narrower key, use Granular and allow creating and deleting posts.
- Save, then copy the key. Discourse shows it only once.
Change the user level
User level defaults to All users, which lets the key act as anyone on your forum, including staff. The agent only ever needs to post as itself, so set this to Single User.
Step 3: Connect from the Rapidflare dashboard
- In the Rapidflare Admin Dashboard, open your hub and go to Deployments.
- Click the Discourse row.
- Fill in:
- Forum URL — for example
https://forum.example.com - Bot username — the account from Step 1
- API key — the key from Step 2
- Forum URL — for example
- Click Connect.
Rapidflare checks the key against your forum and then shows you two values: a Payload URL and a Secret. Copy both — the secret is shown only once.
Step 4: Register the webhook in Discourse
- Back in your forum, go to Admin → Webhooks and click Add webhook.
- Payload URL — paste the URL from Step 3.
- Content Type — leave it as
application/json. - Secret — paste the secret from Step 3.
- Under Which events should trigger this webhook?, choose Select individual events and tick Post is created under Post Events. Leave Send me everything alone — Rapidflare ignores every event except a created post.
- Under Triggered Categories, add every category the agent should answer in.
- Tick Active, then click Create.
Triggered Categories is what scopes the agent
This is the only place scope is set. Name categories and the agent answers in those alone; leave it blank and the forum sends every category, so the agent would answer in announcements and staff areas too.
Tick Active, or nothing is sent
Active sits at the bottom of a long form and is easy to scroll past. A webhook saved without it is created but never fires, and the delivery log stays empty — so there is nothing to tell you it is off.
Step 5: Try it
Post a new topic in one of your chosen categories, using an account other than the agent's. The agent posts once, when its answer is ready, so expect nothing in the topic until the reply itself appears.
To continue the conversation, reply to the topic and mention the agent by name:
@acme-assistant does this apply to version 6 as well?
Where the agent answers
Scope lives on the webhook, in Triggered Categories, and nowhere else. Rapidflare answers wherever your forum delivers a post, so changing which categories the agent covers means editing the webhook — there is no second list to keep in step.
The mention rule is separate and always applies: only the opening post of a topic is answered unprompted, and later posts have to mention the agent.
How the agent decides to answer
| Situation | What happens |
|---|---|
| New topic in a category the webhook covers | Answered automatically |
| New topic in any other category | Never reaches Rapidflare |
| Reply that mentions the agent | Answered, continuing the topic's conversation |
| Reply that does not mention the agent | Ignored, so the agent stays out of discussions between people |
| The agent's own posts | Ignored |
Changing your settings
Open the Discourse row in Deployments again to change the forum URL or the bot account. To change which categories the agent covers, edit Triggered Categories on the webhook instead.
Re-enter the API key to save changes
Rapidflare never displays a stored API key, so changing any setting means entering the key again. Your webhook secret is reused, so the webhook you registered in Step 4 keeps working.
Disconnecting
Click the Discourse row and confirm Disable. Rapidflare stops answering immediately and erases the stored credentials. You can then delete the webhook and revoke the API key in your forum.
Troubleshooting
The agent does not reply to a new topic. Work down the path the post takes:
- Is the webhook Active? An inactive webhook has an empty delivery log — check Admin → Webhooks.
- Did the forum send it? Open the webhook and look at its delivery log. Nothing listed means Triggered Categories excludes that category — add it there.
- Did Rapidflare accept it? A delivery showing
200was received. Anything else is covered below. - Who posted it? The agent never answers its own posts.
Replies are ignored. Only replies that mention the agent are answered. Check the spelling of the username — @acme-assistant2 is a different account, not a mention of @acme-assistant.
Replies appear but get flagged or hidden. The agent's account is probably below trust level 4. Raise it in Admin → Users.
The agent stopped mid-conversation. If a moderator moved the topic to a category that is not on your list, the agent stops answering there. Move it back, or add that category.
Discourse shows webhook errors. Open Admin → Webhooks, select the webhook, and read the delivery log. Redeliver replays a failed event once you have fixed the cause, so you can confirm without posting again.
| Status | Meaning |
|---|---|
200 | Received. If the agent still said nothing, the response body gives the reason — not_mentioned or duplicate. |
401 | The secret does not match. Reconnect from the dashboard for a fresh pair and update it here. |
404 | The payload URL is wrong, or the Discourse deployment was disabled in Rapidflare. |