Your alliance lives in Discord. That's where strategies are planned, events are announced, and members stay connected. ApoClock's Discord integration makes sure your scheduling data lives there too — automatically, without any technical setup.
Three layers of Discord integration
ApoClock has three independent Discord features. Each solves a different problem. You can use any of them in isolation or all three together.
Layer 1: The 1-click wizard
This is the fastest way to connect ApoClock to your Discord server. As workspace owner:
- Open Settings in ApoClock.
- Go to the Discord section and click Connect Discord (1-click).
- Authorise with Discord — ApoClock shows a grid of every server where you're an admin.
- Pick your alliance server.
- Discord asks you to confirm adding the ApoClock bot — click Authorise.
- Pick which channel to post to.
- Done. The bot joins, a webhook is created automatically, and Guild Sync runs.
The whole process takes under 60 seconds. No webhook URL to copy, no bot token to configure, no developer portal visit required.
Once connected, a status card shows your server name, webhook status, and last sync date. To disconnect, hit the Disconnect button — the webhook is deleted and the bot leaves the server automatically.
Manage Server permission. If your alliance server is missing, ask its owner to give you that role first.Layer 2: Guild Sync — member avatars and presence
Guild Sync pulls data directly from your Discord server:
- Member avatars appear on each member's card in ApoClock.
- Live presence status shows who's currently Online, Idle, or Offline in Discord.
This means your ApoClock dashboard doesn't just show timezone data — it shows who's actually in Discord right now. For raid leaders and event coordinators, this is the difference between guessing and knowing.
Guild Sync runs automatically after the 1-click wizard completes, and refreshes periodically.
Layer 3: Member account linking
Each member can link their own personal Discord account to their card in ApoClock. This is separate from the server-level bot integration:
- The alliance leader provides a Discord Client ID in Settings (found in the Discord Developer Portal — a one-time step).
- Members click Link Discord on their card.
- They complete a standard Discord OAuth consent screen.
- ApoClock reads their Discord username and avatar — nothing else.
Member linking is fully client-side and requires no backend. Discord tokens are used once to fetch the user profile and then discarded.
What gets posted to Discord
Once connected, ApoClock can post to your chosen channel automatically:
- Goal Seek results — post the optimal event time with full member availability breakdown in one click. How Goal Seek works →
- Event announcements — when you create, update, or delete an event, an embed is posted to Discord with the APOC time, duration, recurrence schedule, and event description.
- Automated reminders — members receive a reminder embed 60 minutes and 15 minutes before each event. More on automated reminders →
All posts use rich Discord embeds with your alliance name, server colours, and timestamp.
Manual webhook (advanced)
If you prefer not to add the bot, or you self-host ApoClock, you can paste a webhook URL directly into Settings > Discord > Manual setup. Create the webhook in Discord (Server Settings > Integrations > Webhooks > New Webhook), paste the URL, and hit Test Webhook to confirm it's working. A webhook URL looks like this:
https://discord.com/api/webhooks/1234567890123456789/AbCdEf-yourWebhookTokenGoesHereThe manual webhook supports Goal Seek posts and event reminders — everything except Guild Sync and presence.
Why this matters for your alliance
The biggest challenge in global alliances isn't the strategy — it's the communication overhead. Every event announcement manually typed, every timezone conversion redone, every reminder sent by hand represents time your leaders could spend actually playing.
ApoClock's Discord integration eliminates that overhead. Events go to Discord automatically. Reminders fire automatically. Your members never need to ask "what time is that for me?" again.