palmpush icon

project

palmpush

A minimal iOS app that gives scripts, automations, backend jobs, and AI agents a direct line to your iPhone.

Visit project
Type
Push notification bridge
Platform
iOS and HTTP API
Core workflow
Send requests to a listener URL

Highlights

Connect almost any tool

If a workflow can make an HTTP request, it can send a notification through a palmpush listener.

Know when something changes

Get a push when a build finishes, a job fails, or an agent needs your approval to continue.

Keep sources organized

Create separate listeners for different tools or projects so every notification has a clear origin.

Send push notifications to your iPhone from code

palmpush is a lightweight iOS push notification service for personal workflows. It turns an HTTP request into a notification on your iPhone, giving scripts, webhooks, backend jobs, automations, and AI agents a direct way to reach you when something changes.

Create a listener in the app, copy its unique listener URL, and send a title and body to that URL. If a tool can make an HTTP request, it can use palmpush without needing a dedicated integration.

A practical push notification API for everyday workflows

The workflow is deliberately small: an event happens, your code sends a request, and your iPhone receives the update. That makes palmpush useful when a deployment completes, a cron job fails, a background task finishes, or a side project gets a new signup.

You can call the listener URL from curl, JavaScript, Python, a CI pipeline, a server, or an automation platform. The sender does not need to know how iOS notification delivery works; it only needs the URL and the notification content.

Push notifications for AI agents

AI agents often continue working after you leave the terminal. A palmpush listener gives an agent a simple callback for moments that need your attention: a task is complete, a run has failed, or the next step needs approval.

The same pattern works for scheduled agents, research workflows, coding tools, and other long-running automations. Instead of checking a dashboard or reopening a session, you receive the result as an iPhone push notification.

Keep notification sources separate

Create a different listener for each tool, project, or agent so notifications have a clear source. Separate listeners also make it easier to replace one URL without interrupting every workflow connected to palmpush.

A listener URL contains a long random token and should be treated like a secret. Store it only in trusted tools, avoid exposing it in public code, and create a new listener if the URL is ever shared accidentally.

All projects