Keep your team calendar in step with your Discord server. Event details move from Discord into Google Calendar on a regular timer, so people see the latest dates and times without manual updates. Great for community, marketing, and events teams that host sessions on Discord.

On a set schedule, the build calls the Discord API to list scheduled events for one server. A Configure node holds the server ID, which is used in the request URL. Each Discord event ID is used to look up a matching Google Calendar event. If one exists, the date, time, and summary are updated. If none exists, a new calendar event is created with the same ID, name, description, location, and start and end times. This keeps one source of truth and avoids duplicates.

Setup is simple. You need a Discord bot token for header auth and a Google account connected through OAuth in n8n. Pick the calendar once in all Google Calendar nodes and set your check interval in the schedule trigger. Expect to remove double entry, reduce mistakes, and keep everyone aligned. Perfect for recurring community calls, webinars, workshops, and tournaments that start on Discord.

• Scheduled trigger runs the sync at the times you choose
• Server ID is stored in a Configure node and used in the API call
• HTTP request pulls scheduled events from Discord with header auth
• Google Calendar lookup checks for an event by the Discord event ID
• Conditional logic decides whether to create a new event or update an existing one
• Create action sets summary, description, location, start, and end from Discord fields
• Update action adjusts time and title to mirror changes on Discord

• Reduce manual copy from 15 minutes per event to 1 minute
• Keep Discord and Google Calendar in sync without double entry
• Improve event data accuracy by removing copy paste errors
• Ensure timely updates so teams always see the latest schedule
• Connect community planning in Discord with team calendars

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Discord and Google Calendar. See the Tools Required section above for links to create accounts with these services.
3. Open the Configure node and enter your Discord server ID in the guild_id field. You can copy it from your server settings if Developer Mode is enabled in Discord.
4. In the List scheduled events from Discord node, click the Credential to connect with dropdown, choose Create new credential, select HTTP Header Auth, then add a header named Authorization with value Bot YOUR_DISCORD_BOT_TOKEN. Save and test the node to confirm it returns events.
5. Open each Google Calendar node (Get events, Create event, Update event details). In the Credential dropdown, click Create new credential and follow the on screen steps to connect with Google Calendar OAuth. Approve the requested permissions.
6. In all Google Calendar nodes, replace the [UPDATE ME] calendar with the same target calendar. Use one calendar for Get, Create, and Update so IDs match.
7. Check field mappings: the Create event node should set the event ID to the Discord event id and map summary, description, location, start, and end from the Discord payload.
8. Set your timing in the On schedule node. For near real time sync, choose every 5 to 15 minutes based on your needs.
9. Create a test scheduled event in Discord and run the workflow once. Confirm a new event appears in Google Calendar with the same title and time.
10. Edit the Discord event time or name, run again, and verify the calendar event updates instead of creating a duplicate.
11. Troubleshoot: If you see 401 from Discord, check the bot token and that the bot is in the server. If Google returns an auth error, reconnect OAuth and select the same calendar in all nodes. If times look off, confirm both systems use the same timezone.