Automated Discourse Member Approval Queue
Every morning, WebRun opens your Discourse forum, lists the users waiting for approval and the members who joined in the last day, drafts a welcome message for each one, posts the approval queue to Microsoft Teams, and texts the moderator on call through Twilio when anyone has waited too long.
How do I clear the Discourse approval queue every morning?
WebRun reads your Discourse sign up queue every morning, listing users awaiting approval with how long each has waited and drafting a welcome message for yesterday's new members. It posts the queue to Microsoft Teams and texts the on-call moderator through Twilio, so nobody waits a week to post.
- New members are approved the day they sign up, not the week after
- Every new member gets a welcome written in your community's voice
- Moderators see the longest wait first, every morning
Built for community managers · forum moderators · developer relations · membership organisations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
discourse.orgin a real browser with your saved login - no setup, no API keys. -
1
Discourse - read the sign up queue
WebRun opens Discourse to read the sign up queue. - Open Discourse and read the list of users awaiting approval
- Capture each pending user: the name, the sign up date, and how many days they have waited
- List the members who joined since yesterday and note their trust level and any group they landed in
- Draft a short welcome message for each new member in your community's voice, and leave it unsent
- Leave every pending account exactly as it is. WebRun never approves or rejects a sign up itself
Done when Every pending sign up is listed with its waiting time and a welcome message is drafted for each new member.
-
2
Microsoft Teams - post the queue to moderators
WebRun opens Microsoft Teams to post the queue to moderators. - Post the approval queue to your community channel in Microsoft Teams
- Put the longest waiting sign ups first, with the days each has waited
- List who joined yesterday underneath, with the drafted welcome ready to copy
- Leave the approvals for a moderator to make in Discourse
Done when The community channel has this morning's queue and the drafted welcomes.
-
3
Twilio - text the moderator on call
WebRun opens Twilio to text the moderator on call. - Send a short internal text to the moderator on call, at the number you configured, when a sign up has waited past your threshold
- Keep the text to the count and the longest wait, with no member details beyond a first name
- Send nothing on a morning where the queue is clear
- Never text a forum member. Twilio is used only to reach your own moderators
Done when The moderator on call has been texted about anything waiting past the threshold.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it approve sign ups on its own?
No. WebRun reads the queue and reports it. Approving or rejecting an account stays with a moderator in Discourse, so a real person decides who joins your community.
Does it post the welcome messages?
No. Each welcome is drafted and left unsent for a moderator to read, edit, and post. Nothing appears publicly on your forum unless a human sends it.
Will it text new members?
No. The Twilio text goes only to the moderator number you configure, and only when the queue has aged past your threshold. Members are never texted.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.