Reach the right devices
Register devices with an external ID, tags, attributes, and consent so campaigns can target real product audiences instead of anonymous tokens.
First-party Capgo Notifications
Capgo Notifications
Message users, update badges, and trigger live-update checks from the same Capgo release workflow. Notifications now connect native push with progressive deployments instead of leaving release teams to stitch it together.
14-day unlimited free trial. No credit card required
Native notifications work alongside Capgo Live Updates and channel rollouts.
iOS + Android
Native push delivery
External ID
Target known users
Badge + events
Track opens and state
Update checks
Silent push companion
Next or set
Install mode control
Channel-aware
Guide live updates
Animated illustration: a Capgo console card composes an alert for the external ID user_8421, sends it, and the push lands on an iPhone lock screen and an Android home screen. Delivered and opened counts tick up and the app badge moves from 2 to 3. The card then switches to a silent update check for the production channel, and both devices download bundle 1.4.1 to install on next launch.
Release communication
Push is now part of the deployment loop.
Capgo Notifications gives product teams the messaging surface they expect and gives release teams a native way to wake devices for live-update checks.
Move updates faster
Use a silent notification to ask opted-in devices to check, download, and queue the latest Capgo bundle for the channel you choose.
Prove what happened
Track provider setup, campaigns, delivery events, opens, badge changes, and background update-check results from the Capgo console.
Use notifications when a release needs a nudge.
- Tell users about a change that ships with a live update.
- Ask devices to check for a bundle without waiting for the next app open.
- Keep progressive rollout, channel, and install-mode controls in place.
Workflow
From provider setup to targeted update checks.
The notification plugin, Capgo console, and updater now work together for Capacitor apps.
1
Configure providers
Add Android and iOS push credentials in the Capgo console, then run the notification setup so the native plugin and updater are wired together.
2
Register recipients
Attach external IDs, tags, attributes, consent, and badges from your app so support, growth, and release workflows share the same device identity.
3
Send or trigger updates
Broadcast alerts, send API notifications to one user, or push a background update check during a progressive rollout.
Feature set
Native notifications without a separate release stack.
Capgo handles the surfaces that usually become one-off glue code around push, user targeting, and update nudges.
Capgo Notifications
Native push for release teams
Native push for release teams
Ship alert, background, badge, and update-check campaigns from the same product console your team already uses for Capgo releases.
$ npx @capgo/cli@latest notifications setup provider ready | recipients linked | update check enabled
Provider control plane
Keep Android and iOS notification providers active from the same Capgo app settings screen used by your release team.
Broadcast campaigns
Create alert, background, badge, or update-check campaigns when you need to reach every matching device.
API sends
Send a notification to a known external ID and inspect the devices linked to that recipient before you trigger it.
Badge management
Read, write, and sync app badge counts through the native plugin so notification state remains visible to users.
Background callbacks
Handle foreground receives, notification opens, and background data notifications in your Capacitor app.
Campaign stats
Follow campaign status, delivery results, opens, and update-check results without leaving the Capgo release workflow.
Rollout guidance
Use push to accelerate updates, not bypass controls.
Silent notifications can ask devices to check for a new bundle, while Capgo channels, install mode, and progressive rollout rules continue to decide what each device can install.
- Use alerts for user-facing messages and background campaigns for release operations.
- Keep silent update checks paired with channels and progressive rollout controls so every device still follows your deployment rules.
- Treat iOS background pushes as best-effort because the operating system can throttle delivery.
human support from Martin
$ notification.kind = update_check
channel selected | install mode next
progressive rollout still controls eligible devices
devices check, download, and queue the bundle
Push notifications with AI agents
Have your agent wire up push notifications
Capgo Agent Skills teach Claude Code, Codex, or Cursor how to install the notifications plugin, register devices, and handle background callbacks in your Capacitor app.
Try asking your agent
- Add Capgo push notifications to my app and register devices by user ID
- Update the app badge count when a notification arrives
- Trigger a silent live update check from a push notification
-
CLI
Every release action is a command. Script it in CI or let an agent run it.
npx @capgo/cli@latest bundle upload -
MCP server
Tools for apps, bundles, channels, stats, and native builds, ready for any MCP client.
npx @capgo/cli@latest mcp -
Agent Skills
Teach your agent the right way to add live updates, builds, and Capgo plugins.
npx skills add Cap-go/capgo-skills -
llms.txt
The full Capgo docs in one file, ready to paste into any model.
capgo.app/llms-full.txt
Customer proof
Trusted by teams shipping Capacitor apps
Notifications live in the same Capgo account teams already use for live updates and native builds.
Being able to add Device ID's to certain groups and push the changes to only certain groups is a life saver.
Being able to push production OTA updates instantly without waiting for full App Store review cycles has been a massive operational advantage.
Capgo Notifications
Reach users and move releases forward.
Add native push, badge control, campaign stats, and silent update checks to your Capacitor release workflow.