Setup
Create a Pushbullet access token
- Go to Pushbullet Settings → Account
- Under Access Tokens, click Create Access Token
- Copy the token — it’s shown only once
(Optional) Find a device identifier
To target a single device instead of broadcasting to all, list your devices and copy the Leave
iden value:deviceIden empty to push to every device on your account.Configuration
| Field | Description | Required |
|---|---|---|
accessToken | Pushbullet access token | Yes |
deviceIden | Target device identifier; broadcasts to all devices if empty | No |
Troubleshooting
Notifications not arriving (HTTP 401)
Notifications not arriving (HTTP 401)
The access token is invalid or was revoked. Generate a new one under Settings → Account → Access Tokens and update the channel config. Tokens are invalidated if you reset access tokens on your account.
Pushes go to the wrong device or nowhere
Pushes go to the wrong device or nowhere
A stale or mistyped
deviceIden causes pushes to silently miss. Re-list devices with curl https://api.pushbullet.com/v2/devices -H "Access-Token: ..." and confirm the iden, or clear the field to broadcast to all devices.Rate limited (HTTP 429)
Rate limited (HTTP 429)
Pushbullet enforces per-account rate limits. If you hit them during a burst of incidents, space out test calls and rely on DevHelm’s incident-level (not per-check) notifications to stay within quota.