Forms Builder
See also
Building your first form? Building a Form walks through it step by step.
Users create Q/A forms, and an end-user answers them in a Direct Message to the bot. The questions can be a sequence of multiple-choice or open questions. When the user finishes, the bot posts the submission into a server channel, where it can be validated, assigned a priority, and passed on to other services.
Optional extras: when a submission is accepted, a summary of it can be forwarded as a read-only post to another channel, with an "upvote" and "downvote" reaction added so people can show support (or not) for that submission.
Each form submission can stay in Discord, or be uploaded to Trello (a web-based list-making application) as a "Trello card" ("share mode").
The Trello integration also syncs upvote/downvote and comment counts in both directions: the Trello card shows the number of upvotes and downvotes, and the Discord message shows the current number of Trello comments and votes. The submission author also gets a Discord DM when something changes on the Trello card (new comments, title changes, card archival, etc.).
Warning
The Trello integration has these requirements:
- You must invite GiselleBot to your Trello team and give it permissions to edit the board, so the bot can monitor, post and update cards. You can invite GiselleBot to your Trello team using this email address: [email protected].
- You must pair the Discord server with the Trello team from your server's Forms page on the dashboard. Each Discord server can only be paired with 1 Trello team.
- Form settings are fixed once a user sends a submission: changes to a form do not apply to submissions already in the approval queue. This also means the Trello board must exist and be set before a submission is sent.
Note
Users who can use the module through the Permissions System are always authorized to accept or reject any submission from any form. To let more roles accept or reject specific forms, set one or more roles as "authorized roles" on each form from your server's Forms page on the dashboard.
Note
Premium: Out of the box, each server is limited to having a total of 3 available forms. Base raises that to 10, Power to 20 (see Premium Perks).
Note
Creating, editing, publishing/withholding, and deleting forms, and blacklisting users from seeing them, are all done from your server's Forms page on the dashboard - see Form Management below.
Trello pairing (dashboard)
Note
Pairing a Trello team is done from your server's Forms page on the dashboard, not a Discord command.
Enter the team name, or a URL containing it (the team name is the part inside the Trello team page URL, usually the form https://trello.com/TEAM_NAME/home), to pair the server. The same field unpairs the server's currently-paired team.
Any number of Discord servers can pair the same Trello team, but each server must pass the verification step on its own (see below).
Pairing takes 2 steps. Starting a pairing sends a verification request to the target Trello team and gives you a unique 6-digit code, generated at random. The pairing only takes effect once you show that you can create cards on at least one team board.
GiselleBot then queries the team's boards for a card with the 6-digit code as its title. Go to one of the team boards and **create a card (in any list) with the provided 6-digit code as title**.If no card with the correct title appears within 5 minutes of starting the pairing, it fails. When the card is found, the pairing completes and the team boards become available in the Forms module. The verification card is deleted once the pairing completes.
/submit
Command Syntax
/submit
Command Description
Sends a DM to the user running the command, listing the forms available in the server it was run in and offering to start a submission.
Warning
/submit can only be run inside a server - it cannot be run directly in a Direct Message channel with GiselleBot to pick from a list of servers. Run it from within the server whose forms you want to fill out.
Permissions Needed
- User: None, other than a specific blacklist check (see Form Management below). The actual form submission always happens through GiselleBot's DMs.
Examples
/submit
Submit reactions (dashboard)
Note
Setting up and removing "submit reactions" happens on your server's Forms page on the dashboard. There is no Discord command for it.
As an alternative to running /submit in a server, authorized people can enable a specific reaction on a message (or on a message created by GiselleBot for that purpose), and GiselleBot sends the initial form submission DM to whoever clicks it. The Forms page lets you set this up on a specific message using a Discord message URL, a channel + message ID, or a brand-new message, and pick the reaction emoji.
Form Management
Note
All form authoring happens from your server's Forms page on the dashboard: initializing a form, adding/editing/removing/reordering its questions, configuring it (title, color, authorization channel, forwarding channels, authorized roles, share mode, upvoting/downvoting, attachment highlighting, Trello board, anonymization, and every other setting), publishing/withholding it, previewing it, deleting it, and blacklisting users from it.
On the Dashboard
Your server's Forms page covers the full authoring and management workflow that has no slash-command equivalent:
- Current Forms lists every form as a card (title, ON/OFF live status, Discord vs. Trello share mode), with Add New Form and, per form, a Manage link into that form's full editor (questions, title, color, authorization channel, forwarding channels, authorized roles, upvote/downvote, attachment highlighting, Trello board, anonymization, publish/withhold, preview, delete, and blacklist).
- Guild Form Settings has the server-wide Auto-Delete Submit Messages toggle (requires Manage Messages), which deletes the message used to submit a form once it's been submitted, and the server-wide Submission Cooldown (requires Manage Messages), described below.
- Reaction Messages lets you add or remove a "submit reaction" on any message.
- Blacklist lets you block specific users from seeing or submitting any of the server's forms.
- Trello Team is where you pair (or unpair) the server's Trello team, as described above.
Submission cooldown
Note
Configured on the dashboard, requires Manage Messages.
Guild Form Settings sets a server-wide minimum time, in seconds, between two submissions from the same member. It applies across every form on the server, and 0 disables it.
A single form can override it in its own editor with the Override Server Cooldown option:
- leaving the override off inherits the server-wide value,
- a positive number sets that form's own window,
0disables the cooldown for that form only.
A member who tries to submit inside the window gets a message naming the remaining time and is not taken through the form. The check runs after the form is chosen, so it works the same for /submit in a server, /submit in a DM, and a submit reaction.
See also
Full migration mapping for these commands: Migration Guide.