Automation library · Scheduling

Schedule low-risk deployment windows with OpenAI and Slack

Started by another system calling it, and works across Google Calendar, Postgres and Slack. It puts OpenAI behind a retrieval step, so answers are drawn from documents you supply rather than from the model alone. 21 steps, 2 branches, 1 loop or waits: large, and worth reading before you trust it with anything live.

LargeCalls a model: OpenAIRetrieval

21 stepsLarge: read it before trusting it with anything live
2Branches: places the flow splits
1Loop or waits
3Services it connects to

The flow

Starts it 2Model 7Logic 5Service 7

The steps in the order they run, from what starts it.

  1. 1When Deployment RequestedWebhookStarts it
  2. 2Fetch Traffic Analytics DataTool Http RequestModel
  3. 3Retrieve Incident HistoryTool Http RequestModel
  4. 4Get Deployment Failure HistoryTool Http RequestModel
  5. 5Check Team AvailabilityTool Http RequestModel
  6. 6OpenAI GPT-4 ModelLm Chat Open AiModel
  7. 7Use Buffer MemoryMemory Buffer WindowModel
  8. 8Prepare Deployment ConfigSetLogic
  9. 9Deployment Window Analysis AgentAgentModel
  10. 10Parse AI Agent OutputSetLogic
  11. 11Log Window Recommendation to DBPostgresService
  12. 12If Risk is AcceptableIfLogic
  13. 13Ask for Deployment Approval via SlackSlackService
  14. 14Notify High Risk on SlackSlackService
  15. 15Wait for Deployment ApprovalWaitLogic
  16. 16Confirm Recommendation Logging to WebhookRespond To WebhookStarts it
  17. 17If Deployment ApprovedIfLogic
  18. 18Create Deployment Hold in CalendarGoogle CalendarService
  19. 19Announce Reschedule on SlackSlackService
  20. 20Schedule Deployment via CI/CDHttp RequestService
  21. 21Confirm Schedule on SlackSlackService

How it's built

Starts on
Another system calling it
Steps
21, with 2 branches, 1 loop or waits
Size
Large: read it before trusting it with anything live
Connects to
Google Calendar, Postgres, Slack
Model
OpenAI
Retrieval
Answers are drawn from documents you supply, not from the model alone

Questions

What does it need to run?

An n8n account, plus your own Google Calendar, Postgres and Slack accounts, and a key for OpenAI. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

Yes. It calls OpenAI. Its answers draw on documents you give it, not on the model alone. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Take your time. At 21 steps it is large: read it before trusting it with anything live.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 21 steps before you point it at anything that matters.