Google Calendar logo
Discord logo

Workflow template

Announce new Google Calendar events in Discord

Announce new Google Calendar events in a Discord channel. Send the title, start, end and calendar link, preserving timestamp offsets and all-day dates without copying descriptions or attendees.

How it works

From a newly created event to a Discord announcement

1 Trigger · 1 Action
Google Calendar1 · Trigger

New Event

Poll the selected calendar for new events after an initial baseline sync. Primary is preselected and can be changed; existing events, later edits and cancellations are not synchronized.

Discord2 · Action

Notify the calendar updates channel

Post title, start, end and the source link through the destination channel webhook. Disable user, role and everyone mentions and suppress link embeds. Include the all-day exclusive-end explanation.

The result

An event-creation notice in Discord

Timed events retain their timestamp offsets. All-day events use dates, and the end date marks the first day outside the event.

Example Discord calendar announcement

New calendar event: Köln planning session — Grüße Start: 2026-11-16T10:00:00+02:00 End: 2026-11-16T10:30:00+02:00 For all-day events, the end date is exclusive. <https://calendar.google.com/calendar/event?eid=example-discord-planning>

Fictional event. This announces creation rather than reminding people shortly before the scheduled start. Descriptions, attendees, meeting links and attachments are not copied.

Before activation

Set up your workflow

  1. Select the Google Calendar source

    Connect Google Calendar and choose the calendar to watch. The primary calendar is preselected; use a test calendar for the first fictional event.

  2. Connect the destination Discord webhook

    Connect the Discord channel through its webhook and select that connection for the action. No bot installation is needed. Check who should see the copied title and event times.

  3. Wait for initial sync before creating an event

    Activate and allow the first poll to establish a baseline. Then create a new fictional event in the selected calendar and inspect its notice after a later scheduled poll.

Details and limitations
  • Creation notices rather than reminders. Existing events are not imported. Later edits and cancellations do not update or remove the Discord message. The workflow is not an upcoming-event reminder or a live calendar mirror.

  • All-day end dates are exclusive. An all-day event starting 2026-11-16 and ending 2026-11-17 covers November 16 only. Timed events keep the supplied offsets instead of converting to each Discord reader’s local timezone.

  • Limited content with mentions disabled. The prepared message excludes descriptions, attendee addresses, meeting links and attachments. Mentions and embeds are disabled. Channel members still need calendar access to open the source link.

  • Message length and repeated delivery. Discord message-length limits apply, so shorten unusually long event titles. Manual reruns or ambiguous provider failures can send duplicate announcements.

Questions about this template

Should I create the test event before the first poll?

Wait for the initial baseline sync first, then create the new event. Existing events are not backfilled by this recipe.

Is this a reminder shortly before the event starts?

No. It announces event creation when polling observes the new event. It does not schedule an upcoming-event reminder.

What does an exclusive all-day end date mean?

The end date is the first day outside the event. A start of November 16 and end of November 17 describes an all-day event on November 16 only.

Does Discord need a bot, and can event text ping everyone?

Connect the destination channel through its webhook; no bot installation is needed. The prepared action disables user, role and everyone mentions and suppresses link previews.