Alerts & Notifications
Last updated: 26 August 2026
You can have PlayServ push a message to Slack when something notable happens in your project — a function deploys, an environment is created, a schema migration is applied, or platform health changes. Instead of watching dashboards, you point the platform at a Slack webhook and choose which events it should fire on.
Notifications are configured per project and environment. A webhook you add on dev fires for dev events; set up prod separately so staging noise never reaches a production channel.
How it works
There are two pieces: a webhook (where messages go) and rules (which events it fires on).
You add a webhook with your Slack URL, then attach one or more rules that decide which events reach it. A Test action sends a sample message so you can confirm the channel is wired before relying on it.
Events you can be notified about
Notifications are produced by several parts of the platform:
| Source | Fires on |
|---|---|
| Deploy pipeline | A function is deployed (function_deployed). |
| Environment lifecycle | A new environment is created (new_env). |
| Schema service | A schema migration is applied (migration_applied). |
| Health poller | Platform health changes — for example a service going unhealthy and later recovering. |
Setting up a webhook
- Create
- Add rules
- Test
Add a webhook with your Slack incoming-webhook URL, give it a name, and save. It starts with no rules, so it won't send anything until you add one.
Attach rules to the webhook to choose which events fire. Each rule targets an event source; a webhook with several rules fires on any of them.
Use the webhook's Test action to post a sample message to the channel. If it doesn't arrive, re-check the Slack URL before adding rules.
Delivery is queued and retried rather than sent inline with the event, so a brief Slack outage won't drop a deploy notification — but a message may arrive a moment after the event itself.
Next steps
- Public Status Page — the anonymous health endpoint notifications complement
- Functions — deploys are the most common notification source
- Automatic deploys by branch — pair branch deploys with a deploy notification