n8n GPT-4.1 Deployment Windows: Slack Approval + Google Calendar

Get a low-risk deployment window recommendation—then get it approved in Slack and scheduled in Google Calendar

This n8n workflow receives deployment requests via webhook, uses OpenAI-powered internal HTTP lookups to recommend the safest deployment window, logs the decision to Postgres for audit, and routes approvals through Slack before it creates a Google Calendar hold and triggers your CI/CD scheduling at the selected time.

What this workflow does

• Receives a deployment request through an incoming webhook, including service name, version, change details, and optional earliest/latest deploy-by constraints.
• Analyzes risk using an OpenAI agent with session memory. The agent queries internal HTTP APIs for traffic analytics, incident history, deployment failure history, and team availability to select a primary and fallback deployment window with a risk score.
• Generates a structured recommendation (including window, risk, rationale, approvers, and status) and parses the agent’s JSON output.
• Audits every decision in Postgres by logging the recommendation details (window, risk, rationale, approvers, status, timestamp) to a Postgres table.
• Requests approval in Slack. If the risk score is high, it posts a high-risk notice; otherwise it posts an approval request and waits for an approval webhook response.
• Schedules the deployment only after approval: creates a Google Calendar event to hold the window, calls a CI/CD scheduling API to dispatch at the window start, and confirms the result back in Slack.

Use cases

• Choose safer release times by factoring traffic patterns, past incidents, and deployment failures.
• Enforce change-control with Slack approvals before scheduling production deployments.
• Maintain an auditable record of every recommended window and who approved it.

Technical details

• n8n nodes/workflow components: webhook, slack, postgres, wait, set, if.
• Model/agent behavior: OpenAI agent with session memory and internal HTTP API queries (traffic, incidents, deployment history, availability).
• Calendar + scheduling: Google Calendar event creation and CI/CD scheduling API invocation at the window start.