The Forms Builder module enables users to create Q/A forms that are presented to end-users by sending a Direct Message to the bot. The Q/As can be set up to be a sequence of multi-choice or open questions, with the final output (submission) being sent into a server channel by the bot itself for further validation, priority assignment and optional integration with external services.
(Optional features) Upon accepting a submission, a submission summary can be forwarded as a read-only post to a different channel and can be automatically given an “upvote” and “downvote” reaction for people to show their support (or lack thereof) to the specific submission.
Currently, each form submission can be configured to remain within the Discord realm, or uploaded to Trello (a powerful web-based, list-making application) as a “Trello card” (“share mode”).
Trello integration also includes the 2-way synchronization of upvotes/downvotes and comments number from and to Discord and Trello (showing the number of upvotes and downvotes on the Trello card, as well as showing the current number of Trello comments and votes on the Discord message), and Discord DM notifications to the author of the submission upon Trello card activities (new comments, title changes, card archival, etc.).
For the Trello integration to work, some limitations currently apply:
You must invite the bot to your Trello team and give it permissions to edit the board in order for the bot to monitor, post and update cards.
You must pair the Discord server with the Trello team by using the !trellopair command. Each Discord server can only be paired with 1 Trello team.
Form settings will be fixed once a user sends a submission. Any change to a form will not apply to submissions that are already in the approval queue. This also means that the Trello board must be set (thus, exist) before a submission is sent.
A web dashboard (BETA) will soon be available to create, edit and and maintain forms.
Out of the box, each server is limited to having a total of 1 available form. If you want to remove this limitation and have up to 20 forms, you can unlock the number of forms as a Premium feature (see: Premium Perks).
!trellopair [team name]
Pairs a Discord server with a Trello team. Using the command without the team name will unpair the server from the Trello team.
The team name is the one you find inside the Trello URL within the team page, which usually has this form:
This command is only available in a Direct Message channel with the bot. It will not work in actual servers, and it’s not subject to any permissions other than a blacklist check (see !formblacklist).
Shows the available forms for the servers a user is currently in, giving the option to start filling a submission.
Initializes a new form builder. The bot will guide the user into setting up the basic configurations and first question.
Forms questions will expire after:
5 minutes, for reaction questions;
15 minutes, for open questions.
The format to set a form question is:
(message/reaction)|(text of the question)|(list of reactions)/[validation words]|[alias]|[Trello mapping]
Each question has to be set using 5 fields, separated by one
messagewill require the question to be answered with a plain text message.
reactionwill require the user to select one answer by clicking on a reaction that will be added to the question by the bot.
Second field: The actual question.
reactionis selected in the first field, this field will list all of the possible answers, using
;to separate these answers. If this is the case, this field is mandatory.
messageis selected in the first field, this field will include a list of validation words: any answer given by the target user will be ignored unless the message contains at least one of the chosen words/sentences (case insensitive). Again, you can separate words/sentences with
;. If this is the case, this field is optional.
Due to Discord limitations, there can only be a maximum of 20 answers in a reaction question. Answers from the 21st onward will be ignored.
Fourth field: The question “alias”. This is the title that will replace the full question when the feedback is posted in the server channel. This field is optional, but it’s higly suggested that you set an alias.
Fifth field: This will map the question into one of the entities of the Trello board. While
attachmenthave a meaning in in-Discord share mode (see !formsetup), the rest is only useful if you are interested in Trello integration; you can choose whether or not including Trello integration later:
titlewill use the answer as the title of a card.
listwill use the answer as the title of a list.
labelwill add the answer as a card label.
attachmentwill add the answer as a card attachment. If the “attachments highlighting” option is active, fields flagged as
attachmentwill also appear in the public in-Discord summary message.
descriptionwill add the answer as part of the description text, with the format:
privatewill show the answer into the “in-Discord” embed during the authorization process but won’t upload the field to Trello (or show it in the public in-Discord summary message) whatsoever.
A field being “optional” means that its content can be left blank, but the field itself has to exist; e.g.
message|Heads or Tails?||The user picked...|
In order to ease the creation of these complex strings, you can use this Forms Builder Helper to create a pre-made string to be used in this phase. Just create a copy of that sheet and customize it to your needs.
When setting the authorization channel, “authorized users” will be those that are enabled to use the module using the Permissions System, not those that are mentioned in when a new feedback is posted.
!foset (form id)
Opens the forms builder interactive configuration menu. Use the menu items to configure the available settings.
Options 1. and 2. are used to save the settings you applied through the menu (the settings will not apply until you save them), or discard said changes.
“Set title” sets the title of the form, as it appears when listed by GiselleBot.
“Set color” sets the form embeds color.
“Set authorization channel” sets the channel where form submissions are sent to for the initial validation by the authorized users. This option is mandatory.
“Set forwarding channel(s)” sets the additional forwarding channels where, if set, the public in-Discord summary message will be sent to. This is optional.
“Set role mention(s)” sets the list of mentioned roles when a submission is received.
Mentioned roles are not the roles that are authorized to validate the entry: those roles are set through the Permissions module (see !permenablemod).
“Toggle share mode” sets the final target of a validated submission to either Trello, or just Discord.
“Toggle publish status” works as an alias of !formpublish and !formwithhold to make a form available or unavailable for server members through GiselleBot’s DMs.
“Toggle upvoting” enables or disables the upvote tracking feature (and upvote arrow application for new submissions) on a specific form.
“Toggle downvoting” enables or disables the downvote tracking feature (and downvote arrow application for new submissions) on a specific form.
Disabling a voting arrow will not remove the
:arrow_down:reaction from existing submissions, but it will stop those submissions’ votes from being tracked in Trello (if you are using the Trello share mode). New submissions will not have the corresponding arrow reaction applied.
Enabling a previously disabled voting arrow will not reapply the arrow to existing submissions. It will track the votes as long as any user adds the
:arrow_down:reaction to the public submission message (as long as it’s the native Discord reaction and not a custom one).
“Toggle highlighting of attachments” enables or disables the public embed from having an additional field where all of the “attachment”-flagged fields are linked, using their TinyURL short link (using the same engine behind !shorturl).
(Only useful in “Trello share mode”) “Set target board” lists the available boards within the paired Trello team (refer to !trellopair) and sets the linked Trello board for the current form. Renaming a board in Trello will not affect this link.
(Only useful in “Trello share mode”) “Toggle extended embed” enables or disabled the public in-Discord summary message extended mode: by default, a submission that has Trello set as “share mode” will only show a short summary of the submission, while the actual full post will be found in the linked Trello card. By enabling the “extended embed”, the whole submission will be kept within Discord, while still having a link to the corresponding Trello card.
(Only useful in “Discord share mode” or “Trello share mode” with “extended embed” active) “Anonymize public submissions” completely hides the submitter info from the public in-Discord summary message, keeping the user’s anonymity intact (as long as “private”-flagged fields are used for other kinds of recognizable data within the form).
Here’s an example of a public in-Discord summary message with Trello share mode, extended embed, attachments highlighting and anonymizer on.
!foaq (form id)
Adds a question to an existing form. Follow the instructions given by the bot to configure the question. Refer to the previous paragraph for more details.
!foeq (form id) (question id)
Replaces the selected question from an existing form with a new one. Refer to the previous paragraphs for more details.
!foeq 1 5
!forq (form id) (question id)
Deletes a specific question from an existing form.
!forq 1 5
!fosq (form id) (question_ids)
Sorts the questions of an existing workflow into the specified order.
!fosq 1 4 5 1 2 3
!fopub (form id)
!fowh (form id)
Witholds a previously published form, making it unavailable for server members. This is particularly useful, or even required, for forms that need to be edited/deleted.
Prints the list of available forms for the current server. For each form, a preview of each question (and the corresponding question ID) is shown.
!fobl (user id(s)/mention(s)/q_name(s))
Toggles one (or more) user’s presence on the forms blacklist. Blacklisted users won’t be able to see any available form for the current server.