Skip to main content
Engineering

Not translated yet — showing English.

Alerts & Notifications

Notifications post to your own Slack channels when something changes in your project or on the platform. You add Slack incoming webhooks and choose, per webhook, which kinds of alert it receives. Webhooks are set per project and environment, in Project settings → Notifications: open Projects, click the settings icon on a project card, and switch to the Notifications tab.


What you can be alerted about

Three kinds of alert, each switched on or off per webhook.

KindSent whenWhat the message carries
DeploymentA function is deployed, or a new environment is created in the project.The function and its deploy, or the new environment, the environment it was copied from and its state.
Schema changeA schema migration is applied.The migration and the schema version it produced.
Health statusThe platform's overall health gets worse (to yellow or red), and again when it recovers.The new status, the previous one, and which systems are red or yellow.

Health status alerts describe the PlayServ platform as a whole, not your project: every webhook with the kind turned on receives the same alert. An alert goes out only when the status gets worse, so a long incident sends one message, not one a minute. The recovery alert follows once the platform has reported healthy three times in a row. What the colours mean is explained on the Public Status Page.


Add a webhook

Create the webhook in Slack

Create an incoming webhook for the channel that should receive the alerts, and copy its URL.

Add it to the project

In Project settings → Notifications, click Add webhook. Give it a Name, for example the channel name, and paste the Webhook URL; it must be a Slack incoming-webhook address (https://hooks.slack.com/…). Leave Enabled checked and click Add webhook.

Choose what it receives

Switch on the alert kinds this webhook should receive.

PlayServ keeps only the webhook URL: there is no Slack app to install and no Slack token to hand over. Anyone with the URL can post to the channel, so treat it as a secret.

A new webhook sends nothing until you turn a kind on

Routing is off by default. Until at least one kind is switched on for a webhook, its alerts are not delivered and appear in the queue as dropped.

ActionWhat happens
TestSends a test message and shows the result inline: delivered with its latency, or failed with the HTTP status and error. A delivered test proves the URL reaches the channel.
EditRenames the webhook or replaces its URL. The stored URL is never shown again, only masked.
EnabledTurns the webhook off without deleting it. A disabled webhook is kept but receives nothing; you can note why it is off.
DeleteRemoves the webhook.

Recent notifications

The delivery queue shows every alert the project produced and what happened to it. It is read-only.

StatusMeaning
pendingWaiting to be sent. Alerts are sent within about a minute.
sentDelivered to Slack.
failedDelivery kept failing and the retries ran out, after up to five attempts.
droppedNo enabled webhook had this kind switched on, so the alert was not sent.

A queue full of dropped rows usually means the project has no webhook yet, or the webhook doesn't have that kind switched on.


Next steps

Last updated on 14 Oct 2026