---
title: "Stay ahead of action changes with Slack and Email notifications"
description: "Action Notifications help your change or approach expiration -- before surprises hit your pipeline."
canonical: "https://currents.dev/changelog/stay-ahead-of-action-changes-with-slack-and-email-notifications"
updated: "2026-03-25"
---

# Stay ahead of action changes with Slack and Email notifications

2026-03-25, New (tracks: platform)

Action Notifications help your change or approach expiration -- before surprises hit your pipeline.

---


**Action Notifications** help your change or approach expiration -- before surprises hit your pipeline.

Configure delivery once per project, then get alerts in Slack, email, or both, only for the lifecycle events you care about.

- **Slack** — Send to a single project channel (uses your existing Slack connection); pick which events trigger a message
- **Email** — Notify the action creator, org admins, and actions admins, plus optional extra addresses; same event controls as Slack
- **Fine-grained events** — Choose from creation, disable, re-enable, archive, **expiring soon** (advance warning before expiration), and **expired**
- **Where to configure** — **Actions → Settings** in the dashboard, alongside the rest of action management (separate from run-level Slack notifications)
- Available now for organizations using Actions

Open **Actions → Settings**, connect or confirm Slack if you use a channel, turn on **Email** if you want inbox alerts, then select events. Teams that rely on time-boxed quarantines or expiring skips can lean on **expiring soon** and **expired** so ownership and cleanup stay visible without manual polling.

- [Documentation](https://docs.currents.dev/)