Collect Event RSVPs in Discord With Reminders

Before you start

• A connected bot with Events & Reminders enabled for your Discord server.
• A text or announcement channel where you can view and send messages. The bot also needs Embed Links, Attach Files and Read Message History.
• A future start time and a timezone such as Europe/London. Choose an event manager role if someone without Manage Server should manage other organizers’ events.

1. Choose a channel, timezone and reminders

   Create an account through the sign-up link, connect your bot and enable Events & Reminders in Modules. Open Settings, select your server and set a default event channel, timezone and optional manager role. Save the settings before creating an event.

   Reminder offsets are minutes before the start. The defaults are 60 and 10; you can save up to ten offsets from 1 to 20160 minutes (two weeks), or an empty list for no reminders. Offsets that would fall before the event’s creation are not scheduled. Let members opt in to reminders is off by default and applies to events created after it is enabled. Keep native synchronization off for your first test if you only need an RSVP post.

2. Create, list and cancel an event

   In Discord, choose /event create and fill in title and time. Enter a future local date and time in YYYY-MM-DD HH:mm format. The timezone option overrides the saved default; natural-language times are not accepted. You can select a channel for this event, otherwise the saved default or invoking channel is used.

   For a test, choose a title such as Game Night, capacity 2 and duration 120. These are example settings: capacity accepts 1 to 10000, and duration is in minutes from 1 to 10080, defaulting to 60. Omit capacity if you do not need a Going limit. Save the returned event ID.

   Use /event list to see up to fifteen scheduled, unended events in channels you can view. Use /event cancel with the id option to cancel an event you organized; a member with Manage Server or the configured manager role can cancel others’ events. Before it starts, /event edit lets an organizer or manager change its title. It does not change the time or capacity.

3. Collect responses and handle a full event

   Going records an intention to attend, Maybe records an uncertain response, and Can’t records an intention not to attend. A member has one response at a time. Clicking a different button changes it; clicking the same choice again removes it. Responses close at the start time, and cancellation also disables the buttons.

   When Going is full, another Going response joins the waitlist. If a place opens, the first waiting member moves into Going. Clicking Going again while waitlisted withdraws that request. Maybe and Can’t do not consume Going places. Capacity limits the RSVP list; it does not control access to a voice room or verify who turns up.

4. Schedule reminders, repeats and CSV summaries

   Reminders post in the event channel and mention Going members, unless you selected a reminder role when creating the event. Selecting that role requires Manage Server or the configured manager role, plus the necessary mention permissions. If Let members opt in to reminders was enabled before the event was created, its Remind me button lets a member add or remove themselves from channel reminders without changing their RSVP. The button is absent by default, and a selected reminder role takes priority. These are channel reminders, not personal DMs.

   The repeat option accepts none, daily, weekly or monthly. After an occurrence ends and its summary is delivered, the bot creates the next future occurrence with empty response lists. Members must RSVP again. Repeats use the event’s timezone; after downtime, missed occurrences are skipped rather than recreated as a backlog.

   At the end, the bot posts a summary and attaches a CSV with user_id and rsvp columns for Going, Maybe, Can’t and Waitlist responses. This export is available to people who can read the event channel. It is a record of RSVPs, not an attendance report.

   Events, responses and pending deliveries are saved in the bot database. Delivery is retried after failures, with message-history checks to reconcile uncertain sends. Reminders that are already past the start time are skipped. Preserve storage and channel permissions; a stopped bot cannot deliver reminders on time.

5. Understand optional native Discord event sync

   The RSVP post works without creating a native Scheduled Event. Optional native sync creates a separate Discord event for new module events and their repeats. Enable it in settings before creating those events. The source channel must be visible to @everyone, and both the creator and bot need Create Events permission.

   The module manages its own linked native event’s title and lifecycle, but does not import native Interested users into Going or synchronize the RSVP lists. It does not adopt other administrators’ events or recreate a linked event that was manually deleted. Use /event status with the id option to inspect sync status and any native event link. A saved RSVP event can exist while native sync is waiting on permissions or a retry.