Monitor live event sentiment and send alerts with Fanbase MCP, Gemini, and Slack
Ready for 3.0What this workflow does
This AI workflow has 26 nodes and runs when someone submits an n8n form (“Configure Event Monitor”) (plus 1 other trigger). Along the way it connects Google Gemini, Slack and MCP Client.
How it runs
Trigger: When someone submits an n8n form (“Configure Event Monitor”) (plus 1 other trigger).
- Validate Config (Code): runs custom JavaScript code
- Get Active Event(events_config) (Data table): get
- Save Event Config(events_config) (Data table): uses Data table
- Window Gate (Code): runs custom JavaScript code
- Loop Over Events (Loop Over Items (Split in Batches)): loops over the items in batches
- In Monitoring Window? (If): checks a condition and branches into true / false
- Get Seen Records(events_seen) (Data table): get
- Load All Intervals(events_intervals ) (Data table): get
- Collapse To One Item (Code): runs custom JavaScript code
- Build Post-Event Report (Code): runs custom JavaScript code
…plus 14 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- n8n Form Trigger
n8n-nodes-base.formTrigger - Code
n8n-nodes-base.code - Schedule Trigger
n8n-nodes-base.scheduleTrigger - If
n8n-nodes-base.if - Google Gemini
@n8n/n8n-nodes-langchain.googleGemini - Slack
n8n-nodes-base.slack - Split Out
n8n-nodes-base.splitOut - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Data table
n8n-nodes-base.dataTable - MCP Client
@n8n/n8n-nodes-langchain.mcpClient
From the author
Quick overview This workflow monitors a time-boxed event by pulling live activity across your social media from Fanbase MCP every 15 minutes, analyzing each interval with Google Gemini, storing results in n8n Data Tables, and posting rolling reports plus…