Notify and manage podcast edit status with WizCut and Slack
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 5 nodes and runs on Wizcut events (any). Along the way it connects Slack and Wizcut (community).
How it runs
Trigger: On Wizcut events (any).
- Route by Job Status (Switch): routes items into 3 branches
- Notify Slack: Map Speakers (Slack): post (message)
- Wizcut: start render
- Notify Slack: Episode Ready (Slack): post (message)
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 2 community packages, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @wizcut/n8n-nodes-wizcut is verified or supports 3.0 (used in On WizCut Status Change).
- Check that @wizcut/n8n-nodes-wizcut is verified or supports 3.0 (used in WizCut: Start Render).
Nodes used (4)
- Wizcut Trigger
@wizcut/n8n-nodes-wizcut.wizcutTrigger - Switch
n8n-nodes-base.switch - Slack
n8n-nodes-base.slack - Wizcut
@wizcut/n8n-nodes-wizcut.wizcut
From the author
Quick overview This workflow listens for WizCut job status webhooks and routes updates to Slack, prompting a speaker-to-camera mapping review, automatically starting the final render when cuts are ready, and notifying your team with the finished episode…