Notifications on your phone from the services you already use

Every service below posts to a URL. Paste your source's webhook URL from YouLMK where it asks, and its events land in your inbox with the source's own rules: how far it may reach, whether quiet hours hold it, how repeats group. Anything else that posts JSON works through the generic webhook.

Errors and uptime

Sentry: A push when an issue alert fires, with the error's title, where it happened and the level, and the issue one tap away. Fatal becomes critical, if you allow critical to break through.
Datadog: A push when a monitor triggers or recovers, with the alert's title and text and the event one tap away, through Datadog's Webhooks integration.
Better Stack: A push when an incident is created, acknowledged or resolved, with the monitor's name and the incident one tap away.
Grafana: A push when an alert rule fires or resolves, with the alert's title and message and Grafana one tap away, through a webhook contact point.
PagerDuty: A push when an incident is triggered, acknowledged or resolved on a service, with the incident's title and urgency and the incident one tap away.
Uptime Kuma: A push when a monitor goes down or comes back, from Uptime Kuma's own webhook notification, with down at high priority and one card per monitor.
Healthchecks.io: A push when a cron job fails to check in, and another when it does again, from Healthchecks.io's webhook integration with the check's name in the title.

Deploys and code

GitHub: A push when a workflow run finishes or fails, a release is published, or any repository event you choose, with the run one tap away. One webhook, signed.
Vercel: A push when a deployment succeeds, errors or is promoted, for the projects you choose. Pro and Enterprise teams.
Netlify: A push when a deploy succeeds or fails, or when a previously failing deploy recovers, with the site one tap away.
Railway: A push when a deployment fails, succeeds or crashes, or a volume or CPU alert fires, per project.
Render: A push when a deploy starts, ends or fails, or a service's health changes, from the workspace's webhooks. Pro plans and above.
Fly.io: Fly.io has no webhooks for an app's deploys or machines; here is what works instead: a line after fly deploy, the GitHub Action, and a watch on the app's health URL.

Payments

Stripe: A push when a payment succeeds, a charge fails, a payout lands or a dispute opens, with the amount in the card and the object one tap away in the Dashboard. Signed by Stripe.
Lemon Squeezy: A push when an order is created, a subscription starts, renews, fails or is refunded, with the order's amount and status in the card.
Paddle: A push when a transaction completes, a subscription changes or a payout is made, per notification destination.

Data

Supabase: A push when a row is inserted, updated or deleted in a table you choose, with the table as the group so a burst becomes one card.
Neon: Neon has no outgoing webhooks for a project; here is what works instead: a line in the job that runs your migrations, the GitHub Action, and a watch on your own health URL.
PlanetScale: A push when a deploy request opens, queues, applies or errors, when a branch is ready, or storage crosses a threshold, per database.

Automation

Home Assistant: Any automation's notify action lands in your YouLMK inbox with its rules, through Home Assistant's RESTful notify platform: one YAML block, no add-on.
changedetection.io: A push when a watched page changes, from changedetection.io's notifications through Apprise: the JSON line today, YouLMK's own youlmk:// line once changedetection.io carries the Apprise release that has it.
Apprise: One Apprise URL puts YouLMK inside everything that speaks Apprise: the command line, the Python library, the Apprise API container, and the tools that bundle it (Uptime Kuma, changedetection.io, Home Assistant, Sonarr, Radarr). YouLMK's own youlmk:// plugin was merged into Apprise on 14 September 2026 and ships with the release after 1.13.1; the JSON line works on every version today.
Zapier: One Webhooks by Zapier step at the end of a Zap sends a push with the fields you map, to your phone, the browser, email or Slack, with the source's rules.
Make: One HTTP module at the end of a scenario sends a push with the fields you map, with the source's rules.
n8n: One HTTP Request node at the end of a workflow sends a push with the fields you map, with the source's rules. A YouLMK node (n8n-nodes-youlmk) is on GitHub and reaches npm with its first release.
Slack: Slack is a destination in YouLMK; it can also be a sender: a Workflow Builder step that sends a web request posts to your key.