How to Set Up Coolify Deployment Notifications on Your Phone

You pushed to main, Coolify picked it up, and the deploy failed halfway through pulling the image. You didn't find out until an hour later when someone asked why the staging site was throwing 502s. The deploy log was right there the whole time, you just weren't looking at it.

That gap between "the deploy did something" and "you know about it" is the entire problem here. Coolify is great at deploying. It is not great at tapping you on the shoulder when something goes sideways. The good news: it already knows how to fire a webhook on every deploy event, and you can point that webhook at your phone in about two minutes.

This is the no-bot, no-email version. No Telegram channel to create, no Discord server to babysit, just a push notification on your iPhone that says the deploy happened.

Why a Coolify push notification beats the alternatives

Coolify ships with a handful of notification channels: Email, Telegram, Discord, Slack, Pushover, and a generic Webhook. Email buries the alert in a folder you check twice a day. Telegram and Discord work, but now you're maintaining a bot token and a channel just to learn that a deploy finished.

The Webhook channel is the one almost nobody configures, and it's the simplest of the lot. Coolify sends a plain POST to any URL you give it whenever a deploy succeeds, fails, or a container changes state. Point it at TheNotificationApp's static webhook endpoint and the whole payload becomes a readable push on your phone. No SDK, no app to build.

What you need

• A Coolify instance you can reach the settings of (self-hosted or cloud, both have the same Notifications page).
• A free TheNotificationApp account and the iOS app installed, signed in with Apple.
• Your app key: it lives in the app under your application's settings.

That's it. No server-side code for the first method.

Step 1: Grab your static webhook URL

TheNotificationApp has an endpoint built exactly for "some service wants to ping me": the static webhook. You hand it your app key and an optional title, it accepts any JSON body, and it formats that body into a readable notification automatically. The URL looks like this:

https://thenotification.app/api/webhook/static/?app_key=YOUR_API_KEY&title=Coolify%20Deployment

Two things to know. app_key is required. That's the key from your app's settings. title is optional; it's the headline of the push, and you URL-encode the space as %20. Skip title entirely and the notification just reads "Webhook Notification," which is less useful when you're glancing at a lock screen.

Keep that full URL on your clipboard. The full reference is in the static webhook docs if you want the details.

Step 2: Add it as a Webhook channel in Coolify

In Coolify, go to Notifications → Webhook. Paste the URL from Step 1 into the endpoint field, save, and enable the channel. Coolify gives you a Test button right there: hit it. Within a second or two your phone should buzz. If it does, the plumbing works.

If nothing arrives, it's almost always one of two things: a typo in the app key, or you're testing on a device that isn't signed into the same account. Check both before you blame the webhook.

Step 3: Pick which events you actually care about

This is the step people skip, and then they wonder why their phone won't shut up. Under the Webhook channel's settings, Coolify lets you toggle which events fire a notification: deployment success, deployment failure, container status changes, backup results, and a few server-level alerts like disk usage.

For most people the honest answer is: turn on deployment failure and leave the rest off. A failed deploy is the thing you need to know about in real time. A successful deploy is nice to confirm, but if you ship ten times a day, ten "deploy succeeded" pushes get ignored fast, which means you'll miss the one failure buried among them. Start narrow. You can always add more later.

Want more control? Use a post-deployment command

The Webhook channel sends Coolify's raw payload, which is fine but generic. If you want a notification that says exactly what you want ("api.example.com is live"), drop down to a direct API call in a post-deployment command.

In your resource, open General → Pre/Post Deployment Commands and add this to the post-deployment field. It runs after a successful deploy:

curl -X POST https://thenotification.app/api/sendNotification \
  -H "app_key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Deploy finished",
    "body": "api.example.com is live",
    "link": "https://api.example.com"
  }'

One catch worth knowing before you paste it: post-deployment commands run inside your container, so curl has to actually be installed in that image. Slim Alpine or distroless images often don't have it, and the command will silently do nothing. If that happens, add curl to the image, or just stick with the Webhook channel from Step 2, which runs on Coolify's side and doesn't care what's in your container. The full request format is in the API reference.

The honest tradeoff

The free tier caps at 100 notifications total, not per month, total. For "ping me when a deploy fails," that's a long runway, because failures should be rare. But wire up every deploy event on a project you ship to twenty times a day and you'll chew through 100 in under a week. That's the whole reason Step 3 exists: notify on failure, not on everything. If you do need the volume, Pro is $2.99/month for 1,000 notifications a month.

That's the whole setup

Two minutes, one URL, and Coolify now tells you when a deploy breaks instead of leaving it in a log you'll read tomorrow. If you run CI on the same project, the same idea works there, here's how to get GitHub push notifications on your iPhone. Worth a look if you're tired of hearing about broken deploys from your users: thenotification.app.

New to this? Start with how webhook push notifications work.