Skip to main content

Discord — Connection

The Connection page links one Discord server to your EventSale workspace. Once connected, EventSale can send event announcements, application updates, submission news, payment reminders, and marketing messages into the channels you choose.

EventSale Discord connection and channel routing

Connect the server​

Choose Connect Discord and complete the Discord authorization window. Discord asks you to select a server and approve the permissions required by the shared EventSale bot. Pick the server used by your event team, not a personal test server unless you are deliberately testing.

After authorization, use Re-scan channels. The scan makes the channels available in the routing selectors. If a new channel is created later, scan again before trying to route messages to it.

Bot identity and runtime​

The Visible bot name in this server field changes the name visitors see for this workspace. It does not create a second bot. Use a recognizable name such as your event name.

Runtime controls whether the bot is allowed to process EventSale work for this workspace. Keep it Enabled for live delivery. Temporarily disable it when you want to pause automated Discord activity while preparing templates or changing routes.

You can upload a workspace-specific bot photo or return to the shared CaveTech name and photo. Save with Save bot identity; a badge showing unsaved changes means the new identity is not active yet.

Channel routing​

Each route answers two questions: where should this kind of message go, and which template should be used by default? Choose a Channel, select a State, and choose the Default layout for each purpose. Save each route after checking it.

Typical purposes include announcements, submissions, payments, marketing, and operations. A purpose with no channel is not ready to deliver. A disabled route is intentionally paused even if its channel and template are present.

Use Preview layout to check the message before saving. The connection summary shows how many routes are mapped. Aim for every purpose you actually use to have an active channel and a suitable template.

A simple first-time checklist​

  1. Connect the correct Discord server.
  2. Re-scan channels.
  3. Set the bot name and photo, then save.
  4. Map each required purpose to a channel.
  5. Choose a default template for each route.
  6. Confirm the Discord runtime is enabled.
  7. Send a test from the Templates page before relying on automation.

If the connection is no longer the right one, disconnect it deliberately and reconnect the correct server. Disconnecting stops future deliveries for this workspace; it does not erase EventSale applications, submissions, or payment records.