Supercharging Incident Response: Contextual Alerts & Safe Automation with n8n

We're resuming our in-person meetups and will start with one at Vintage Bar from Baia Mare's old town with our good friend zozo (Peter), amazing us with a nice way of using AI agents to automate services monitoring alerts, and adding more context to them to help the devops team save the day one more time.

Live streaming: https://youtube.com/live/nIMZRqAacWc?feature=share

Of course we'll grab a beer from the bar and we'll have pizza.

Stop drowning in vague alerts. Start shipping context and solutions directly to Slack.

Every SRE and DevOps engineer knows the pain: A monitoring tool fires a generic "High CPU" or "Pod Crash" alert into Slack at 3 AM. You have to wake up, log into VPN, open three different dashboards, and grep logs just to understand what is happening, let alone fix it.
It’s time to make our alerts work for us.

Join us for a deep dive into using n8n, the workflow automation tool, to transform noisy monitoring into intelligent incident response.
In this session, we will move beyond simple alert forwarding. We’ll demonstrate how to build n8n workflows that act as the "glue" between your cluster monitoring (Prometheus, Datadog, K8s events, etc.) and your communication channels.

We will cover practical examples of how to:

• Intercept and Enrich Alerts: Don't just post the webhook. Use n8n to immediately query the Kubernetes API for pod logs, fetch recent deployment events, or grab a snapshot graph from Grafana to attach to the Slack message.
• Perform Safe Auto-Remediation: Learn how to configure n8n to take immediate, low-risk actions—like restarting a specific deployment, clearing a cache, or scaling a non-production service—before a human even sees the alert.
• Empower the On-Call Engineer: Design Slack messages that provide the "who, what, where, and why" instantly, along with one-click buttons to trigger further investigative workflows, helping your team "save the day" in minutes instead of hours.

Who should attend: SREs, DevOps Engineers, Platform Engineers, and anyone tired of "dumb" paging alerts.