Set up Slack notifications for ZopNight scheduling events, start/stop confirmations, override alerts, failures, and savings summaries delivered to your channels.
This is the practical version, the one you can follow in a single sitting. It starts read-only, touches no production resource by default, and every step is reversible, so there is no point at which you are committed to something you cannot undo. Budget about 5 minutes. Before you start you will want: A ZopNight account with active schedules; Slack workspace admin access; At least one active schedule to test.
The steps
- Create a Slack webhook or install the ZopNight app.
- Configure notification channels.
- Set notification preferences.
- Test the integration.
Why this is safe to do today
The reason this is a low-stakes change is that nothing here is destructive. Scheduling stops and starts resources; it never deletes them, and your data persists across a stop exactly as it does across a normal reboot. Production is excluded by default, actions run in dependency order, and every state change is logged with what triggered it.
If you want the fuller context behind this task, the FinOps guide covers where it fits, and the AWS EC2 scheduling page shows the same loop applied to a specific resource.
Getting started
Getting started is intentionally low-stakes:
- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.
Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Can I trigger overrides from Slack?
Yes, if you use the ZopNight Slack app (not just webhooks). Override buttons appear on scheduling notifications, letting team members extend running hours directly from Slack without logging into the ZopNight dashboard.
How do I avoid notification fatigue?
Use daily digests instead of per-action notifications for routine start/stop events. Reserve real-time notifications for failures and overrides. Route different notification types to different channels so teams only see what is relevant to them.