1. Opening Problem Statement
Meet Sarah, an event coordinator who runs weekly online webinars hosted on Zoom. Every time her recurring Zoom meeting link changes or needs to be refreshed, she must manually update the redirect link on her WordPress website to keep attendees connected seamlessly. On top of that, she has to notify her team on Slack that the meeting link has been updated. This back-and-forth takes up several hours monthly, is prone to errors, and sometimes causes attendees to miss meetings due to outdated links.
This manual process leads to wasted time, lost attendee trust, and constant fire-fighting every time the meeting configuration changes. Sarah needs a reliable, hands-off way to keep the meeting redirect page current and keep the team informed immediately when any Zoom meeting updates happen.
2. What This Automation Does
This automation using n8n handles the whole process automatically every 360 days at 3 AM EST. Here’s what happens when it runs:
- Schedules a Zoom recurring meeting: Creates or refreshes a recurring Zoom meeting with custom settings like muted entry and participant video ON.
- Updates a WordPress page automatically: The meeting redirect URL on a WordPress page is updated with the latest join link from Zoom for seamless attendee redirect.
- Notifies Slack Channel: A message is sent to a designated Slack channel informing the team of the updated Zoom meeting link with a direct URL.
- Runs automatically without manual intervention: Scheduled via Cron job every 360 days at 3 AM to keep meetings fresh and synchronize info.
- Customizes Zoom meeting experience: Automatically sets meeting options such as mute on entry, allowing join before host, and enabling participant video per meeting.
- Eliminates human errors: No more broken or outdated links on WordPress or Slack communication errors.
3. Prerequisites ⚙️
- An n8n account, either cloud-hosted or self-hosted (consider Hostinger for self-hosting)
- A Zoom account with OAuth2 credentials configured in n8n
- A WordPress website with ability to edit pages programmatically via API and page ID to update redirect content
- A Slack workspace with an authorized bot and channel ID to send messages
4. Step-by-Step Guide
Step 1: Set Up the Scheduled Trigger Node
Navigate to the n8n editor. Click Add Node → Search and select Schedule Trigger.
Configure it to run every 360 days at 3 AM. Under Parameters → Rule, set:
– Interval: Days Interval = 360
– Trigger At Hour = 3
You should see a summary of “Runs every 360 days at 03:00 hours”.
This ensures the workflow automatically triggers to refresh your Zoom meeting annually.
Common mistake: Not setting the timezone correctly could cause unexpected trigger times. Check your n8n server time or confirm timezone setting if available.
Step 2: Configure the Zoom Node to Create a Recurring Meeting
Click Add Node → Search Zoom node.
Set Authentication to OAuth2 (make sure your credentials are authorized).
Under Parameters:
– Topic: “New Meeting” (or your custom meeting name)
– Meeting Type: Recurring meeting (type = 3)
– Settings:
• Mute Upon Entry: true
• Allow Join Before Host: true
• Participant Video: true
– Timezone: America/New_York (adjust as needed)
These settings customize how participants enter and behave in the meeting.
Expected outcome: A new recurring Zoom meeting is created or refreshed with these settings and its join URL is output for next step.
Common mistake: Forgetting to authenticate with OAuth2 properly will cause API call failures.
Step 3: Update WordPress Page with Redirect Meta Refresh
Add a WordPress node.
Configure it to Update a page and provide the pageId of the WordPress page that contains your meeting redirect.
Under Update Fields, enter the Content HTML exactly as:
Redirecting, please wait a moment. Meeting will begin shortly…
This meta refresh tag ensures visitors are immediately redirected to the latest Zoom meeting URL.
Expected outcome: Your WordPress page content updates automatically with the new Zoom join link after each workflow run.
Common mistake: Using incorrect WordPress page ID or insufficient API permissions results in update failures.
Step 4: Notify Slack Channel of Meeting Update
Add a Slack node.
Set the channel ID where you want to post the update notification.
Configure the message text as:
Zoom recurring meeting updated!
{{ $('Zoom').item.json.join_url }}This message lets your team instantly know the fresh meeting link.
Expected outcome: A Slack message posts each time the Zoom meeting refreshes automatically.
Common mistake: Using invalid Slack channel ID or missing bot permissions will prevent messages from sending.
5. Customizations ✏️
- Change recurrence frequency: In the Schedule Trigger node, adjust
daysIntervalandtriggerAtHourto reflect how often you want the Zoom meeting refreshed automatically. - Modify meeting settings: Inside the Zoom node’s
additionalFields.settings, toggle options likemuteUponEntryorparticipantVideoto customize participant experience. - Update WordPress page ID: Change the
pageIdin the WordPress node to target a different page for your redirect. - Change Slack channel: In the Slack node, update the channel ID to notify a different team or private group.
- Add extra Slack message details: Edit the Slack message text to include meeting time, agenda, or reminders using additional data from Zoom if desired.
6. Troubleshooting 🔧
Problem: “Zoom node authentication failed”
Cause: OAuth2 credentials are expired or incorrectly configured.
Solution: Go to Credentials in n8n, re-authenticate your Zoom OAuth2 credentials, then retest the node.
Problem: “WordPress page update failed”
Cause: Incorrect pageId or insufficient API permissions.
Solution: Verify the page ID in WordPress admin, ensure your API user has edit permissions, and test the node separately.
Problem: “Slack message not sent”
Cause: Invalid channel ID or missing bot token permissions.
Solution: Confirm the channel ID is correct, and your Slack bot token has necessary scopes like chat:write.
7. Pre-Production Checklist ✅
- Test the Schedule Trigger by manually triggering it once to verify workflow starts correctly.
- Manually run the Zoom node to confirm meeting is created with desired options and output includes a join URL.
- Use your WordPress API token/user to update the targeted page and verify content changed successfully.
- Check Slack bot messaging by sending a test message to the chosen channel.
- Backup your WordPress page content before deploying automation to avoid accidental data loss.
8. Deployment Guide
Activate the workflow in n8n by toggling it to “Active” mode.
Verify the schedule trigger runs as expected by checking the last execution timestamp.
Monitor workflow logs especially on the first few runs to ensure Zoom meetings refresh, WordPress updates, and Slack notifications happen without errors.
For long-term stability, enable email notifications in n8n for workflow failures to quickly react.
9. FAQs
Q: Can I run this more frequently than every 360 days?
A: Yes, just adjust the Schedule Trigger node interval parameters to your preferred frequency.
Q: Does this automation consume Zoom API credits?
A: Zoom’s API limits are generally high for this type of call, but always monitor your usage depending on the number of calls and your plan.
Q: Is the WordPress update safe without affecting other content?
A: Yes, as long as you specify the correct page ID and only update the intended content field.
10. Conclusion
By building this n8n workflow, you’ve automated the refresh of recurring Zoom meetings, updated your WordPress redirect page in real-time, and instantly notified your Slack workspace. Sarah would now save hours monthly, avoid errors, and keep attendees connected without lifting a finger.
Next, you might explore automations to add Zoom meeting transcripts to a documentation system or integrate calendar invites automatically to participant emails. This step-by-step has you confidently managing multi-tool workflows seamlessly.
Keep experimenting with your automation skills — it only gets easier from here! ⏱️