Skip to content

Integrations

Anything that can make an HTTP request can send to Pocketbell. These guides walk through the services people connect most, each with a request you can paste. The same list is at pocketbell.dev/integrations.

Monitoring and alerts

  • Healthchecks.io: An alert when a job misses its check-in, and when it’s back.
  • Uptime Kuma: Critical when a monitor goes down, and an all-clear when it’s back up.
  • UptimeRobot: Down alerts that repeat until someone acknowledges them.
  • Better Stack: Incidents as Critical notifications, cleared when they resolve.
  • Grafana: Alerts as they fire and resolve, Critical with a payload template.
  • Prometheus Alertmanager: Prometheus alerts, with the severe ones as Critical.
  • Sentry: Issues from your alert rules, the moment they fire.

Developer tools

Apps and automation

  • Zapier: Any Zap can end with a notification.
  • Make: Any scenario can end with a notification.
  • n8n: Any workflow can end with a notification.
  • IFTTT: Any applet can send a notification.
  • Stripe: Sales, failed payments and disputes as they happen.

Home and servers

Every guide uses one of these, and says which.

API Source: for a service that lets you write its request’s headers and body. It sends to https://api.pocketbell.dev/v1/messages with the Source’s key, and chooses the priority, the replace key, links and the rest itself. See Send a notification.

Webhook Source: for a service that only asks for a URL. It posts its own event to the Source’s URL, and templates in the app turn the event’s fields into the title and message. See Webhooks.

If it can send a webhook, it works with a webhook Source today. To ask for a guide, write to support@pocketbell.dev.