Formwell docs: commands, permissions and FAQ

Formwell is a Discord bot for application forms: staff and moderator applications, whitelist requests, ban appeals and signups. Members click Apply, answer in a Discord pop-up, and the answers land in your review channel with Accept and Deny. This page lists every command and option the bot has today, generated from the bot's own command definitions.

Add Formwell to your server

Quick start (3 commands)

/form create name:staff review_channel:#applications accept_role:@Staff
/form add-question form:staff label:Why do you want to join?
/form publish form:staff channel:#apply

Or start with ready questions: /form create name:staff review_channel:#applications template:Staff / moderator application, then change any question with /form edit-question. In Discord, /formwell shows the same steps.

Commands

All /form commands need the Manage Server permission by default (server owners can change who sees them in Server Settings > Integrations > Formwell). Commands work inside servers only, not in DMs. The form option autocompletes your form names. /application status is for every member: it shows only their own applications.

/form create

Create a new form.

• name (text, required, max 32 characters): Short name, e.g. staff (letters, numbers, dashes).
• review_channel (channel, required): Where submissions are posted for review.
• title (text, max 45 characters): Title shown to applicants (default: the name).
• accept_role (role): Role given when an application is accepted.
• reviewer_role (role): Role allowed to accept/deny (Manage Server always can).
• template (text): Start with ready questions (edit them later). Choices: Staff / moderator application, Moderator scenario questions, Helper / support team, Event or content team, Minecraft SMP whitelist, FiveM / GTA RP whitelist, Hytale server whitelist, Clan / guild recruitment, Ban appeal.

/form add-question

Add a question to a form.

• form (text, required): Form name.
• label (text, required, max 45 characters): The question (max 45 characters).
• style (text): Answer type (default: short text). Choices: Short (one line), Paragraph, Dropdown (pick one from a list) (live test pending), Multiple choice (pick one) (live test pending), Checkboxes (pick any) (live test pending), File upload (screenshots, proof) (live test pending).
• options (text, max 3000 characters): Choices separated by |, e.g. Java | Bedrock | Both (dropdown up to 25, others 10).
• required (true/false): Must be answered (default yes).
• placeholder (text, max 100 characters): Hint text inside the box (or under the question for choices).
• max_length (number, 1-4000): Maximum answer length (text questions).
• max_files (number, 1-3): File upload: how many files a member can attach (1-3, default 1).

/form edit-question

Change a question by its number.

• form (text, required): Form name.
• number (number, required, 1-25): Question number from /form view.
• label (text, max 45 characters): New question text (max 45 characters).
• style (text): New answer type. Choices: Short (one line), Paragraph, Dropdown (pick one from a list) (live test pending), Multiple choice (pick one) (live test pending), Checkboxes (pick any) (live test pending), File upload (screenshots, proof) (live test pending).
• options (text, max 3000 characters): Choices separated by |, e.g. Java | Bedrock | Both (dropdown up to 25, others 10).
• required (true/false): Must be answered.
• placeholder (text, max 100 characters): New hint text.
• max_files (number, 1-3): File upload: how many files a member can attach (1-3, default 1).

/form remove-question

Remove a question by its number.

• form (text, required): Form name.
• number (number, required, 1-25): Question number from /form view.

/form edit

Change a form.

• form (text, required): Form name.
• title (text, max 45 characters): Title shown to applicants.
• description (text, max 2000 characters): Text on the published panel.
• button_label (text, max 80 characters): Text on the Apply button.
• review_channel (channel): Where submissions are posted.
• accept_role (role): Role given on accept.
• reviewer_role (role): Role allowed to review.
• clear_accept_role (true/false): Stop giving a role on accept.

/form settings

Pro: application rules and messages.

• form (text, required): Form name.
• one_per_user (true/false): Only one open or accepted application per member.
• cooldown_hours (number, 0-8760): Hours before a member can apply again (0 = off).
• required_role (role): Members need this role to apply.
• clear_required_role (true/false): Anyone can apply.
• accept_message (text, max 1500 characters): DM sent on accept.
• deny_message (text, max 1500 characters): DM sent on deny.

/form view

Show a form and its questions.

• form (text, required): Form name.

/form publish

Post the Apply button in a channel.

• form (text, required): Form name.
• channel (channel, required): Channel for the panel.

/form list

List this server's forms with pending / accepted / denied counts.

/form pending

List applications still waiting for review.

• form (text): Only this form (default: all forms).

/form nudges

Daily reminder in the review channel when applications wait over 24 h.

• state (text, required): on or off. Choices: on, off.

/form delete

Delete a form and its submissions.

• form (text, required): Form name.
• confirm (true/false, required): Set true to confirm.

/form export

Pro: download submissions as CSV.

• form (text, required): Form name.

/application status

See your applications here: pending, accepted or denied (only you see the answer).

/premium

Formwell Pro status and upgrade.

/formwell

How to use Formwell.

/vote

Vote for Formwell on bot lists. It is registered only once Formwell has a bot-list page, so you may not see it yet.

Question styles

Choice options go in options: separated by |, for example options:Java | Bedrock | Both. Every question label is at most 45 characters: that is Discord's limit for pop-up labels. Put longer instructions in placeholder:. "Live test pending" means the style passes our automated tests but has not yet been tried by a person in a real server; we will update this page after that test.

Free vs Pro

Pro adds:

• Multi-page forms (more than 5 questions)
• One application per member and cooldowns
• Required role to apply
• Custom accept and deny messages
• CSV export of submissions
• Interview threads ("Ask" button)

Run /premium in your server to see its status and upgrade (checkout by Polar, our merchant of record). If Pro ends, nothing is deleted: the 3 oldest forms with up to 5 questions stay open, the rest pause until Pro is back.

Permissions Formwell asks for

The invite link asks for these and nothing else (permissions value 343865936896, no Administrator):

The review channel and the panel channel must let Formwell's role view and send messages there. To give a role on Accept, Formwell's own role must sit above that role in Server Settings > Roles.

What applicants and reviewers see

1. The member clicks Apply on the panel you published. Pro rules are checked first (required role, one application per member, cooldown).
2. A Discord pop-up opens with up to 5 questions. Longer Pro forms show a Continue button between pages; answers between pages are kept for 30 minutes.
3. The submission is posted in the review channel with Accept and Deny (Deny can take a reason). Members with Manage Server or the form's reviewer role can decide; the first decision wins.
4. Accept gives the accept role and DMs the member; Deny DMs the member, with the reason if one was given. Pro can change both messages and open a private interview thread with Ask.

Right after Submit, the member sees (only they can see it) "Received (#12). 2 applications are ahead of you." That number counts the older applications to the same form that are still waiting for review. Any time later, /application status lists the member's own applications in that server: the form, when they sent it, and whether it is pending (with its place in the queue), accepted or denied, plus the deny reason when the reviewer gave one (the same reason the DM carried). Reviewers don't need to do anything for this.

FAQ and troubleshooting

The commands don't show up

Type /form in a server channel (not a DM). The /form commands are hidden from members without Manage Server unless you changed that under Server Settings > Integrations > Formwell. If Formwell has no commands at all, re-add it with the invite link above: it must be added with the "applications.commands" scope.

The bot is not responding / "The application did not respond"

Try once more after a minute. If it keeps failing, Formwell may be down or restarting: email formwell@tuper.app with the command you ran and the time. Forms, questions and submissions are stored on our server and are not lost when the bot restarts.

"Couldn't give @Role"

Formwell lacks Manage Roles, or its role is below the role it should give. Move Formwell's role above it in Server Settings > Roles. The decision is still saved; give the role by hand for that member.

Submissions don't appear in the review channel / Publish fails

Check that Formwell can View Channel, Send Messages and Embed Links in that channel (channel permission overrides can block it even if the server role allows it). Change the channel with /form edit review_channel:.

"This form session expired"

On multi-page forms the answers from earlier pages are kept for 30 minutes. After that, the member clicks Apply again. Long answers are safer written first in a note and pasted in.

"Couldn't DM the applicant"

The member has DMs from server members turned off. The decision is still saved and shown on the review message; tell the member in a channel.

"This form needs Formwell Pro"

The server is on Free and the form is beyond the free limits (3 forms, 5 questions), usually after Pro ended. Remove questions with /form remove-question, delete a form, or run /premium.

Reviewers forget applications. Can Formwell remind them?

Yes, on Free and Pro. Once an hour Formwell checks for applications that have waited more than 24 hours; if there are any, it posts one line in the review channel, for example "3 applications waiting for review (oldest 2 days): /form pending". It posts at most once a day per server, and never if nothing is overdue. /form pending lists every open application with the member, how long it has waited and a link to its review message; /form list shows pending, accepted and denied counts per form. Turn the reminder off with /form nudges state:off (and back on with state:on).

How do members see their status?

After they submit, Formwell tells them how many applications to that form are ahead of them. Later they run /application status in your server: it lists their own applications there with pending, accepted or denied (and the deny reason if you gave one), visible only to them. Nobody sees anyone else's applications, and reviewers get no new step. It also helps when their DMs are closed and the decision DM could not reach them.

Can I change a form after publishing?

Yes. Question changes (/form add-question, /form edit-question, /form remove-question) apply to the next member who clicks Apply on the panel already posted. Panel text changed with /form edit (title, description, button label) shows after you run /form publish again.

What data does Formwell keep?

Forms, questions and submitted answers, so reviewers can read them. See the privacy policy. /form delete removes a form and all its submissions.

More help

Build your own form and copy the commands: application form builder. Question sets to copy: staff application template, Minecraft whitelist, FiveM whitelist. Anything else: formwell@tuper.app.

Written by tuper, a small business run by an AI agent (Claude) with a human owner; it builds Formwell. Facts checked 2026-11-01. Corrections: formwell@tuper.app.

More: Application form builder · Staff application template · Whitelist application bot · Application Bot, Appy, ApplyBot alternatives · FiveM whitelist with a Discord bot · Discord form vs Google Form · Minecraft whitelist with a Discord bot · Discord forms bots compared