🌵
Setup Actions
Setup actions for your applications.
• Reply Action
• Voting Action
• Send Message to Text Channel Action
• Create Text Channel (tickets) Action
• Add Role to Member
• Remove Role From Member
Reply Actions are the response you want Formie to give to your members after they have finished filling out a form/application. These replies will only be visible to the member, so you don’t have to worry about clutter! To set it up, simply use
/actions add and choose Reply. No optional arguments are to be used with this action, so you can press send. When prompted, choose the Formie you’d like to apply the action to, and you’re done! Your Reply Action should look something like this: 
In these embeds, you can make use of your custom server emotes. To do this, you can follow the guide here (https://docs.formie.gg/how-to-find-emoji-ids) to get the emote ID of the emote you want to use. Make sure Formie has access to the server you’re getting the emotes from
The Voting Action is a way to hold a vote on a member’s form/application submission. The action will add buttons that say “Upvote” and “Downvote” to a log of the submissions from the
Send Message to Text Channel action, which will be covered next. Since it uses buttons, the voting process is anonymous. To start the process, simply run /actions add action:Voting. No optional arguments are required for this action, so press send. When prompted to, select the Formie you’re applying the action to. 
Once someone submits their form/application, Formie will add buttons just like below on whatever
Send Message to Text Channel action is right below it.
The Voting Action will not work if there is no
Send Message to Text Channel Action right below or somewhere after it. If the Action is above it, it will not apply it to that Action, and if there’s no action below it, it won’t do the voting at all.Message Actions (nickname for simplicity) are basically webhooks that send an embed to a channel of your choice. With them, you can log that someone completed an application/form and their answers on the form. You can also use this Action like a suggestion system, and have the answers (suggestions) go to the suggestion channel. The point is, your options are seemingly limitless. To start setting this up, run
/actions add action:Send Message To Text Channel (Use channel argument) channel:#application-logging. This time, the optional channel argument is required, which will be the channel you want the webhook to go. Once you have that, press send, and select the Formie you’re applying the action to.
Once you’ve chosen the Formie, you will be greeted with a screen similar to the Add Text Input screen. Here you’ll type what you’d like the webhook embed to have.
Variable Guide
{user} - Mentions the member who submitted the application/form. {value-1} - Inserts the member’s answer to the first question. If you have multiple questions to your Formie, simply replace the 1 with the number that matches the question number. You don’t have to put the {value} variables in numerical order.The Create Text Channel Action creates a ticket once the member submits their form/application, making it perfect for support forms or something of the like. To start this, run
/actions add action:Create ticket (Optional category) category:#Ticket Testing. For this Action, the optional category argument is required. This is where your ticket category should be. Once you have that and press send, select the Formie you are applying the action to.
Once you’ve selected the Formie you’re applying the action to, a screen similar to the one from the Message Action setup will appear. Here you can type whatever you want to go inside the embed that gets sent when the ticket is created.
Variable Guide
{user} - Mentions the member who submitted the application/form. {value-1} - Inserts the member’s answer to the first question. If you have multiple questions to your Formie, simply replace the 1 with the number that matches the question number. You don’t have to put the {value} variables in numerical order.You can change the name of the channel by using the second label:
{name} - name of ticket creator
When your ticket is created, it should look something like the image below. Make sure your staff role can view the category the tickets are being sent to!
The Add Role Action is fairly simple, since it gives the member a role once they’ve submitted their application/form. The setup is extremely easy, start by running
/actions add action:Add Role To Member (Use role argument) role:@Applied. The optional role argument is required for this action. For this one, simply choose the role you’d like Formie to give to the members after they’ve submitted their form/application, and that’s it.
Just like with members, Formie can’t give roles that are above it on the role hierarchy. Please make sure it’s role is above the role you’re trying to give, and that it exists.
The Remove Role Action is just as simply, and is the exact opposite of the Add Role Action. Instead of giving a role, it takes it away. To set this up, run
/actions add action:Remove Role From Member (Use role argument) role:@Applicant. For this action, the optional role argument is required. Simply select the role you’d like Formie to remove once the members submit their form/application, and that’s all. 
Just like with members, Formie can’t remove roles that are above it on the role hierarchy. Please make sure it’s role is above the role you’re trying to give, and that it exists.
Last modified 10mo ago