Schedule low-risk deployment windows with GPT-4.1, Slack, and Google Calendar
Needs changesNeeds changes. This template uses 2 thing(s) that n8n 3.0 removes: HTTP Request Tool (legacy), AI Agent v1 (old agent modes). 2 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 21 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects HTTP Request, OpenAI Chat Model, Postgres and Slack and 1 more.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Prepare Deployment Config (Edit Fields (Set)): sets 8 fields: service, changeDescription, version…
- Deployment Window Analysis Agent (AI Agent): runs an AI agent, with model: OpenAI GPT-4 Model; 4 tools (Check Team Availability, Retrieve Incident History, Fetch Traffic Analytics Data, Get Deployment Failure History); memory: Use Buffer Memory
- Parse AI Agent Output (Edit Fields (Set)): sets 1 field: parsedOutput
- Log Window Recommendation to DB (Postgres): uses Postgres
- If: checks a condition and branches into true / false
- Ask for Deployment Approval via Slack (Slack): uses Slack
- Notify High Risk on Slack (Slack): uses Slack
- Wait: pauses before continuing
- Confirm Recommendation Logging to Webhook (Respond to Webhook): sends the response back to the webhook caller
- If: checks a condition and branches into true / false
…plus 4 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
2 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- HTTP Request Tool (legacy) in Fetch Traffic Analytics Data, Retrieve Incident History, Get Deployment Failure History…: replace with HTTP Request node connected to the AI Agent's Tool input.
- AI Agent v1 (old agent modes) in Deployment Window Analysis Agent (v1.6): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| HTTP Request Tool (legacy) Fetch Traffic Analytics Data, Retrieve Incident History, Get Deployment Failure History, Check Team Availability | HTTP Request node connected to the AI Agent's Tool input |
| AI Agent v1 (old agent modes) Deployment Window Analysis Agent (v1.6) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (13)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request Tool
@n8n/n8n-nodes-langchain.toolHttpRequest - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Simple Memory
@n8n/n8n-nodes-langchain.memoryBufferWindow - AI Agent
@n8n/n8n-nodes-langchain.agent - Postgres
n8n-nodes-base.postgres - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Wait
n8n-nodes-base.wait - Google Calendar
n8n-nodes-base.googleCalendar - HTTP Request
n8n-nodes-base.httpRequest - Respond to Webhook
n8n-nodes-base.respondToWebhook
From the author
Quick overview This workflow receives a deployment request via webhook, uses OpenAI with internal HTTP APIs (traffic, incidents, deployment history, and availability) to recommend a low-risk deployment window, logs the recommendation to Postgres, and requests…