Forms
Key features
Custom slash-command forms
Create forms that appear as guild slash commands. Each form has its own command name, description, fields, submission behaviour, and response handling.
Flexible field types
Collect structured answers with text inputs, select choices, file upload prompts, radio choices, checkbox groups, and single checkbox fields.
Submission actions
After a member submits a form, Nox can post a submission embed, assign a role, send a channel message, create a staff review thread, reply to the submitter, or skip follow-up actions until staff review is complete.
Requirements and cooldown
Gate who can run a form by member level, currency balance, or membership age, and add a per-user or whole-guild cooldown so the command cannot be rerun too quickly.
Response browser
Staff can review response counts, filter by form and date range, page through submitted answers, and delete stored responses from the dashboard.
Best for
Applications, signups, reports, suggestions, and structured staff intake.
Workflows where staff need consistent answers before deciding what to do next.
Communities that want member-facing slash commands without writing custom bot code.
How it works
Build and publish the form
Staff configure the command name, description, fields, submission channel, anonymity, approval requirement, and actions. Nox creates or updates the matching Discord application command.
A member runs the command
When the member uses the form command, Nox resolves the Discord command id to the configured form and opens a Discord modal with the current fields.
Nox stores the response
On modal submit, Nox prevents duplicate processing, stores the response and ordered answers, and records any Discord message ids created by submission actions.
Actions and review happen after submission
Configured actions run after the response is accepted. Staff can review responses in the dashboard, delete stored responses, and inspect the Errors page when Discord-side actions fail.
Setup checklist
Choose a unique slash command name and a clear description.
Add fields in the order members should answer them, with clear labels and option text.
Choose whether submissions should be anonymous to staff-facing outputs.
Configure a submission channel if staff should receive response embeds.
Add any requirement gates (level, currency, or membership age) and a cooldown if the form should be limited to certain members or rate limited.
Review every action that sends messages, creates threads, or assigns roles before publishing.
Fields, actions, and requirements
Forms collect answers through ordered fields.
| Field type | Collects |
|---|---|
| Text | A short or paragraph text answer |
| Select | One choice from a list |
| Radio | One option from a small set |
| Checkbox group | Any number of options |
| Single checkbox | A yes or no acknowledgement |
| File prompt | Asks the member to attach a file |
One to five fields per form.
After a submission is accepted, Nox runs the configured actions.
| Action | What it does |
|---|---|
| Reply | Respond to the member who submitted |
| Send message | Post a message to a chosen channel |
| Assign role | Grant a role to the submitter |
| Create thread | Open a staff review thread |
One to four actions, including at least one reply. A reply action can appear at most once.
Requirements gate who is allowed to run the form, and a cooldown limits how often it can run.
| Gate (minimum or maximum) | Checks the member's… |
|---|---|
| Level | levelling level |
| Currency | currency balance |
| Membership age | time since they joined the server |
Add up to five requirements. A cooldown applies per member or to the whole guild, from off up to 30 days.
Important notes
Forms create guild application commands. If Discord command creation is still being applied, the dashboard may report an in-flight or conflict state until it is safe to retry.
Form commands are dynamic, so this page cannot list every configured command in the global command reference. The dashboard and Discord Integrations view are the source for your guild's form commands.
Submission actions are best effort after the response is accepted. A role, message, thread, or reply action can fail independently and create an Errors page entry without deleting the stored response.
When approval is required, Nox stores the response and sends the pending reply, but it does not currently provide approve/reject buttons, timeouts, or reminders.
Deleting a response can also delete the linked Discord submission message. If that Discord delete fails, Nox records the failure and does not silently remove the stored record.
Troubleshooting
A form command does not appear in Discord
Check whether the form save returned an in-flight, conflict, or unknown Discord operation state. If the command was just created, wait for Discord to make it visible, then retry or repair from the dashboard.
A submission action did not run
Verify the target channel, thread permissions, role hierarchy, and message permissions needed by that action. Stored responses can succeed even when a later Discord action is recorded on the Errors page.
Response counts do not match expectations
Check the selected date range and form filter in the response browser. Retried modal submissions should not create extra stored responses.
Permissions
Discord permissions Nox needs for this feature and what each permission is used for.
