Starts with a schedule and a button
Event sign-ups
Eight people say they are coming to game night and three show up. The bot posts the event every Friday at 18:00 with a Sign up button, then sends everyone on the list a DM half an hour before it starts.
Illustration. The real interface may look different.
How it works
A schedule posts the announcement in your events channel.
Sign up saves the member to the list.
Before the start, everyone on the list gets a reminder by DM.
How to make event sign-ups on Discord
Two schedules frame the event: one posts it and empties the list, the other sends the reminders and closes it. The button in between adds members to one stored list.
Describe it to your AI assistant
Half the people who say they're coming to game night forget about it. Build an event sign-up module: every Friday at 18:00, post the game night announcement in #events with a Sign up button and start a fresh list. A click adds the member once and answers privately. At 19:30, DM everyone on the list that it starts at 20:00 in the Lounge voice channel, then close the sign-ups. Make the channel and the event name settings.
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
Three flows: a "Schedule" trigger posts the event, the Sign up button fills the list, and a second schedule sends the reminders. In the "Create new flow" dialog, "Start from a template" offers this build as "Event signup".
The 3 flows, step by stepStep names are the ones the editor shows.
Flow 1Post the event
Trigger: ScheduleFridays at 18:00.
- Store a valueOpens the sign-ups and empties the list from last week.
- Create embedCreates the embed with your event name.
- Create messageBuilds the message with the Sign up button.
- Send messagePosts it in the sign-up channel.
Flow 2Sign up
Trigger: Button clickedfrom the Sign up button.
- Read a stored valueReads whether sign-ups are open, and the list.
- List containsChecks whether the member is already on it.
- Add item to stored listIf not, adds them.
- Reply to interactionAnswers privately: on the list, already on it, or closed.
Flow 3Remind
Trigger: Schedulea second schedule shortly before the event, 19:30 in our example.
- Read a stored valueReads the list.
- For each itemGoes through it member by member.
- Fetch member by IDFetches each member.
- Send DM to memberSends them the reminder by DM.
- Store a valueCloses the sign-ups until the next post.
Test it, change it
What it stores
- SignupsWhole serverOne list for the server: the members signed up for the next event.
- Signups openWhole serverA switch that is on between the post and the reminder.
How to test it
- 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.
- A new flow is a "Draft" and does not run in Discord. Switch it on and click "Save & activate".
- Move both schedules a few minutes ahead, sign up with a second account and wait for the DM. Then click Sign up again: the flow should say that sign-ups are closed.
- Each real run then shows up under "Executions", with the reason if it failed or was skipped.
What to change
- Day and time
- Both times are in the "Schedule" triggers of the two flows and follow your bot's timezone.
- Channel
- The "Signup channel" setting in the module's "Configuration" tab.
- Event name
- The "Event name" setting. It appears in the post and in the reminder.
- Wording
- The post is built in the first flow, the DM in the third.
Watch out for
- Members who do not accept DMs from server members will not get the reminder. Mention the time in the post as well.
- There is no way to sign off again in this build. Ask for a second button if your events have limited seats.
- The list holds one event at a time. Two events in the same week need two copies of the module.
Questions about this build
Can I limit the number of seats?
Yes. In the Sign up flow, compare the length of the list with your limit before the member is added, and answer "the event is full" otherwise.
Can members see who else signed up?
Not in this build. To show it, have the Sign up flow rewrite the post with the number of people coming, as in the scene at the top of this page.
How is this different from Discord's own events?
Discord events show up in the server's event list and let members mark themselves as interested. This build posts in a channel on your schedule and sends the reminder as a DM from your own bot.
More examples
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.