Get a push notification when your deploy finishes
A deploy takes long enough to lose your attention, but not long enough to start something else. Lert buzzes your phone the second production is live — or the moment a build breaks — so you can look away from the terminal and get on with your day.
The one-line version
Lert gives you a unique URL. Anything that can make an HTTP request can POST to it, and your phone gets a notification. To know when a deploy finishes, you add exactly one request to the end of your pipeline:
curl -X POST "https://lert.dev/p/your-id" \ -H "Content-Type: application/json" \ -d '{"title":"Deploy finished","body":"production · 2m 14s"}'
That's the whole thing. No headers beyond content type, no auth token, no SDK. Replace your-id with the endpoint from your Lert app and you're done.
Set it up in three steps
1. Copy your Lert URL
Open the Lert app, and your unique endpoint is on screen — something like https://lert.dev/p/your-id. Tap Copy. Treat this URL like a password: anyone who has it can send you a notification, and you can regenerate it any time if it leaks.
2. Add a POST to your pipeline
Drop the request into the last step of your build or deploy. Send one message on success and, ideally, a different one on failure so a red build is unmistakable on your lock screen.
# .github/workflows/deploy.yml - name: Notify phone on success if: success() run: | curl -X POST "https://lert.dev/p/your-id" \ -d '{"title":"Deploy finished ✅","body":"${{ github.repository }} is live"}' - name: Notify phone on failure if: failure() run: | curl -X POST "https://lert.dev/p/your-id" \ -d '{"title":"Deploy failed ❌","body":"${{ github.repository }} needs you"}'
3. Deploy
Push, let it run, and put your phone in your pocket. When the pipeline finishes, you get a real iOS push — it wakes a locked phone and buzzes a paired Apple Watch. Usually under a second.
Prefer a specific platform? The same one-line POST works from a Node post-deploy script, a Python step, a Vercel deploy hook, or a GitHub Action. Pick whichever fits your setup.
Platform notes
- Vercel / Netlify: add the curl as a post-deploy command, or point a deploy hook at a tiny function that forwards to Lert.
- GitHub Actions / GitLab CI: add a final step with
if: success()andif: failure()as shown above. - Docker / self-hosted: append the curl to your deploy script — it needs nothing but network access.
Why Lert for deploy alerts
Most notification tools make you create an account, generate an API key, and install a client library before you can send a single message. Lert removes all of that: the endpoint URL is the authentication, so a deploy notification is one HTTP request and zero configuration. It's the fastest path from "I wish my phone told me" to "my phone told me."
FAQ
Can I get notified when a deploy fails, not just succeeds?
Yes. Send the POST from both the success and failure branches of your pipeline with different text for each — for example a ✅ title on success and a ❌ title on failure. Lert delivers whatever you send.
Does this work with Vercel and Netlify?
Yes. Use a post-deploy command, a deploy hook, or a GitHub Action that sends an HTTP POST to your Lert URL. Anything that can make a request works.
Do I need an API key or account for the notifications?
No. Your Lert endpoint URL is the authentication — there's no separate key, token, or login to wire up.
How fast does the notification arrive?
Typically within a second or two of the POST. It's a real push, so it wakes a locked phone and buzzes a paired Apple Watch.
Never watch a deploy finish again.
Download Lert, copy your URL, add one line to your pipeline. Your phone does the waiting.