Starts with a slash command

Staff applications

Applications by DM get lost, and nobody knows who already replied. Here /apply opens a form and the answers arrive in your staff channel as one card. Whoever clicks Approve or Deny settles it for the whole team.

Illustration. The real interface may look different.

How it works

  1. /apply opens a form with the questions you chose.

  2. The answers are saved and posted to your staff channel as a card with two buttons.

  3. Approve gives the role and sends the applicant a DM. Deny closes the application.

  4. After the first decision the buttons stop working, so two mods can't answer the same person.

How to make staff applications on Discord

Four flows share three stored fields. Every application is filed under the ID of its own review card, so ten open applications never mix.

Describe it to your AI assistant

We need two more mods and I'm tired of getting applications by DM. Build a module where /apply opens a form asking for age, timezone and why they want to join the Crew. Post each application in #staff-applications as a card with Approve and Deny buttons that only the Crew role can use. Approve gives the Crew role and DMs the applicant. Deny asks the reviewer for a reason and DMs it. A card can only be decided once, and each member can only have one open application. Add a setting to pause applications.

Copy it and swap in your own channel and role names. Your assistant has a tested version of this example to start from.

Build it in the editor

Four flows: /apply, the submitted form, and one each for Approve and Deny. Every button names the flow it starts, so the card keeps working after a bot restart.

The 4 flows, step by stepStep names are the ones the editor shows.

Flow 1/apply

Trigger: Slash command/apply, with a one-minute cooldown per member.

  1. IfStops with a private reply if the "Accepting applications" setting is off.
  2. Is a value stored?Checks whether this member already has an application in the queue.
  3. Show modalOpens the form with your questions.

Flow 2Form submitted

Trigger: Modal submittedmatched to the application form.

  1. Set stored value if (atomic)Claims the member's one open slot. A double click on Submit cannot post two cards.
  2. Create embedBuilds the review card from the answers.
  3. Send messagePosts the card with the Approve and Deny buttons in your review channel.
  4. Build a shape valuePacks applicant, status and answers into one value.
  5. Store a valueStores it under the ID of the card.

Flow 3Approve

Trigger: Button clickedfrom the Approve button on the card.

  1. Member has roleLets only your reviewer role decide. Members with "Manage server" can too.
  2. Increment if (atomic)Claims the card. If two reviewers click in the same second, the second one is told it is already handled.
  3. Add role to memberGives the applicant the member role before anything else, so a role the bot cannot hand out is reported while the card is still open.
  4. Update messageRewrites the card with who approved it and when.
  5. Send DM to memberTells the applicant by DM. If their DMs are closed, the reviewer is told.
  6. Delete a stored valueDeletes the stored application and frees the member's slot.

Flow 4Deny

Trigger: Button clickedfrom the Deny button on the card.

  1. Show modal and await submitAsks the reviewer for a reason in a second form and waits for it.
  2. Increment if (atomic)Claims the card only once the reason is in, so an abandoned form leaves the application open.
  3. Edit messageRewrites the card with the decision and the reason.
  4. Send DM to memberSends the applicant the reason by DM.

Test it, change it

What it stores

  • ApplicationBy custom keyThe answers of one applicant, filed under the ID of the review card. Deleted when the card is decided.
  • Decision claimBy custom keyA counter per card that moves from 0 to 1 once. A nightly flow clears the leftovers.
  • Open applicationPer userA marker per member while their application is in the queue.

How to test it

  1. Open a flow in the editor and click "Test run". Choose the member under "Run as" and click "Run test". The run uses your real server data but sends, changes and deletes nothing, and shows what each step would have done.
  2. A new flow is a "Draft" and does not run in Discord. Switch it on and click "Save & activate".
  3. In Discord, run /apply with a second account, then click Approve from an account without the reviewer role. It should be refused. Approve again as a reviewer and check the role and the DM.
  4. Each real run then shows up under "Executions", with the reason if it failed or was skipped.

What to change

Channel
The review channel is a setting in the module's "Configuration" tab.
Roles
The reviewer role and the role granted on approval are settings too.
Questions
Edit the fields of the form in the "Show modal" step, then add the new answers to the card and to the stored application.
Wording
The card and both DMs are built in the Approve and Deny flows.

Watch out for

  • Your bot's role has to sit above the role it grants, and it needs "Manage roles". Otherwise Approve reports an error and the card stays open.
  • A reviewer has about five minutes to fill in the Deny reason. After that the form is gone and they click Deny again.
  • To pause applications, switch off "Accepting applications" in the settings. Open cards can still be decided.

Questions about this build

Can I ask more questions in the application form?

Yes. Add fields to the form in the /apply flow and carry them through to the review card. Keep the form short: people give up on long applications.

What happens when two mods decide at the same time?

Only the first click counts. The second reviewer gets a private message that the application was already handled, and the applicant gets one answer.

Can someone apply again after being denied?

Yes. The decision frees their slot, so /apply works again right away. If you want a waiting period, raise the cooldown on the /apply trigger.

Vuoi il tuo server nella beta?

La V3 è un sistema vasto e in continua evoluzione, quindi i server entrano uno alla volta e non tutti insieme. Ogni candidatura viene letta da una persona e ricevi una risposta entro pochi giorni.

I server già nella beta decidono buona parte di ciò che costruiamo dopo. Ciò che crei resta tuo: flow e moduli restano anche quando la beta finisce.